x64 BSOD after "sleep"

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 236
    Windows 7 Ultimate x64
    Thread Starter
       #11

    OK, that's easy

    I hope you can get some sence out of this file
      My Computer


  2. Posts : 125
    Win 7 RC
       #12

    WhoCrashed shows:

    On Thu 14/05/2009 22:25:25 your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xFFFFFFFFC000021A (0xFFFFF8A00BBC80C0, 0xFFFFFFFFC0000006, 0x77403518, 0x232E590)
    Error: STATUS_SYSTEM_PROCESS_TERMINATED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


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


  3. Posts : 236
    Windows 7 Ultimate x64
    Thread Starter
       #13

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


  4. Posts : 125
    Win 7 RC
       #14

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


  5. Posts : 236
    Windows 7 Ultimate x64
    Thread Starter
       #15

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


  6. Posts : 125
    Win 7 RC
       #16

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


  7. Posts : 236
    Windows 7 Ultimate x64
    Thread Starter
       #17

    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 :)
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #18

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


  9. Posts : 1
    Windows 7 RC
       #19

    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
      My Computer


  10. Posts : 5,705
    Win7 x64 + x86
       #20

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


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:12.
Find Us