Solved Need help with a BSOD issue.

[Avison Atrius]

I recently built a new pc but I seem to be randomly getting BSOD errors infrequently every day or so. I have a full retail version of Windows 7 Ultimate 64 bit os. All my specs are in my profile.

Thanks for any and all help!

 

[zigzag3143]

I recently built a new pc but I seem to be randomly getting BSOD errors infrequently every day or so. I have a full retail version of Windows 7 Ultimate 64 bit os. All my specs are in my profile.

Thanks for any and all help!

caused by memory corruption (probably a driver) Please run these two tests


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



Driver verifier

I'd suggest that you first backup your stuff 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.

 

[Avison Atrius]

Well memtest86 says my memory is fine. I let it do five passes and not a single error.

It must be a driver error. How does using the verifier narrow down the bsod cause? Is there anything else I should know?

Either way, I input the settings into it and restarted and I haven't had a BSOD yet. What do I do when I get a BSOD?

 

[zigzag3143]

Well memtest86 says my memory is fine. I let it do five passes and not a single error.

It must be a driver error. How does using the verifier narrow down the bsod cause? Is there anything else I should know?

Either way, I input the settings into it and restarted and I haven't had a BSOD yet. What do I do when I get a BSOD?

Driver verifier "traps" the offending driver most of the time. Keep running till it crashes then upload the DMP

 

[Avison Atrius]

It crashed. Now what do I do?

 

[Avison Atrius]

I don't know where the DMP is so I can't post it, however after my computer crashed I can no longer access Steam. Which is not good.

 

[zigzag3143]

I don't know where the DMP is so I can't post it, however after my computer crashed I can no longer access Steam. Which is not good.

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.



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.

 

[Avison Atrius]

Here's the dumps.

 

[zigzag3143]

Here's the dumps.

Verifier enabled pool corruption. I would run these two tests.


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



Driver verifier

I'd suggest that you first backup your stuff 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.

 

[Avison Atrius]

7 passes no errors on memtest86.

 

[zigzag3143]

7 passes no errors on memtest86.

Great and verifier? Just remember memtest tests just the ram outside the windows environment so it may not crash outside windows but may in the windows environment,

 

[Avison Atrius]

Under those verifier settings windows bluescreened every time at start. Here is the only dump in the folder.

I'm starting to get artifacts in games now. Model coordinate stretching mostly. I tested my gpu for artifacts and it came up clear. This means I probably have a bad mem stick. >_<

 

[Avison Atrius]

I ran memtest under windows and I got this error:

Memory error detected. Copying between 2eebeb1 and 2eebe30 did not result in an accurate copy.

MemTest has detected that your computer cannot accurately store data in RAM. You need to fix this.

What do I do?

 

[zigzag3143]

I ran memtest under windows and I got this error:

Memory error detected. Copying between 2eebeb1 and 2eebe30 did not result in an accurate copy.

MemTest has detected that your computer cannot accurately store data in RAM. You need to fix this.

What do I do?

First (if you can) pull the stick and test the others again. If memtest found errors you may have to return the warranty (RMA).

You also want to test the mobo slots with known good ram to ensure the problem is ram and not a mobo slot.

 

[Avison Atrius]

I pulled the stick out and I seem to be running fine with no problems. So hopefully it was just the stick and not the slot. I'll update when I put the stick the the other slot.

 

[zigzag3143]

It crashed. Now what do I do?

Read the instructions. They say to reboot normally if you can, if not follow the directions

 

[Avison Atrius]

That's an old thing to quote, in addition there wasn't anything in the instructions prior to that post about what to do. But pulling that stick of ram solved all my problems. -_-