Windows 7: BSOD probably caused by Ntfs.sys, ntkrnlmp.exe, win32k.sys

jmt83 · 22 Jan 2013

OK, thanks!

jmt83 · 27 Jan 2013

Hey, everyone. Right now I'm 13 hours and counting running memtest86+ with no errors. Right now I am 4 passes into testing the last DIMM slot (so far I have run every test to at least 8 passes). The PC has 2 RAM sticks and 4 slots, and I have tested each stick individually accross the slots and have yet to experienced an issue.

Are there any other tests or reports I can provide to help out?

Thanks,

JMT83

Quote: Originally Posted by koolkat77

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

Quote:

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

Arc · 27 Jan 2013

In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

jmt83 · 27 Jan 2013

Archie,

I logged in this morning to run Driver Verifier, but the computer crashed before I even got started. Here is the latest info attached. I will go ahead and run Driver Verifier now to see if it will crash while the program is running. Thanks!

Arc · 27 Jan 2013

There is one new crash dump, but the is not with DV enabled, and equally silent. In the next try of enabling DV, make it sure that you are not checking any of the "microsoft" and "unknown" provided drivers. Hopefully it will work.

jmt83 · 28 Jan 2013

Archie,

I've been running DV for about 12 hours, but need to shut down the computer to take it back to the office. Just my luck; the computer crashed 3 times Sunday before I started to run DV, but did not crash afterwards. I will continue to run DV and provide you with any new info I receive, but I have attached another zip folder, just in case there is anything inside that might be helpful. Thanks!

Arc · 28 Jan 2013

We need the verifier enabled dumps to see.

Make it user that crash dump recording is properly configured. Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

jmt83 · 01 Feb 2013

The PC has been running since AM Monday and after 4.5 straight days of running DV, the system finally crashed earlier this afternoon. I am crossing my fingers that enough information has been collected to figure out what is wrong. I have attached the latest zip.

Also, please note from my earlier posts that I ran memtest86+ last weekend for about 16 hours, alternating each stick for 8+ passes in each slot. This yielded no errors.

Thanks in advance for looking into this. Best of luck trying to decode the answer!

JMT83

Quote: Originally Posted by Arc

We need the verifier enabled dumps to see.

Make it user that crash dump recording is properly configured. Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Arc · 02 Feb 2013

Do some disc checks.

Update your SSD's Firmware
Reseat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

If any component of the hardware is overclocked, stop overclocking.

And, try to dismantle the computer and reassamble it.

BTW, there is no new crash dump in the zip.

jmt83 · 03 Feb 2013

I follwed the instructions with these resuls:

1. To my knowledge, there is not a firmware update available for my HDD. The model number is
WDC WD2500AAJS-75M0A0 and the firmware version is 02.03E02.

2. I reseated the SATA and power.

3. Last night I ran SFC /SCANNOW and CHKDSK /F /R. SCANNOW showed errors the first time I ran it and said they were corrected. I ran SCANNOW again and the message said it could not fix the errors. Results attached.

4. I ran the SeaTools Long Test this morning and it passed.

Just an FYI, I also applied some Windows Updates and updated the PC's network drivers.

Thanks!
JMT83

Quote: Originally Posted by Arc

Do some disc checks.

Update your SSD's Firmware
Reseat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

If any component of the hardware is overclocked, stop overclocking.

And, try to dismantle the computer and reassamble it.

BTW, there is no new crash dump in the zip.

Windows 7: BSOD probably caused by Ntfs.sys, ntkrnlmp.exe, win32k.sys

BSOD probably caused by Ntfs.sys, ntkrnlmp.exe, win32k.sys problems?