BSOD after Hibernate! (maybe only on X2 Dualcore)

[Thels]

I have the same try that I get a "0X0000001D with a IRQL_NOT_LESS_OR_EQUAL" BSOD whenever I try to enter hybernate mode. I know now it's related to Daemon Tools, as I tried reпnstalling with several configurations and everything works fine, until I install Daemon Tools. Note that uninstalling Daemon Tools doesn't fix the problem. Once I have it, I have it.
I'm running Windows 2K on a P5ND2-SLI system with Intel P4 3Ghz processor, 2 gigs of memory and Dual GeForce 7800 GT in SLI mode. There is an ASUS DRW-1604P DVD Rewriter as primary on my 2nd IDE port and 2 identical harddisks combined into an Nvidia Stripe disk on my NVIDIA nForce4 Intel@ Edition Serial ATA RAID Controller. Everything else is on board.

1.47 fixed my problem cheers!

[tentonine]

1.47 works with nforce4 RAID for me too. I have had this problem with a single core Athlon 64 for some time. I hadn't even thought that it could be due to Daemon tools until I checked the home page recently and read the change log.

[Mykos]

works with NV4 Raid. THX!!

[Copytrooper]

Anyone tried SPTD layer v1.47 yet?

[Mykos]

Hi there,

I have the same problem. After installing DT (doesn't matter sptd 1.43 or sptd 1.45) i get bsod.

[strategy_fan]

SPTD v1.45 fixes some strange bug causing issues with quite some programs including Nero, EAC, WinAmp etc., so it is highly recommended to update to v1.45. Maybe it fixes the hibernation issue for some of you guys with problems, too.

Nope, same problem still occurs.

[Copytrooper]

SPTD v1.45 fixes some strange bug causing issues with quite some programs including Nero, EAC, WinAmp etc., so it is highly recommended to update to v1.45. Maybe it fixes the hibernation issue for some of you guys with problems, too.

[Klueless]

I have the same problem with DAEMON Tools (4.09 x86, STPD 1.43). I have not tried with STPD 1.45. Why would you suggest 1.45? It's not listed for download by Duplex Secure (http://www.duplexsecure.com/downloads).

I'm running X2 4400+, A8N32-SLI, RAID 0 over SATA, and 7900 GS with Windows XP SP2.

What else would you need to debug this problem?

[Copytrooper]

Anyone tried v1.45 yet?

[strategy_fan]

Detailed problem reproduction description:

I just clean formatted my system, here are the specs:

Athlon 64 3000+
DFI LanParty UT NF3 250gb
4 SATA Hard drives
3 PATA Optical drives

The following software is installed:

Windows XP Professional x64 Edition with Service Pack 2
NVIDIA official nForce3 RAID drivers v6.25
NVIDIA official nForce3 Ethernet drivers v6.25
Realtek AC'97 Drivers version A3.99

I then proceeded to install Daemon tools. After the first part of the installation, after the computer had restarted, I tested to see if hibernate worked. It did not work. It caused a BSOD as described by the above poster. Daemon tools was not installed at this point, only the SPTD layer. I hope this helps.

[P.A.W]

I was running on a fresh install of windows xp sp 2 with a single core processor and was having the stop error while hibernating issue:

Driver_IRQL_NOT_LESS_OR_EQUAL
Stop: 0x000000d1 (0x00000000, 0x000000FF, 0x00000008, 0x00000000)

the problem was resolved the very instant i uninstalled sptd layer 1.43.

[Copytrooper]

Anyone of you with hibernation issue did try SPTD layer v1.43 yet?
Also did you try with SPTD installed only, i.e. without Daemon Tools and/or Alcohol installed, but SPTD running?

[Dave_M_26]

Hmmm...

I've now discovered that the minidump is initially created within the pagefile on the C: drive and is only copied to the minidump folder on the next boot. Handy!

I'll have to look into sending the debug info through the serial port. I've no idea what's needed for that, but I'll look into it. If anyone's got any other ideas, I'm open to suggestion.

Dave

[Dave_M_26]

Unfortunately (probably due to the issue with writing to disks) the minidump has not been created. However, I see that I can change where the minidump is saved, so I'll attach a PATA drive tonight and try again.

Dave

[Jito463]

Check your Windows\minidump directory for the latest minidump file (they're named by creation date). If one exists, you could send it to support@daemon-tools.cc to have them analyze it for you. That may lead to a more definitive source of the problem.