Solved BSOD at random intervals caused by NTOSKRNL.exe

[bassplayer97]

Hi,

I'm new here, but not new to IT and I'm quickly running out of ideas on this one. PC started to BSOD at random intervals. I haven't been able to narrow down the culprit though. Below, I have attached the last few crash dumps from whocrashed. Only thing I've done out of the ordinary recently was to uninstall a partition that I had installed Windows 8 for testing. The last step I took was to back up my important data, nuke the entire thing and do a fresh install of Windows 7 from a disk. Any input would be greatly appreciated. If you need any other information, please let me know!

On Sat 6/2/2012 12:53:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060112-20841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80076DAB30, 0xFFFFFA80076DAE10, 0xFFFFF80002F93510)
Error: CRITICAL_OBJECT_TERMINATION
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 a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.


On Fri 6/1/2012 11:22:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060112-21231-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80076214E0, 0xFFFFFA80076217C0, 0xFFFFF80002FCF510)
Error: CRITICAL_OBJECT_TERMINATION
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 a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.


[FONT=Segoe UI, Arial]On Fri 6/1/2012 2:55:14 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\053112-21512-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800763A490, 0xFFFFFA800763A770, 0xFFFFF80002F81510)
Error: [FONT=Segoe UI, Arial]CRITICAL_OBJECT_TERMINATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 5/31/2012 2:07:58 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\053112-21606-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008BEDB30, 0xFFFFFA8008BEDE10, 0xFFFFF80002FDF510)
Error: [FONT=Segoe UI, Arial]CRITICAL_OBJECT_TERMINATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 5/21/2012 11:26:45 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\052912-22386-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008C18B30, 0xFFFFFA8008C18E10, 0xFFFFF80002F86510)
Error: [FONT=Segoe UI, Arial]CRITICAL_OBJECT_TERMINATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 5/21/2012 7:34:24 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\052112-19827-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80092B8250, 0xFFFFFA80092B8530, 0xFFFFF80002FCD510)
Error: [FONT=Segoe UI, Arial]CRITICAL_OBJECT_TERMINATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.

[/FONT]

 

[JaidynM]

Run a full system scan with Malwarebytes.
Malwarebytes : Free anti-malware, anti-virus and spyware removal download

Run an sfc/scannow command in an elevated command prompt. If errors are found, run it twice more with each scan followed by a reboot.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

The following drivers need to be updated:

GEARAspiWDM.sys Mon May 18 22:17:04 2009
mcdbus.sys   Tue Feb 24 21:34:07 2009

These drivers can be found by searching them in Google and then finding the associated software or driver. Finally, find the latest version of this driver or software and download and install it. Some of the drivers may also be found here (if the driver says 'Windows Update' simply make sure all Windows Updates are installed).

You should also update any other drivers you can think of including graphics, audio, chipset, SSD etc.

Make sure all Windows updates are installed.

 

[bassplayer97]

All drivers are updated now (the mcdbus is the most current one from 2010, believe it or not)
Malwarebytes and sfc found nothing
All windows updates are installed

I'll keep an eye on it and update this as soon as it crashes again. Thanks for the quick reply!

 

[JaidynM]

No worries, post back with your dumps if another BSOD occurs.

 

[bassplayer97]

No luck on this one. It seems to continue to crash. There isn't really a rhyme or reason to it either. This time I had a single Chrome browser open and an Excel sheet when it froze up. It seems like an extremely slow crash too. The system becomes unresponsive and starts to hang and about 30 seconds later, it will BSOD. One thing worth noting is that when it reboots, it hangs at the Dell splash screen and I have to power it off and back on again to get it to fire up like normal. Attached are the dumps as requested. As always, I appreciate any help you guys can offer!!

 

[JaidynM]

I see you have an SSD installed. SSD's are a common cause of BSOD's, in particular Crucial M4's with outdated firmware. Make sure that the following is up to date:

• SSD Firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• Marvell IDE ATA/ATAPI controllers (older drivers for these are especially problematic)

 

[bassplayer97]

Firmware updates for 2 of my 3 drives and the chipset that Wupdate DIDN'T find. Had to go directly to Dell, crucial, and intel for those! All are installed and updated. Fingers crossed!!

 

[JaidynM]

Hopefully you don't get any more BSOD's. Please do post back though in a couple days, just so we know how you're going.

 

[bassplayer97]

Almost 24 hours up and running. Had to have been the firmware update for the SSD. Can't believe I didn't think of that one. Sevenforums has a new fan! Thank you very much JaidynM!!!

 

[JaidynM]

No worries, I'm glad I could help.