BSOD playing Fallout: New Vegas/Random BSODs during startup

[jman114]

Hello forum. I'm hoping somebody can assist me with these BSODs. My computer is about 2 years old and the only thing I've had replaced in it was a hard drive. Here is some information about the BSODs.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 7e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002F6B682
BCP3: FFFFF880031A1A48
BCP4: FFFFF880031A12B0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111511-19546-01.dmp
C:\Users\Jared\AppData\Local\Temp\WER-73164-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
_______________________________________________________________________

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
_______________________________________________________________________

And I have also been getting a blue screen corresponding with the file "nvlddmkm.sys" which is a Nvidia driver file, and momentarily my screen will flicker on and off and a message will pop up in the corner stating that "This driver has stopped working but has recovered".

Any assistance would be much appreciated. Thank you!

 

[zigzag3143]

Hello forum. I'm hoping somebody can assist me with these BSODs. My computer is about 2 years old and the only thing I've had replaced in it was a hard drive. Here is some information about the BSODs.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 7e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002F6B682
BCP3: FFFFF880031A1A48
BCP4: FFFFF880031A12B0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111511-19546-01.dmp
C:\Users\Jared\AppData\Local\Temp\WER-73164-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
_______________________________________________________________________

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
_______________________________________________________________________

And I have also been getting a blue screen corresponding with the file "nvlddmkm.sys" which is a Nvidia driver file, and momentarily my screen will flicker on and off and a message will pop up in the corner stating that "This driver has stopped working but has recovered".

Any assistance would be much appreciated. Thank you!

We do need the actual 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.

 

[jman114]

Sorry I should have attached the Minidump files in my initial post.

Here they are...

 

[zigzag3143]

Sorry I should have attached the Minidump files in my initial post.

Here they are...

No worries

Both DMP's were corrupt and not of much use but they do point to memory corruption (probably a driver)

These crashes were caused by memory corruption. 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.

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

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


ALSO PLEASE DOWNLOAD MALWAREBYTES AND RUN IT JUST TO PLAY IT SAFE.

 

[jman114]

Thank you for the reply.

Okay, so far I ran Memtest and let it run for 6 full passes and it did not show any errors. I just did a full scan with Malwarebytes and it did not show any infections. I am going to re-boot here soon with driver verifier and I will keep you posted on what happens with that.

Thanks again for your help and patience.

 

[zigzag3143]

Thank you for the reply.

Okay, so far I ran Memtest and let it run for 6 full passes and it did not show any errors. I just did a full scan with Malwarebytes and it did not show any infections. I am going to re-boot here soon with driver verifier and I will keep you posted on what happens with that.

Thanks again for your help and patience.

As I said before it is most likely a driver but we have eliminated both malware, and Ram as being the cause.

 

[jman114]

Yes I agree I think it is most likely a driver. I did a complete restore yesterday on this computer and kept installed programs down to a minimum just in-case it decided to give me BSODs again. I do have a virtual drive program (PowerISO) installed along with Nvidia drivers so I want to say it's either one or the other causing the BSODs, but in the past virtual drive programs and Nvidia drivers have never given me BSODs on this computer. I don't know if it might just be the hard drive going bad, causing my drivers to fail and making my monitor flicker on and off.

Anyway, driver verifier is currently enabled and it just so happens it is not wanting to BSOD now.

I'll keep you updated.

 

[zigzag3143]

Yes I agree I think it is most likely a driver. I did a complete restore yesterday on this computer and kept installed programs down to a minimum just in-case it decided to give me BSODs again. I do have a virtual drive program (PowerISO) installed along with Nvidia drivers so I want to say it's either one or the other causing the BSODs, but in the past virtual drive programs and Nvidia drivers have never given me BSODs on this computer. I don't know if it might just be the hard drive going bad, causing my drivers to fail and making my monitor flicker on and off.

Anyway, driver verifier is currently enabled and it just so happens it is not wanting to BSOD now.

I'll keep you updated.

Good luck

 

[jman114]

Okay, so I got a few more blue screens this morning. I attached another minidump file below.

The BCCodes are:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF88002FBB738
BCP3: FFFFF88002FBAFA0
BCP4: FFFFF880013042A3
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Ntfs.sys - Address FFFFF880013042A3 base at FFFFF88001241000, DateStamp 4d79996d

Files that help describe the problem:
C:\Windows\Minidump\111611-54959-01.dmp
C:\Users\Jared\AppData\Local\Temp\WER-106018-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

______________________________________________________________________

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111611-54959-01.dmp
C:\Users\Jared\AppData\Local\Temp\WER-106018-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[zigzag3143]

If you had a few you only uploaded one. That one is corrupt and of no use.

Blue Screen view often blames (incorrectly) the OS when it cant find the real cause and so is unreliable.


I would suggest you run the update readiness tool and update to SP-1


Ensure you install the correct 64 or 32bit option for your system)

Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)

ISC Diary | Windows 7 / 2008 R2 Service Pack 1 Problems

links courtesy jmh

 

[jman114]

I'm sorry I keep uploading corrupt .dmp files. I'm getting the .dmp files from C:\Windows\Minidump... how do I obtain a non-corrupted version?

It did blue screen a few times but there was only 1 recent .dmp file present which was the one from this morning. I'm currently installing the System Update Readiness Tool. I thought I already had SP1 installed but a quick update check showed that it wasn't installed. Thank you for the reply. I'll keep you updated on what happens.

 

[zigzag3143]

I'm sorry I keep uploading corrupt .dmp files. I'm getting the .dmp files from C:\Windows\Minidump... how do I obtain a non-corrupted version?

It did blue screen a few times but there was only 1 recent .dmp file present which was the one from this morning. I'm currently installing the System Update Readiness Tool. I thought I already had SP1 installed but a quick update check showed that it wasn't installed. Thank you for the reply. I'll keep you updated on what happens.

Good luck and let us know

 

[jman114]

Okay, so I played a stable session of New Vegas lastnight, but earlier today and about an hour ago, it gave me some more BSODs.

Here are the .dmp files. I am not aware if they are corrupt or not. I have heard that if your minidumps are corrupted, they are not being saved properly due to a hardware problem. Is that true?

 

[zigzag3143]

Okay, so I played a stable session of New Vegas lastnight, but earlier today and about an hour ago, it gave me some more BSODs.

Here are the .dmp files. I am not aware if they are corrupt or not. I have heard that if your minidumps are corrupted, they are not being saved properly due to a hardware problem. Is that true?

Making progress.


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOTbefore).

 

[jman114]

Okay so I replaced ASACPI.sys with the newer 2009 version by installing it with the ATK0110 Utility. I checked the date stamp and everything was good to go. It still caused BSODs so I took out the hard drive and replaced it with another one, re-formatted, and again, made sure I updated the ASACPI.sys file. It was running fine for a day but I got another BSOD about 30 minutes ago. Here is the newest .dmp file...

 

[jman114]

Just had another BSOD. Here's the minidump...