BSOD random - ntoskrnl.exe and ntkrnlmp.exe errors

[DaveRapoza]

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.

 

[JMH]

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:

* 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:

* 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.

 

[DaveRapoza]

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.

 

[DaveRapoza]

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.

 

[DaveRapoza]

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.

 

[JMH]

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.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[DaveRapoza]

Hey JMH,

I ran the scan 3 times and it didn't find any violations.

 

[JMH]

Good news.
Continue using your computer as per normal.
Submit any further DMP's for analysis.

 

[DaveRapoza]

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.

 

[JMH]

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

 

[zigzag3143]

In addition to JMH's suggestions please run the two below tests.

I know you have run verifier for at least one crash but you need to keep running it so that we have a trend.

Before you run verifier lets have you run memtest to eliminate the ram as a possibility.



Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[DaveRapoza]

JMH - The avast was actually something new I put on to help maybe find if a virus was causing it. That being said I uninstalled it like you asked

zigzag3143 - I ran the verifier a few days ago and it found that tosporte.sys was causing an issue and I fixed that one. Buts its not the consistent bsod I get.

I ran one of the ram sticks that was healthy in all 3 slots and didn't find any issues until the 3rd slot which gave me the screen(attached) but its still running the test and I can actually see through the scramble a bit and it doesn't look like its found any errors(as new things move on the screen the scramble goes away from that one bit).

 

[DaveRapoza]

Just wanted to update again, I ran the test on the same card/slot and didn't get the scrambled screen

 

[zigzag3143]

Just wanted to update again, I ran the test on the same card/slot and didn't get the scrambled screen

So All sticks and slots test with no errors?

 

[DaveRapoza]

so far no issue but I can't finish just yet, still have to test the last card but I got a call from a client and I need to finish a job. I will post soon though, hoping something is found from the ram

 

[zigzag3143]

so far no issue but I can't finish just yet, still have to test the last card but I got a call from a client and I need to finish a job. I will post soon though, hoping something is found from the ram

Take your time and yell if you need help.

 

[DaveRapoza]

Hello, ran the rest of the ram cards and nothin changed. Still get BSOD got 2 BSOD's here -


On Sat 6/9/2012 12:15:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-21262-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B3BBB30, 0xFFFFFA800B3BBE10, 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 Sat 6/9/2012 12:15:51 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, 0xFFFFFA800B3BBB30, 0xFFFFFA800B3BBE10, 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.

 

[writhziden]

Probably related to the SSD, but I cannot tell for sure since you did not follow the blue screen instructions.

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with your full crash reports and system logs.

 

[DaveRapoza]

Ah ok, thanks! Sorry about that, I was still going by what the last poster did helping me.

Uploaded the zip requested, heres my info -

-x64
-I had x64 before but reinstalled it apon request from someone helping me
-full retail version
-the computer was put together 2011
-I believe I reinstalled the OS in March this year

 

[writhziden]

Problematic Software:

Start Menu\Programs\Argente - Registry Cleaner	Public:Start Menu\Programs\Argente - Registry Cleaner	Public
Start Menu\Programs\RegistryCleaner	Public:Start Menu\Programs\RegistryCleaner	Public

• Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
  
  In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.

The latest crashes primarily indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure it is up to date.
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

I do see the Marvell Controller driver installed. RAID: Marvell* SATA Driver