BSOD on shutdown - ntoskrnl.exe

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Jamrock, Jun 9, 2010.

  1. Jamrock

    Jamrock New Member

    Joined:
    Dec 30, 2009
    Messages:
    8
    Likes Received:
    0
    Hello,

    I fairly recently built my own computer and it has been working great except for the occasional BSOD on shutdown. I will shutdown the computer, and it will hang on shutting down for quite some time.. 15+ minutes, and then it will go to a DRIVER_POWER_STATE_FAILURE BSOD. I use the program BlueScreenView to inspect the minidump files and more often than not the BSOD is related to the ntoskrnl.exe . Sometimes there are other files involved, but ntoskrnl.exe is always one of them.

    Once it was hal.dll, tcpip.sys, win32k.sys, atipmdag.sys, and ntfs.sys. Ntoskrnl.exe was always mentioned in BlueScrenView along with one of these, more recently it was only Ntoskrnl.exe .

    This only started happening fairly recently, and for a couple months after building the computer I never had any of these problems.

    Something worth mentioning. I use the program ReadyDriverPlus to automatically disable Driver Signature Enforcement for Win7 so I can use the ATI Tray Tools program to better control my graphics card. I had a slight mishap when installing this program, and I uninstalled it (via control panel) and every time I started up the computer from then on out it would automatically go to the screen during startup where you can select "Disable driver signature enforcement" and "Safe mode" and the other startup options. It would not automatically select driver signature enforcement now that it was uninstalled, but the screen would pop up and it would show ReadyDriverPlus next to Windows 7 on the startup screen mentioned. So some files must have lingered after un-install.

    I installed ReadyDriverPlus again, and now each time the computer starts up it will got to that screen and instead of showing one ReadyDriverPlus entry it will show two, next to the Windows 7 selection.

    I am not sure if this has caused some of the issues or not, if I knew a way to completely remove the lingering settings for this program I would. Although, as I said I am not sure this is an issue.

    I am an advanced user, and know quite a bit about computers and how they work. I am not sure if this is a hardware issue, or something else. I have run MemTest86 for ~12 hours and no issues showed up so there is that.

    Computer specs:
    i7-920 @ 4.0 ghz
    ATI 5970HD
    3 x 2GB OCZ DDR3 RAM running @ 1600mhz (advertised running speed)
    Asus P6T Deluxe V2 mobo
    Auzentech Prelude X-fi 7.1 sound card
    2x Samsung Spinpoint F3 1TB HDD's
    1x Western Digital Caviar Black 1TB HDD
    Antec 1200 Tower Case
    Win 7 x64

    Thanks in advance.
     

    Attached Files:

    #1 Jamrock, Jun 9, 2010
    Last edited: Jun 9, 2010
  2. pcs3657

    pcs3657 New Member

    Joined:
    May 6, 2010
    Messages:
    210
    Likes Received:
    13
  3. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    When you put the overclock back to a normal speed and reset your system to the normal parameters, do the blue screens continue?

    Have you uninstalled the Driver Signature Over ride program and not selected over ride? Surely there must be up to date Win 7 drivers for a 5970.

    Anything in the Event Viewer that might help identify the problem, such as error or warning messages?

    What type of temps have you been showing for the CPU while overclocking?
     
  4. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Hi. You are getting an error with your notorious Creative drivers.

    Code:
    FAILURE_BUCKET_ID:  X64_0x9F_3_ctaud2k_IMAGE_pci.sys
    
    Please see this thread about using proper ones as it should help.

    Creative Sound Cards. - Windows 7 Forums

    Or if your Auzentech Prelude X-fi 7.1 sound card relies on Creative drivers, then update the software for that.

    I also noticed you have DaemonTools installed which is even more notorious for crashing systems. Please uninstall it and then remove the sptd.sys with the installer/uninstaller found here (must do for stability):

    DuplexSecure - Downloads

    A great stable replacement for drive emulation is PowerIso.

    PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive
     
    #4 TorrentG, Jun 9, 2010
    Last edited: Jun 9, 2010
  5. Jamrock

    Jamrock New Member

    Joined:
    Dec 30, 2009
    Messages:
    8
    Likes Received:
    0
    These are the most up-to-date creative drivers, well almost.. it is a consumer-made driver because the most up to date BETA drivers (that's all, last update was july 2009) have an issue with sound popping/crackling.

    I will un-install Daemon Tools and use that program thanks, willing to try anything atm but I am worried it may be some sort of hardware failure.

    CPU temps are fine. It's 50C, 44C, 45C, 47C for all four cores according to RealTemps with 5% load.

    I will try resetting the CPU clocks back to normal I guess for a few days.. although it's pretty necessary as my 5970 will be pretty bottle necked with default clocks.

    I have also un-installed ReadyDriver Plus and no longer enforce driver signature enforcement. This hasn't made a difference in BSOD's yet however.

    I am a bit worried it may be some type of hardware failure but I am not sure.. my 5970 has been a bit dodgy lately.. not OC'ing well if at all, red/grey lines on the screen when un-installing drivers.. forcing me to hard-reboot. I have run Furmark for quite some time with no issues however.. so I am not sure.

    Starting to run out of ideas... :frown: . Is there a fairly easy way for me to test all of my components to check for hardware failure? Hardware failure of any kind could cause BSOD's with any varying amount of files listed as possible causes in BlueScreenView right?
     
  6. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Not to worry. It is for sure your Creative drivers causing issues. They are notorious and showing in WinDbg (professional debugger.)

    You have to do something about that to alleviate bsod.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\Temp\Rar$DI00.525\060810-24804-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`03006000 PsLoadedModuleList = 0xfffff800`03243e50
    Debug session time: Tue Jun  8 22:03:49.685 2010 (UTC - 4:00)
    System Uptime: 1 days 8:36:57.934
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................................
    Loading User Symbols
    Loading unloaded module list
    .....................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8006323a20, fffff80000b9c518, fffffa8009188280}
    
    Probably caused by : pci.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8006323a20, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa8009188280, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000f91000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`030e51b3 : 00000000`0000009f 00000000`00000003 fffffa80`06323a20 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`030826a6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
    fffff800`00b9c570 fffff800`03081a26 : fffffa80`08ec2c68 fffffa80`08ec2c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`0308257e : 00000111`628ae795 fffff800`00b9cc58 00000000`0072d956 fffff800`031f3d48 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`03081d97 : 0000006a`ca9f26c3 0000006a`0072d956 0000006a`ca9f260d 00000000`00000056 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`0307edfa : fffff800`031f0e80 fffff800`031fec40 00000000`00000000 fffffa80`073760f0 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_ctaud2k_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_ctaud2k_IMAGE_pci.sys
    
    Followup: MachineOwner
    ---------
    
    
     
  7. Jamrock

    Jamrock New Member

    Joined:
    Dec 30, 2009
    Messages:
    8
    Likes Received:
    0
    Crossing me fingers here heh, I had gotten rid of ATITool and some other programs that were showing up on the bugcheck. I am working on finding a way to install the Beta Auzentech drivers, which are the newest released. Which are unfortuantely based on Creative's drivers so looks like i'm stuck with them for the moment.

    Thing is, whenever I try to install the Beta1 driver's after restarting any Creative control panel will say that "the current device is not supported by this application. Closing now." Something along those lines, should have it worked out soon though apparently it is a fairly common issue when installing new Creative drivers.

    Although I removed every trace of Creative's drivers via Driver Sweeper and uninstalled all related Creative components and programs.
     

Share This Page

Loading...