BSOD only after long time without power supply, 0x0000001E

[200g]

Hi,
I´ve had my computer for exactly one year now.
The parts were all new and a friend of mine built it for me.

The problem occurs kind of strange:
If the computer is shut down and disconnected from the power supply for about 5 hours or longer I get a bluescreen right after the windows boot screen. Otherwise it starts without problems and works fine.
My workaround for the problem after long shut down is to switch on the power supply, then immediately switch it off and then on again. This works always fine!

My System:
Windows 7 Home Premium 64bit SP1
AMD Phenom II X6 1090T Black Edition
Asus M4A89GTD PRO/USB3
4GB (2x2) 1333-777 RAM
ATI Radeon HD 5570

Blue Screen:
*** STOP: 0x0000001E (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

I already used all of the windows debugging, diagnostic tools and Memtest but without success.

I hope you can help me.
thanks

 

[JMH]

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

When you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.

http://www.magiciso.com/download.htm

 [B]
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2 
*** WARNING: Unable to verify timestamp for sptd.sys 
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys  
[/B]

 

[200g]

Thanks for the advice JMH, but the problem is still the same. After removing Daemon Tools and using the SPTD uninstaller only the blue screen changed:

*** STOP: 0x00000024 (0x00000000001904FB, 0xFFFFF88002B28068, 0xFFFFF88002B278C0, 0xFFFFF880012D80F3)

*** Ntfs.sys - Adress FFFFF880012D80F3 base at FFFFF8800120F000, Datestamp 4d79997b


I also attached the new dmp file.
Hope that helps, thanks.

 

[JMH]

These two November crashes were caused by memory corruption.
I see you updated to SP1 between the first crashes & last.

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

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/Windows 7 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


3 - Run a SFC as well please.
Read here for more information
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[200g]

Ok, thanks again JMH. I will try these things and report then.

But i detected a different problem:
The Motherboard has overall 4 dram slots. Two blue ones (A1, B1) and two black ones (A2, B2). Refering to the manual it says:
• 1 DIMM: Supports one (1) module inserted into any slot as Single-channel memory configuration.

• 2 DIMMs: Supports two (2) modules inserted into either the blue slots or the black slots as one pair of Dual-channel memory configuration.

• 4 DIMMs: Supports four (4) modules inserted into both the blue and the black slots as two pairs of Dual-channel memory configuration.

But when i put the two rams in the black slots, the computer doesn´t boot. Maybe I should try a Bios update and then test it with the Memok button of the board? If it doesn´t work, there might be an issue with the board itself?

 

[zigzag3143]

Ok, thanks again JMH. I will try these things and report then.

But i detected a different problem:
The Motherboard has overall 4 dram slots. Two blue ones (A1, B1) and two black ones (A2, B2). Refering to the manual it says:
• 1 DIMM: Supports one (1) module inserted into any slot as Single-channel memory configuration.

• 2 DIMMs: Supports two (2) modules inserted into either the blue slots or the black slots as one pair of Dual-channel memory configuration.

• 4 DIMMs: Supports four (4) modules inserted into both the blue and the black slots as two pairs of Dual-channel memory configuration.

But when i put the two rams in the black slots, the computer doesn´t boot. Maybe I should try a Bios update and then test it with the Memok button of the board? If it doesn´t work, there might be an issue with the board itself?

OK with dimms (dual inline memory modules) you fill the "A" slots first (both of them) before you fill the "B" slots.

If you have nothing in the "A" the "B" may not work

Check your owners for the lost accurate (or asK the mfr) answer.

Did you have something in a when you tried b?

 

[200g]

Thanks for your reply.

OK with dimms (dual inline memory modules) you fill the "A" slots first (both of them) before you fill the "B" slots.

Ok, but in the manual it says, if you have 2 ram modules you should put them into A1, B1 (blue) or in A2, B2 (black). Refering to your post this is wrong?

 

[zigzag3143]

Thanks for your reply.

OK with dimms (dual inline memory modules) you fill the "A" slots first (both of them) before you fill the "B" slots.

Ok, but in the manual it says, if you have 2 ram modules you should put them into A1, B1 (blue) or in A2, B2 (black). Refering to your post this is wrong?

While the manual is the ultimate guide, why would you want to put ram the in a2 & b2 before you populated the a1 & b1?

 

[SledgeDG]

My workaround for the problem after long shut down is to switch on the power supply, then immediately switch it off and then on again. This works always fine!

Looks to me as if you need a new power supply. One or more capacitors short out/ don't hold their charge, causing the supplied power during boot up to be instable, which in turn also could trigger a BSOD (normally you would get a POST error though). Certain types of capacitors (MP types) are able to "heal" themselves. Which would explain why it works after the initial power up. I admit that this is just a (my) theory at this point, so before you go all out and buy a new PSU see if you can borrow one to check if that strange behavior changes.

-DG