Vista - Random BSODs (Ultimate x64 SP1)

At this time, I've had a few random BSODs after ~2 weeks with Vista SP1. As far as I remember, I've had 3 different BSODs: 0x000000F4 (one time, today just after booting), 0x00000109 (two times, when loading two different games, the game worked just fine afterwards) and 0x0000003B (one time, when exitting Photoshop CS3).

I've tried Google, but I can't find a solution.

My specs are:
E8200 @ 3.5Ghz (440x8) OCCT'd for 16 hours, no crash
2x1GB Corsair XMS2 PC2-6400 1:1
GeForce 8600GTS
Asus P5K SE
WD Caviar 250GB SATA2 (system, I think it's become bad (very slow loading times, been going on for a while)
Samsung Spinpoint 400GB SATA2 (storage, doesn't seem to have any problems)

Visit this page and you may find answers you're looking for

Troubleshooting Windows STOP Messages

I looked there, and I couldn't find the answers for any of the BSODs. :/

According to the information you gave, and the site that Acdcfan provided, the "0x000000F4" stop message is

According to Microsoft (Connecting a hard disk drive in slave only mode leads to system halt during resume from standby) this stop message may also appear as 0x7A.

What you need to check is whether any of your PATA drives (hard disks or CD/DVD drives) are set as slave drives, but are the only devices on the cable.

STOP 0x00000109 can maybe be resolvd by shutting down then removing and reseating you memory. also, if you have overclocked you rig, try resetting to factory defaults to see if this clears up the issue, as STOP 0x109 can also be caused by a poor OC.

See if this patch from Microsoft (oddly not released via Windows Update) helps - An update is available that improves the compatibility and reliability of Windows Vista

I've clocked down my cpu to 3Ghz now, reseated my RAM and checked my PATA drive. The PATA driver was already set as master, so it couldn't be that. When I tried to install the update, it gave me an error saying 'This update is not relevant for your system.', although I never installed any other updates than the ones released through Windows Update.

I would take a close look at your DRAM - run a memory check and make sure that funky corsair memory is getting the right voltage - BIOS update may be required.

I realise the memory worked before SP1, but memory can go bad anytime, and SP1 seems to accelerate the process.

The caviar is the next likely cause.

good luck!

Hi Tricky, This is very strange, all the BSODs relate to system security services being corrupted or changed in ways completely unsupported on Vista... Its either malicious software, an old driver or application thats causing all these problems for sure....

The CRITICAL_STRUCTURE_CORRUPTION bug check has a value of 0x00000109 This indicates that the kernel has detected critical kernel code or data corruption. Cause There are generally three different causes for this bug check: 1. A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems. 2. A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time. 3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.

The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Sounds like I know what to do this week then. I updated the BIOS a few days ago after I got a new motherboard, as the old one failed (same one, with an older BIOS) and didn't detect my keyboard. As I'm writing this post, I've already started scanning for viruses and malware (damnit, this is going to take a long time !).