BSOD during a game and at startup

[XplicitMind]

This has been happening for a while now. I would get random BSOD screens as I start up and that would be the only time it happens. As well as when I play a game online, it randomly freezes and BSOD happens again. I hope the information that I have provided is enough to correct my problem.

Thanks.

Windows 7 Ultimate x64
Installed a full retail copy 2 weeks ago
Age is about 1 year
Installed a fresh copy of Windows 7 Ultimate x64 two weeks ago.

 

[zigzag3143]

This has been happening for a while now. I would get random BSOD screens as I start up and that would be the only time it happens. As well as when I play a game online, it randomly freezes and BSOD happens again. I hope the information that I have provided is enough to correct my problem.

Thanks.

Windows 7 Ultimate x64
Installed a full retail copy 2 weeks ago
Age is about 1 year
Installed a fresh copy of Windows 7 Ultimate x64 two weeks ago.

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
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

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).

 

[XplicitMind]

EDIT: Nevermind I misread it.

I'll see how things goes and let you know if anything else happen.

 

[XplicitMind]

New BSOD screen. Said Bad pool sector. It was during when I was idling when I had a game screen on with firefox browser on top of it.

Thanks for all the help.

 

[zigzag3143]

New BSOD screen. Said Bad pool sector. It was during when I was idling when I had a game screen on with firefox browser on top of it.

Thanks for all the help.

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

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

 

[XplicitMind]

Question: Is it possible to fully wipe my HD and install a fresh OS and maybe it'll go away? Also I tried to run memtest86+ with a USB but apparently it doesn't work even if I go into my BIOS and set it to 1st boot.

 

[zigzag3143]

Question: Is it possible to fully wipe my HD and install a fresh OS and maybe it'll go away? Also I tried to run memtest86+ with a USB but apparently it doesn't work even if I go into my BIOS and set it to 1st boot.

If it is software perhaps.

Did you format the USB stick to bootup?

 

[XplicitMind]

Update: I guess that clean install didn't work. The first day it didn't seem like much problems. When I woke up this morning, a restart before coming onto the desktop and a few minutes later, a BSOD happens. Says system service exception. Have the required files attached.

Thanks.

 

[zigzag3143]

Update: I guess that clean install didn't work. The first day it didn't seem like much problems. When I woke up this morning, a restart before coming onto the desktop and a few minutes later, a BSOD happens. Says system service exception. Have the required files attached.

Thanks.

Inconclusive. If clean install didnt fix it, and you have installed NOTHING ELSE BUT THE OS, it is probably hardware.

Start here:

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

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

 

[XplicitMind]

I have done the memtest. After 5 passes no errors. Not sure if leaving it any longer would have made a difference.

I'll try to do the driver verifier.

Question: To me it sounds like a harddrive issue. Would replacing the harddrive resolve this issue or it could be anything else? Cause the RAM sticks passed so I dunno what else it could be.

 

[XplicitMind]

I also noticed that when I start up after turning off my computer for a while, it usually freezes as it loads up and restarts itself once then a couple of minutes after that, it BSOD to different kind of BSOD screens then usually fine after that. Right now I just started it up again after it was off for a while and it froze as soon as it was loading and had to manually restart the computer and as I was typing my issue on this post right now, it gave me a BSOD screen of a kind I haven't seen before, Memory management.

I'm starting to notice a trend here. I'm actually currently going to do the Driver Verifier. Hopefully I'll have new minidumps for you. Thanks again.

 

[XplicitMind]

Update: Device Verifier on. When I restarted, my pc preformed a chkdsk and deleted alot of corrupted files and restored or orphaned certain files back or whatever that means. Just bits and pieces of information hoping that means anything.

 

[zigzag3143]

I also noticed that when I start up after turning off my computer for a while, it usually freezes as it loads up and restarts itself once then a couple of minutes after that, it BSOD to different kind of BSOD screens then usually fine after that. Right now I just started it up again after it was off for a while and it froze as soon as it was loading and had to manually restart the computer and as I was typing my issue on this post right now, it gave me a BSOD screen of a kind I haven't seen before, Memory management.

