BSOD when booting windows,almost every cold boot.

[deathwing911]

hi i got a 3 years old machine and all was working great,but now ( this month) i have multiple BSOD . i have recently replace my power supply for a 650 w it worked until i had those BSOD but now only on cold boot

*recently reinstall win 7 64 bit home premium to see if it will worked, but no luck

here my pc stats :
Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 10/14/09 14:43:46 Ver: 05.01
Processor: AMD Phenom(tm) II X4 965 Processor (4 CPUs), ~3.4GHz
Memory: 4096MB RAM
Available OS Memory: 4096MB RAM
Page File: 1582MB used, 6606MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode


and i got a SF dump files.
thanks .
-GAb

 

[JMH]

Hello there,

This is probably your problem...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 (not before).

 

[deathwing911]

may i add that my motherboard is a asus m4a785td-v-evo. (will try to find that for my model) thanks for the quick respond.

just find out the ATK010 for my mobo but now after my cold boot this morning i had an other BSOD this time a "BAD_POOL_HEADER" crash i got a newer dump here:

 

[deathwing911]

may i bump please .

 

[JMH]

Apologies. :shock:
You should not have been overlooked.

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.

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

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 "Special Pool", "Force Pending I/O Requests" and "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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

 

[deathwing911]

thanks for not letting me down , so far iv done all the procedure you told me to do and no problems has appeared for the memory test ,and i tested the ram by removing one and try it and vice versa. its all working great. So my thoughts too are driver related. By removing those off-line what do you mean ? (sry, im noob in the crash / diagnostic side of the computer). does it mean that i just need to delete those files manually? .
all i can do is give ya a other dumps here :

 

[JMH]

I am going to get my partner to help you. He is a whiz.....
Have to go offline now.
Night.

 

[zigzag3143]

thanks for not letting me down , so far iv done all the procedure you told me to do and no problems has appeared for the memory test ,and i tested the ram by removing one and try it and vice versa. its all working great. So my thoughts too are driver related. By removing those off-line what do you mean ? (sry, im noob in the crash / diagnostic side of the computer). does it mean that i just need to delete those files manually? .
all i can do is give ya a other dumps here :

Deathwing hi and welcome.

Ok lets get some terminology straight so we both are on the same page.


RE: Memtest. How many passes did you complete? Remember 6-8 at a minimum and also remember they test both the ram and the motherboard sots.

Re: Verifier. None of your DMPS show verifier was enabled when the crash occured can you type verifier /query and tell us what drivers are being verified?

I am pretty sure it is a driver and that is what verifier is for.

Ken

 

[deathwing911]

alright thanks zigzag , ill do it and let you inform .

 

[zigzag3143]

alright thanks zigzag , ill do it and let you inform .

No problems. Let u s know if you need help


ken

 

[deathwing911]

ok the verifier is running and i have check all the non microsoft drivers and i t has not crash yet so what i need to do now ?
PS : for the driver list ,where is the dump file of the verifier ?

 

[zigzag3143]

ok the verifier is running and i have check all the non microsoft drivers and i t has not crash yet so what i need to do now ?

Wait.!! I have seen it take 36 hours or more. When it finds the driver it is supposed to, and will, crash. Upload that DMP file.

 

[deathwing911]

sorry for noob question but where will the dump file be when it crash ?
or it is just the same diump as the sf .

 

[zigzag3143]

sorry for noob question but where will the dump file be when it crash ?
or it is just the same diump as the sf .

If configured as below it should be in c:\windows\minidump


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.

If you are overclocking STOP

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.

 

[deathwing911]

here you go ken :

 

[zigzag3143]

here you go ken :

Driver verifier does not seem to be enabled when these crashes occurred. Are you sure you are following the instructions carefully?


It is also possible verifier did not catch the bad driver, which sometimes happens. Keep verifier running.

 

[deathwing911]

ok , it has not crash yet this is a dump of a previous crash . But the verifier is up and still running ill try to make it crash today when im gonna cold boot it ( because its the only time it crash).

 

[zigzag3143]

ok , it has not crash yet this is a dump of a previous crash . But the verifier is up and still running ill try to make it crash today when im gonna cold boot it ( because its the only time it crash).

No new dmp. Where did you put it?

 

[deathwing911]

theres no new dumps , because this morning when i cold boot it , strangely it dint crash at all :O. So i cant provide ya the crash info "yet".(its like uncheck microsoft driver verifier did something dunno).But it will surly crash sometimes soon, it will be too good to be true lol .Ill keep ya inform for further dumps files when it crash.

 

[zigzag3143]

theres no new dumps , because this morning when i cold boot it , strangely it dint crash at all :O. So i cant provide ya the crash info "yet".(its like uncheck microsoft driver verifier did something dunno).But it will surly crash sometimes soon, it will be too good to be true lol .Ill keep ya inform for further dumps files when it crash.

We are both here if it does crash