P5QL-CM Fresh W7x64 BSOD after COLD Wake/Start

Windows 7 SP1 x64 Pro or Enterprise (tried both)
Not-yet-activated (no need, I'm trying to resolve before actually activating...)

The build is hmmm a bit more than 2 years old. All errors are with FRESH installs + SP1 + Updates.
ASUS P5QL Latest BIOS (was also same problem before with previous one)
Core2Duo #7300 CPU
2x1TB Disks in Stripe
1xSSD 120GB OCZ Vertex3 (also had another simple sata2 and tried a PATA disk... same problem)
1xSATA DVD-RW
2x2GB Ram (Tested ok for 6h+)
1xNVIDIA GeForce 9800 GPU (that I can play for hours with, no problem).


Soooo... the problem:

Having my computer on I can play or even run CPU, disk and whatever burn-in tests for hours... system happily chewing on everything I throw @ it.
I turn it off for a few hours (say night but it's not needed to be that long) and turn it on to do something... it will reboot automatically on just when windows animation would be... and it's back on bios. Then it will go into the "safe mode" selection (because of the previous crash) and if I immediately choose to boot normally it will BSOD, minidump and reboot. If I keep it on the selection screen for 30seconds-1m... it will happily boot... but if I don't and I constantly immediately "normal boot" it can reboot like 10 times before it will actually work...

Same thing happens with waking from sleep...

Please help! Proper help files attached and will happily try anything you need and haven't already done!


Andreas - McX

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.

RAM - Test with Memtest86+



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.

Driver Verifier - Enable and Disable


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

MemTest doesn't produce any errors.

I did run the verifier with the options listed... does that produce any logs or anything? I applied the settings, did a reboot, made the computer sleep and left it 30 seconds and it woke up fine... then made it sleep again and let it cool down for 15 minutes... and tadaaaa... BSOD again...

The bugcheck says:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff96000104053, 0xfffff88006ab2f70, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121711-11200-01.

What do you need me to provide? I included the standard as I did before that includes the latest minidump and I also have a (much bigger) memory.dmp available that I can upload somewhere if you need it.

Did you notice the part that the system MUST BE COLD-BOOTED to produce this? other than than I can reboot/boot/wake 100 times *hot* without a single problem...

This smells like hardware and/or a very low level problem like ACPI or AHCI etc... to me... but I can't put my finger on it... and call it a day...

Again... THANK YOU for your advice/help :)

Andreas

Any ideas? I'm lost for weeks now... on this

mcx said:

MemTest doesn't produce any errors.

I did run the verifier with the options listed... does that produce any logs or anything? I applied the settings, did a reboot, made the computer sleep and left it 30 seconds and it woke up fine... then made it sleep again and let it cool down for 15 minutes... and tadaaaa... BSOD again...

The bugcheck says:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff96000104053, 0xfffff88006ab2f70, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121711-11200-01.

What do you need me to provide? I included the standard as I did before that includes the latest minidump and I also have a (much bigger) memory.dmp available that I can upload somewhere if you need it.

Did you notice the part that the system MUST BE COLD-BOOTED to produce this? other than than I can reboot/boot/wake 100 times *hot* without a single problem...

This smells like hardware and/or a very low level problem like ACPI or AHCI etc... to me... but I can't put my finger on it... and call it a day...

Again... THANK YOU for your advice/help :)

Andreas

Most obvious thing that jumps out is this

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

GianniDPC said:

Go to power settings> (go to your energie scheme)> advanced and then choose sleep mode and disable hyrbid sleep and see if it BSOD's or not. ,
Gianni

That didn't help ether...

zigzag3143 said:

Most obvious thing that jumps out is this

Asacpi.sys

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

When I ran that installer... it gave me an immediate BSOD. On reboot it was fine and keeps having the same problem as before... (only waking from sleep/hybernation or shutdown... COLD).

I'm attaching the latest minidumps etc in the proper format and a snap of my ATK driver... hope it helps?!?

Andreas

It is for vista but I will give a try with all devices removed to see if it helps...

Nothing... Running MemCheck from cold boot doesn't produce errors ether (I read on some other posts that this might be the case...)

I also tried with nothing but system disk on... sheesh... I'm out of ideas... really.

Re-Uploading latest minidumps etc, in case someone wants to take another look...