I'm starting to notice a trend here. I'm actually currently going to do the Driver Verifier. Hopefully I'll have new minidumps for you. Thanks again.

Inconclusive. Either verifier was not enabled or verifier did not catch a mis-behinvg drive.

You can check the status of verifier by typing verifier /query. It will tell you what drivers it is watching.

 

[XplicitMind]

Inconclusive. Either verifier was not enabled or verifier did not catch a mis-behinvg drive.

You can check the status of verifier by typing verifier /query. It will tell you what drivers it is watching.

Oh that time the driver hasn't been enabled, which i attached a minidump of just a regular bsod, but now it is. I'm just waiting for something to act up.

EDIT: when i typed in verifier /query. it shows the cmd prompt but then quickly disappears. suppose to happen?

 

[zigzag3143]

Inconclusive. Either verifier was not enabled or verifier did not catch a mis-behinvg drive.

You can check the status of verifier by typing verifier /query. It will tell you what drivers it is watching.

Oh that time the driver hasn't been enabled, which i attached a minidump of just a regular bsod, but now it is. I'm just waiting for something to act up.

EDIT: when i typed in verifier /query. it shows the cmd prompt but then quickly disappears. suppose to happen?

Apologies, try this

 

[XplicitMind]

Okay I wake up this morning and it did the same thing again. It freezes at the BIOS screen then I would have to manually restart it. It goes to the desktop and after a few minutes, it would BSOD. special pool system memory management i believe. so I went to see if there was a minidump for it but I only see the one that was made from yesterday. Should my minidump be set up to kernal dump or small memory dump? does it make a difference? I believe it was the same one from yesterday, i couldnt get a minidump from that cause it didnt save.

my verifier is on but only one doesn't get loaded. i attached a picture for you to look at.

Usually after it freezes on the BIOS screen and BSOD's during the first few minutes, it doesnt BSOD again unless I play a game or something. But it gets so annoying to go through that. Like it messes up my PC more and more everytime it does it and I have no idea how to stop it.

 

[zigzag3143]

Okay I wake up this morning and it did the same thing again. It freezes at the BIOS screen then I would have to manually restart it. It goes to the desktop and after a few minutes, it would BSOD. special pool system memory management i believe. so I went to see if there was a minidump for it but I only see the one that was made from yesterday. Should my minidump be set up to kernal dump or small memory dump? does it make a difference? I believe it was the same one from yesterday, i couldnt get a minidump from that cause it didnt save.

my verifier is on but only one doesn't get loaded. i attached a picture for you to look at.

Usually after it freezes on the BIOS screen and BSOD's during the first few minutes, it doesnt BSOD again unless I play a game or something. But it gets so annoying to go through that. Like it messes up my PC more and more everytime it does it and I have no idea how to stop it.

OK verifier is checking drivers. DO you have any new DMP files?

 

[XplicitMind]

I don't. The BSOD I just had said it wrote a DMP but I'm looking at the folder right now and it's not there. Can it be somewhere else?

EDIT: Noticed it was set to Kernal Memory Dump. I set it back to Small Memory Dump. Usually around this time I don't suffer any BSODs but when I do I'll post one up. I just woke next time it saves the next DMP.

 

[zigzag3143]

I don't. The BSOD I just had said it wrote a DMP but I'm looking at the folder right now and it's not there. Can it be somewhere else?

EDIT: Noticed it was set to Kernal Memory Dump. I set it back to Small Memory Dump. Usually around this time I don't suffer any BSODs but when I do I'll post one up. I just woke next time it saves the next DMP.

You can search for *.DM, and they are sometimes in c:\windows and may be called MEMORY.dmp

 

[XplicitMind]

I don't. The BSOD I just had said it wrote a DMP but I'm looking at the folder right now and it's not there. Can it be somewhere else?

EDIT: Noticed it was set to Kernal Memory Dump. I set it back to Small Memory Dump. Usually around this time I don't suffer any BSODs but when I do I'll post one up. I just woke next time it saves the next DMP.

You can search for *.DM, and they are sometimes in c:\windows and may be called MEMORY.dmp

This MEMORY.dmp file is over 400MB and it won't let me put it into a .zip

How can I go about this?