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 probably caused by Ntfs.sys, ntkrnlmp.exe, win32k.sys

22 Jan 2013   #11
jmt83

Windows 7 Pro x64
 
 

OK, thanks!


My System SpecsSystem Spec
.
27 Jan 2013   #12
jmt83

Windows 7 Pro x64
 
 

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   Quote: Originally Posted by koolkat77 View Post
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
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   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.
My System SpecsSystem Spec
27 Jan 2013   #13
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
.

27 Jan 2013   #14
jmt83

Windows 7 Pro x64
 
 

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!
My System SpecsSystem Spec
27 Jan 2013   #15
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
28 Jan 2013   #16
jmt83

Windows 7 Pro x64
 
 

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!
My System SpecsSystem Spec
28 Jan 2013   #17
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
01 Feb 2013   #18
jmt83

Windows 7 Pro x64
 
 

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   Quote: Originally Posted by Arc View Post
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.
My System SpecsSystem Spec
02 Feb 2013   #19
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Do some disc checks.
  1. Update your SSD's Firmware
  2. Reseat the sata and power.
  3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
  4. 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.
My System SpecsSystem Spec
03 Feb 2013   #20
jmt83

Windows 7 Pro x64
 
 
HDD

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   Quote: Originally Posted by Arc View Post
Do some disc checks.
  1. Update your SSD's Firmware
  2. Reseat the sata and power.
  3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
  4. 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.
My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
ntoskrnl.exe + ntfs.sys + win32k.sys BSOD
hello everyone, I get randomally BSODs for over a month and I need some help. I have 6 dmp files: I got 4 BSODs caused by address ntoskrnl.exe+75b80, 1 BSOD caused by address win32k.sys+48005, 1 BSOD caused by address Ntfs.sys+1f745 The crash address of all of them is...
BSOD Help and Support
BSOD twice in 5 days (ntoskrnl.exe/ntkrnlmp.exe and ntfs.sys)
I got a BSOD twice in the last 5 days. According to WhoCrashed, the first one came from ntfs.sys and the next one from ntoskrnl.exe/ntkrnlmp.exe. Apparently most likely a driver/memory error. The OS is Win7 x64 Ultimate Professional retail. The PC is slightly less than 2 years old and so is the...
BSOD Help and Support
BSOD caused by ntkrnlmp.exe
When I opened YouTube video, pc give me BSOD. Here is the dump file. I have uninstalled Flash Player using this method. Installed latest version. Using Firefox 9.0.1. Thanks, StalkeR.
BSOD Help and Support
BSOD ntfs.sys and win32k.sys
Is Windows 7 . . . - x86 (32-bit) - Windows Vista, now Windows 7 Ultimate - an OEM - What is the age of system (hardware)? --> 1 year + - What is the age of OS installation (have you re-installed the OS?) Installed windows 7 about 4-5 months ago. I normally get a BSOD when im playing...
BSOD Help and Support
BSOD on startup Ntfs.sys,Win32k.sys
I just built my computer about a week ago and was running fine for about two days. The second day I started getting BSOD errors just as the system booted, or when I tried to run a program. I have ran a memory test, and checked the disk. All my drivers are up to date, and I am out of options. I can...
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 15:23.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App