x64 BSOD after "sleep"

[Sven]

First I used Win7 x86 RC1, and no problems with sleeps. Just moved on to Win7 RC1 x64, and sometime after "sleep" it shows the desktop very briefly, then BSOD. Not the same STOP code every time, but the error-name allmost everytime has the word KERNAL in it.
As the STOP-code changes, how do I track this error? (I totally newbie to x64 OS)

 

[Hammerhead786]

Have you checked the event viewer for any errors? Can you upload the minidump files anywhere so someone can have a look at them? Are you using native Win 7 drivers?

 

[Sven]

Where do I find this minidump file?
Yes all drivers are for Windows 7, but I have installed Daemon tools, Rivatuner (as monitoring and fan-profile, as it can't OC because of Windows 7 drivernatur) along with Kaspersky 8.0.0.181 beta (should be compatible with Windows 7 recording to Kaspersky)

 

[Hammerhead786]

Minidumps are created in C:\Windows\minidump.

 

[usasma]

Also, since this is sleep related, try updating your video drivers through Windows Update or from the video chipset manufacturer's website (ATI, nVidia, Intel, etc).

 

[Sven]

I have tried all day to re-create the error, but every time I'm wakening the PC it works. I'll be back if/when the error reoccur

 

[JDog]

Also, since this is sleep related, try updating your video drivers through Windows Update or from the video chipset manufacturer's website (ATI, nVidia, Intel, etc).

I agree here. I put Windows 7 RC on a Dell Latitude D830 laptop. It would constantly crash when it came out of sleep mode. I would also see corrupted display with Aero. I went into the Device Manager and forced it to search for updated drivers for the 965GM chipset and it installed them. No more BSODs and display is perfect.

 

[ollie007]

I agree here. I put Windows 7 RC on a Dell Latitude D830 laptop. It would constantly crash when it came out of sleep mode. I would also see corrupted display with Aero. I went into the Device Manager and forced it to search for updated drivers for the 965GM chipset and it installed them. No more BSODs and display is perfect.

there is a recent 965 driver, and it may help others

 

[Sven]

Now I have a minidump file from a BSOD after waking up from "sleep mode", but I don't know where to upload it. Any ideas?

 

[Hammerhead786]

Just zip it up and add it as an attachment in your message.

 

[Sven]

OK, that's easy

I hope you can get some sence out of this file

 

[Hammerhead786]

WhoCrashed shows:

On Thu 14/05/2009 22:25:25 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xFFFFF8A00BBC80C0, 0xFFFFFFFFC0000006, 0x77403518, 0x232E590)
Error: [FONT=Segoe UI, Arial]STATUS_SYSTEM_PROCESS_TERMINATED[/FONT]
[FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.[/FONT][/FONT]

I would suggest a clean install of Windows 7 using native drivers and seeing if the problem persists. Use Windows update to find any driver updates. This may be a driver or an application issue.

 

[Sven]

Driver ... the only driver that is comming from outside and is not WHQL is Creative X-Fi soundcard. Could it be this?

Other installed driver is Nvidia 185.85 WHQL 64 bit. All other drivers are native.

Or could it be Daemon tools Lite, allthough they claim that it is compatible with Windows 7? I don't know if a program like Daemon tool will give this kind of error, but a lot of people have problems with daemon tool. I just don't know any other program that can do the same job.

 

[Hammerhead786]

If the soundcard is an add-in card, then I would suggest un-installing the drivers and physically removing it to see what happens. If the problem still occurs then I would suggest removing Daemon tools Lite. Do you have the latest bios update? If not I'd suggest updating the bios as well.

 

[Sven]

Newest BIOS yes. I will try and remove daemon tool first, as I can't predict when the error occur, i.e. I can put it to sleep 10 times and nothing happens, and then suddently it is there (it seems allways to show up, when I'm in a hurry, and never when I do it for test ).

How do I find another program that can mount ISO-images and that has no issues with Windows 7? I don't need all Daemon tools "overwriting" of copyprotections, as I'm using it for pictures, videos and backup-databases, so all I need is a "mounting"-program to ISO and IMG files. I don't even know what that kind of programs is called in English, so I can't search for it.

 

[Hammerhead786]

Sven, have a look at this:

SlySoft Virtual CloneDrive

I've never used it so I can't comment on how good it is or isn't. It is freeware and it supports Win 7.

 

[Sven]

That seems to be a great succes! The program is small and ultra fast, and I have now put it to sleep and wake 5 times, and no error.

I'll be back if the error reoccur.

Thank you for the link to this sweet little program

 

[usasma]

Just got a new Intel integrated chipset/video driver from Windows Update today. Try that one if it's an Intel chipset.

 

[toolboxnj]

Hate to bump an old thread, but I have the same issue. BSOD while in sleep mode.

Looked at the minidump file and it looks like ntoskrnl.exe is the culprit. I never heard of this file.

I went into device manager and cleared out all the "problem" devices. Running the Win7 RC.

Thanks

 

[usasma]

toolboxnj - Please start your own thread. Each issue is different and it's easier to work on an individual issue in it's own thread.

FWIW - ntoskrnl.exe is a core Windows file. So if it was the cause of the problem you'd likely have more problems than just a BSOD. Often the offending driver has exited before it's command crashes ntoskrnl.exe (or other core Windows files).

When you start your new thread, please zip up and upload/attach the contents of your C:\Windows\Minidump folder in a .zip file.