Frequent BSOD Crashes related to ntoskrnl and NTFS.sys

[SJMaye]

I built a PC for my Dad and get daily BSOD. Cannot find the source.
Windows 7
- x64
- Is theoriginal installed OS on the system. I installed in on an all new system
- Is full retail version

- What is the age of system (hardware) - ~ 1year
- What is the age of OS installation- Did full reinstall. OS reinstalled about 1 month ago.

Can anyone help?

 

[zigzag3143]

These crashes were caused by memory corruption (probably a driver). 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!!!


1-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 or 6 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



2-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 data 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"
- 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.

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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


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

One thing that needs to be removed is this driver. Related to SCMNdisP.sys NDIS User mode I/O Driver from Windows (R) Codename Longhorn DDK provider

 

[SJMaye]

I did run MemTest+. The first run with both sticks of ram in their original positions it found errors. Then I followed the instructions to move single sticks around and found nothing. I assumed that a ram stick was not properly seated and was fine after moving around. Crashes continued.

I will try memtest again and see what I get.

 

[SJMaye]

I just ran Memtest+ 16 passes for about 13 hours. No errors found. On to step 2.

 

[zigzag3143]

I just ran Memtest+ 16 passes for about 13 hours. No errors found. On to step 2.

Good news. Let hope verifier is quick and painless for you.

 

[SJMaye]

One thing that needs to be removed is this driver. Related to SCMNdisP.sys NDIS User mode I/O Driver from Windows (R) Codename Longhorn DDK provider

I have verifier running, but did not delete this driver. Wanted to be sure with you before doing so. Doing a search the location is

C:\Windows\System32\drivers\SCMNdisP.sys

Does this seem correct?

 

[zigzag3143]

One thing that needs to be removed is this driver. Related to SCMNdisP.sys NDIS User mode I/O Driver from Windows (R) Codename Longhorn DDK provider

I have verifier running, but did not delete this driver. Wanted to be sure with you before doing so. Doing a search the location is

C:\Windows\System32\drivers\SCMNdisP.sys

Does this seem correct?

If you are 32 bit yes.

 

[SJMaye]

I am running Win 7 HP 64bit edition. If you think that driver has anything to do with a Netgear usb wireless network adapter I can delete it. I only used that temporarily. No longer in use.

Strange thing is I was getting minidump files the other day almost every hour or so. Since running the verifier I see nothing. I will just keep it running.

 

[SJMaye]

Incidentally, how do I delete a driver? Go to the folder shown in my post above and just delete the file?

 

[SJMaye]

Odd. Verifier running now for about 6 hours. No crashes. Look at the snapshot from event viewer. You can see frequency was very high. Now nothing. The only thing I can recall doing that could have had an affect was a scan disk operation. Cannot find the log yet. I thought that would tell me the date and time of the scan disk to see if it correlates.

 

[zigzag3143]

No idea about event viewer as of now but I have seen verifier run for 36+ hours before crashing.

It is all a combination of circumstances.

 

[SJMaye]

I found the Check Disk scan. The date and time seem to correlate to when the crashes ceased. I will continue to run driver verifier. It has run almost 24 hours now without issue. Here are the results to the check disk. Not used to reading these, but nothing is popping out at me.

 

[SJMaye]

The machine has run for 3 days straight without incident. Granted it has just been idling, but it had been crashing relentlessly at idle in the past. It appears I am out of the woods. I just don't like knowing for sure what fixed it.

Again, thank you for the help!