Frequent 0x0000004 BSOD while gaming or installing or opening

So, I built myself this computer about 6-10 months ago and on initial setup everything was running smoothly, until I started getting BSODs left right and centre, I attributed this to my overclocking and downclocked. I then had trouble booting, as the Bios kept resetting the boot drive to the seagate, instead of my vertex 3.

Once I had sorted this out I resumed using the system, until frequent BSODs plagued me again. I attributed this to corruption in windows from all the previous blue screens and Secure Erased my drive and reinstalled Windows, I hoped this would remedy the BSODs, however I wasn't putting enough voltage through my ram which caused a few, but after sorting that aspect out, and having default clocks for all components on a stable Memory tested setup, in use I experienced more blue screens.

These are the 0x0000004 Code BSODs, and I am not getting any dumps from them, so I can't analyse if a driver is causing it or a component.

After the most recent BSOD, my hard-drive was not found on boot or in the bios, a restart solved the problem. This immediately made me suspect my hard-drive and I ran perfmon /report, It showed me a read/write of 10mb/s which is way too low for the vertex, so I downloaded SSDlife, which shows drive health as being "Excellent" and on 100%

However, SSD life only shows the drive as having written/read 1 gigabyte in the last 7 days which is impossible.

I am utterly perplexed, the error I get is
'A process or thread crucial to system operation has unexpectedly exited or been terminated.'



STOP: 0x0000004 (0x0000000000000003,0xFFFFFF
Is all I can write down before my computer resets.

There is no progress bar in the dumps on the BSOD, and when I run WhoCrashed a crash isn't picked up. Which is why I have no dumps to offer you.

And just now a new BSOD, again I feel this points to the hard-drive, yet if I can't diagnose it with anything I can't RMA it.

On Wed 06/06/2012 01:40:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060612-12324-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x19408)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000069408, 0xFFFFF8800D5A7DE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Same problem, different system file.

On Wed 06/06/2012 16:45:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060612-12573-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D9DF8C, 0xFFFFF8800BD22760, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

I ran sfc /scannow it found corrupt files but was unable to fix some of them, I also found my drives firmware is out of date, so I'm going to update the firmware and then run sfc a few more times.

The information you are getting is useless. It is telling you Windows is not working properly. I think you already knew that, or you would not be here. Please follow the https://www.sevenforums.com/crashes-d...tructions.html so we can do a full analysis of the crash reports and provide troubleshooting.

3rd party blue screen tools often point to Windows as the issue. That is why we use WinDbg instead of 3rd party analysis software.


By the way, a BugCheck 0x3B generally means graphics driver issues.

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION