BSOD problem

[ace1]

Lately my computer has been having BSOD's.

The first one was on 10-11-11, and the second one was today 10-19-11.

After doing some research, I was able to get some info about the BSOD's.

If you guys can tell me what is causing the problem, I would greatly appreciate it.

Let me know if you need additional info.

Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path Ntfs.sysNtfs.sys+c68470xa56250000xa57540000x0012f0000x4d7995273/10/2011 8:21:11 PMMicrosoft® Windows® Operating SystemNT File System Driver6.1.7600.16385 (win7_rtm.090713-1255)Microsoft CorporationC:\Windows\system32\drivers\Ntfs.sys ntkrnlpa.exentkrnlpa.exe+a3e050xe324f0000xe36610000x004120000x4e02a3896/22/2011 7:23:05 PMMicrosoft® Windows® Operating SystemNT Kernel & System6.1.7601.17640 (win7sp1_gdr.110622-1506)Microsoft CorporationC:\Windows\system32\ntkrnlpa.exe

 

[zigzag3143]

Lately my computer has been having BSOD's.

The first one was on 10-11-11, and the second one was today 10-19-11.

After doing some research, I was able to get some info about the BSOD's.

If you guys can tell me what is causing the problem, I would greatly appreciate it.

Let me know if you need additional info.

Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path Ntfs.sysNtfs.sys+c68470xa56250000xa57540000x0012f0000x4d7995273/10/2011 8:21:11 PMMicrosoft® Windows® Operating SystemNT File System Driver6.1.7600.16385 (win7_rtm.090713-1255)Microsoft CorporationC:\Windows\system32\drivers\Ntfs.sys ntkrnlpa.exentkrnlpa.exe+a3e050xe324f0000xe36610000x004120000x4e02a3896/22/2011 7:23:05 PMMicrosoft® Windows® Operating SystemNT Kernel & System6.1.7601.17640 (win7sp1_gdr.110622-1506)Microsoft CorporationC:\Windows\system32\ntkrnlpa.exe

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.

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.

 

[ace1]

Lately my computer has been having BSOD's.

The first one was on 10-11-11, and the second one was today 10-19-11.

After doing some research, I was able to get some info about the BSOD's.

If you guys can tell me what is causing the problem, I would greatly appreciate it.

Let me know if you need additional info.

Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path Ntfs.sysNtfs.sys+c68470xa56250000xa57540000x0012f0000x4d7995273/10/2011 8:21:11 PMMicrosoft® Windows® Operating SystemNT File System Driver6.1.7600.16385 (win7_rtm.090713-1255)Microsoft CorporationC:\Windows\system32\drivers\Ntfs.sys ntkrnlpa.exentkrnlpa.exe+a3e050xe324f0000xe36610000x004120000x4e02a3896/22/2011 7:23:05 PMMicrosoft® Windows® Operating SystemNT Kernel & System6.1.7601.17640 (win7sp1_gdr.110622-1506)Microsoft CorporationC:\Windows\system32\ntkrnlpa.exe

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.

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.

Thanks for the reply, hopefully this attachment helps

 

[zigzag3143]

Memory corruption caused by a driver. Since the computer was up for 6 + days before it crashed, and there has only been 3 crashes in three months it may be difficult to pin down.

If you wish to pursue it run these three tests

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


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.

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



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


There was some indication of a disk controller error so please also run this CHKDSK

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.


B- Elevated Command Prompt:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.

 

[ace1]

Ran the memtest, No errors were detected. I'll move on to the driver verifier now.

 

[zigzag3143]

Ran the memtest, No errors were detected. I'll move on to the driver verifier now.

Sounds good.

 

[ace1]

Ran the memtest, No errors were detected. I'll move on to the driver verifier now.

Sounds good.

Hi, sorry for the late reply. Before I could attempt to the second fix that you posted, my HDD crashed. It was about 5 years old. I just got a new one today, so hopefully that will take care of my memory interfering with a specific driver. Thanks for all your help.