Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD random - ntoskrnl.exe and ntkrnlmp.exe errors


26 Apr 2012   #1

Windows 7 64bit
 
 
BSOD random - ntoskrnl.exe and ntkrnlmp.exe errors

Intel Core i7-2600K CPU @3.40 GHZ
12 GB RAM - OCZ Agility 3 120GB SSD

Hello,

Over the course of the past few weeks I've been getting all kinds of random BSOD's. At first they mainly started when accessing netflix but slowly escalated to just randomly when I'm using photoshop to do my client work. Sometimes they'll just happen when I let the computer idle for too long and it goes into sleep mode. Usually after the BSOD I'll restart it but it wont read the hard drive but after another shutdown it'll read again.

Whenever I run chkdsk /r the computer starts running great again but slowly goes back to the BSOD. Also, whenever I run chkdsk /r after having used the computer (BSOD or not) it always cleans through everything as opposed to saying its already clean.

Is this a bad SSD drive? I have no idea whats going on . Any help would be greatly appreciated!

Heres my Crash dump analysis(it doesn't always catch the crashes, they happen daily)

On Thu 4/26/2012 3:36:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042512-27471-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AC29B30, 0xFFFFFA800AC29E10, 0xFFFFF800035928B0)
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 Thu 4/26/2012 3:36:52 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AC29B30, 0xFFFFFA800AC29E10, 0xFFFFF800035928B0)
Error: CRITICAL_OBJECT_TERMINATION
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 Mon 4/23/2012 7:35:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-30045-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B3DA060, 0xFFFFFA800B3DA340, 0xFFFFF800035908B0)
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 Sun 4/15/2012 3:11:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041412-29421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B334060, 0xFFFFFA800B334340, 0xFFFFF800035E18B0)
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.


My System SpecsSystem Spec
.

26 Apr 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.



You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:
Quote:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:
Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
My System SpecsSystem Spec
26 Apr 2012   #3

Windows 7 64bit
 
 

Hey JMH - Attached the System info and the small dump files, although everything you asked wasn't enabled but hopefully thats some help. Although I did enable everything you asked.
My System SpecsSystem Spec
.


26 Apr 2012   #4

Windows 7 64bit
 
 

Also, having shut off overclocking I got the same crash again. Included the info again and new Minidump



On Thu 4/26/2012 1:29:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042612-41808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B5DF060, 0xFFFFFA800B5DF340, 0xFFFFF800035DA8B0)
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 Thu 4/26/2012 1:29:43 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B5DF060, 0xFFFFFA800B5DF340, 0xFFFFF800035DA8B0)
Error: CRITICAL_OBJECT_TERMINATION
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.
My System SpecsSystem Spec
26 Apr 2012   #5

Windows 7 64bit
 
 

Just wanted to update, I ran the Driver Verifier as someone else suggested and found this. Its not the same error and running the verifier after fixing it didn't come up with any errors. But it didn't address the previous problem -



On Thu 4/26/2012 2:48:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042612-21543-01.dmp
This was probably caused by the following module: tosporte.sys (tosporte+0x8EE4)
Bugcheck code: 0xC9 (0x24C, 0xFFFFF880054EEEE4, 0xFFFFF980130C6DC0, 0x103)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\tosporte.sys
product: TOSHIBA Bluetooth Port Emulation Driver
company: TOSHIBA Corporation
description: TOSHIBA Bluetooth Port Emulation Driver
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tosporte.sys (TOSHIBA Bluetooth Port Emulation Driver, TOSHIBA Corporation).
Google query: tosporte.sys TOSHIBA Corporation DRIVER_VERIFIER_IOMANAGER_VIOLATION




On Thu 4/26/2012 2:48:44 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC9 (0x24C, 0xFFFFF880054EEEE4, 0xFFFFF980130C6DC0, 0x103)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug check description: This is the bug check code for all Driver Verifier
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.
My System SpecsSystem Spec
26 Apr 2012   #6
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

We prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps.
It is considered the Gold standard for those of us that do this and often will give us the answer by itself.

{BlueScreenView more often than not doesn't point out the correct causes.
Similarly Who crashed is even worse.}

I suggest you run SFC {Option 2}
Read through the Tutorial carefully.
Note you may need to run SFC three times to fix things.
Let us know the report at the end.


SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
My System SpecsSystem Spec
26 Apr 2012   #7

Windows 7 64bit
 
 

Hey JMH,

I ran the scan 3 times and it didn't find any violations.
My System SpecsSystem Spec
27 Apr 2012   #8
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Good news.
Continue using your computer as per normal.
Submit any further DMP's for analysis.
My System SpecsSystem Spec
30 Apr 2012   #9

Windows 7 64bit
 
 

Had another crash, I'm attaching the dump file

This is the Dump analysis


On Mon 4/30/2012 8:33:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043012-26473-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B0FE060, 0xFFFFFA800B0FE340, 0xFFFFF800035CC8B0)
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 Mon 4/30/2012 8:33:34 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B0FE060, 0xFFFFFA800B0FE340, 0xFFFFF800035CC8B0)
Error: CRITICAL_OBJECT_TERMINATION
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.
My System SpecsSystem Spec
30 Apr 2012   #10
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials
AT LEAST TO TEST

Download tools and utilities | AVG Worldwide


Microsoft Security Essentials - Free Antivirus for Windows
My System SpecsSystem Spec
Reply

 BSOD random - ntoskrnl.exe and ntkrnlmp.exe errors




Thread Tools



Similar help and support threads for2: BSOD random - ntoskrnl.exe and ntkrnlmp.exe errors
Thread Forum
Solved Random BSOD's, mainly ntoskrnl.exe but also other errors. BSOD Help and Support
Solved BSOD ntoskrnl.exe and ntkrnlmp.exe BSOD Help and Support
BSOD at random time at ntoskrnl.exe (nt+0x75C40) and ntkrnlmp.exe (nt BSOD Help and Support
Random BSOD errors ntoskrnl.exe and wdf01000.sys BSOD Help and Support
BSOD in random moments, ntoskrnl.exe, different errors BSOD Help and Support
BSOD ntoskrnl.exe, ntkrnlmp.exe BSOD Help and Support
Random BSOD with ntoskrnl.exe and ntkrnlmp.exe BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 02:26 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33