Windows 8 and 8.1 Forums


Bluescreen Error 9F caused by hal.dll

  1. #1

    Bluescreen Error 9F caused by hal.dll


    Hello all,

    I am having another bluescreen issue. I received a 9F error after I resumed my computer to sleep. The issue occurred once before, but between the errors, I had no problems. I have listed my specs below. I have updated windows, updated all drivers from the manufacturers websites, and even clean installed windows again. Any help would be appreciated. This is a new build (about 1 month old now) so there isn't anything I changed hardware wise to cause the error.

    Here are my specs:
    Windows 8 Pro x64
    Asus P8Z77-V Deluxe
    Intel i7 3770K at stock
    16GB RAM
    Sapphire Radeon HD 7950 at stock
    512GB Crucial M4
    2 x 2TB HDD


    Here are the bluescreen details:
    ==================================================
    Dump File : 111212-12937-01.dmp
    Crash Time : 11/12/2012 6:22:35 PM
    Bug Check String : DRIVER_POWER_STATE_FAILURE
    Bug Check Code : 0x0000009f
    Parameter 1 : 00000000`00000003
    Parameter 2 : fffffa80`0c7b6b30
    Parameter 3 : fffff880`0136d7e0
    Parameter 4 : fffffa80`1c717cf0
    Caused By Driver : hal.dll
    Caused By Address : hal.dll+1ce61
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7ad40
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\111212-12937-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 9200
    Dump File Size : 630,352
    ==================================================

    I really appreciate any help solving this as I use my PC for media center recordings and this error results in missed recordings. Otherwise I probably wouldn't care much for this since it has only occurred twice in 2 weeks. Thank you.

      My System SpecsSystem Spec

  2. #2


    Posts : 197
    Win 8 Enterprise RTM


    This one is a bit strange, but ACPI is implicated. Try updating your bios. Try updating the ATK package.

    Code:
    Loading Dump File [C:\Users\xxx\Downloads\SF_12-11-2012\SF_12-11-2012\102812-12718-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols\*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
    Machine Name:
    Kernel base = 0xfffff800`3bc15000 PsLoadedModuleList = 0xfffff800`3bedfa60
    Debug session time: Mon Oct 29 02:21:31.532 2012 (UTC + 1:00)
    System Uptime: 1 days 2:31:48.116
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    .......................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 9F, {3, fffffa800c70eaf0, fffff8003acbd7e0, fffffa8023706e10}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800c70eaf0, Physical Device Object of the stack
    Arg3: fffff8003acbd7e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa8023706e10, The blocked IRP
    Debugging Details:
    ------------------
    
    DRVPOWERSTATE_SUBCODE:  3
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAULTING_MODULE: fffff8003c35e000 hal
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    TAG_NOT_DEFINED_c000000f:  FFFFF8003ACC3FB0
    STACK_TEXT:  
    fffff800`3acbd7a8 fffff800`3bda565e : 00000000`0000009f 00000000`00000003 fffffa80`0c70eaf0 fffff800`3acbd7e0 : nt!KeBugCheckEx
    fffff800`3acbd7b0 fffff800`3bda5691 : fffffa80`1f300bd0 fffff800`3c37ae61 00000000`00000000 00000000`000000e9 : nt!PopIrpWatchdogBugcheck+0xe2
    fffff800`3acbd810 fffff800`3bcbc734 : fffffa80`1f300c08 fffffa80`0c716040 fffff800`3acbdb18 fffff800`3bcbad91 : nt!PopIrpWatchdog+0x32
    fffff800`3acbd860 fffff800`3bcbcd55 : 00000000`00000000 00000000`00004773 00000000`00140001 00000000`000000e9 : nt!KiProcessExpiredTimerList+0x214
    fffff800`3acbd9a0 fffff800`3bcbcc08 : fffff800`3bf0b180 fffff800`3bf0df80 00000000`00000001 00000000`003797d1 : nt!KiExpireTimerTable+0xa9
    fffff800`3acbda40 fffff800`3bcb6cf6 : fffffa80`00000000 00001fa0`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
    fffff800`3acbdaf0 fffff800`3bcbb3fa : fffff800`3bf0b180 fffff800`3bf0b180 00000000`00183de0 fffff800`3bf65880 : nt!KiRetireDpcList+0x1f6
    fffff800`3acbdc60 00000000`00000000 : fffff800`3acbe000 fffff800`3acb8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    STACK_COMMAND:  kb
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    FAILURE_BUCKET_ID:  0x9F_3_ACPI_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  0x9F_3_ACPI_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner
      My System SpecsSystem Spec

  3. #3


    Fairfield County, CT
    Posts : 348
    Windows 7 SP1


    Analysis inconclusive means just that. Usually a hardware error. Test your hard drive, post back with results.
      My System SpecsSystem Spec

  4. #4


    Quote Originally Posted by jmv2009 View Post
    This one is a bit strange, but ACPI is implicated. Try updating your bios. Try updating the ATK package.
    My BIOS is updated. I do not believe I have an ATK package. Based on my search it seems that is for notebooks. But all other drivers/programs from Asus are updated. I'll run a chkdsk on my hard drive and see what turns up.

    If the hard drive is okay, what are other possibilities for this problem?

    Thanks a lot for your responses.
      My System SpecsSystem Spec

  5. #5


    Fairfield County, CT
    Posts : 348
    Windows 7 SP1


    Memory, BIOS, CPU, Overheating, just about anything that hardware can cause.
      My System SpecsSystem Spec

  6. #6


    Quote Originally Posted by richc46 View Post
    Memory, BIOS, CPU, Overheating, just about anything that hardware can cause.
    I ran Memtest86+ after I first installed everything. It passed fine. Does a pass on that test eliminate memory as a potential cause? I haven't had a chance to run chkdsk yet since I need the pc on for media center recordings. But the SMART status is green on all drives.

    At this point I'm thinking of getting a replacement motherboard. I also have another issue with resuming from sleep with an E1 code on the motherboard and fans running at full screen with a blank screen. Hopefully another motherboard solves the issue.
      My System SpecsSystem Spec

  7. #7


    Fairfield County, CT
    Posts : 348
    Windows 7 SP1


    To perform the memory test correctly, you must run for 6 passes and if that passes take each stick and test separately in a good slot
    Smart is fairly reliable.
      My System SpecsSystem Spec

  8. #8


    Quote Originally Posted by richc46 View Post
    To perform the memory test correctly, you must run for 6 passes and if that passes take each stick and test separately in a good slot
    Smart is fairly reliable.
    I've ran the driver verifier. And I'm constantly blue screening on volmgrx.sys upon every startup. Does this narrow down the issue any bit? I've attached the minidump. Thanks for your help.

    Here are the details:

    ==================================================
    Dump File : 111612-4484-01.dmp
    Crash Time : 11/16/2012 7:13:16 PM
    Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
    Bug Check Code : 0x000000c4
    Parameter 1 : 00000000`000000f6
    Parameter 2 : 00000000`000007e8
    Parameter 3 : fffff980`5306a940
    Parameter 4 : fffff803`b28bbe85
    Caused By Driver : volmgrx.sys
    Caused By Address : volmgrx.sys+9cdbcc9
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7a740
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\111612-4484-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 9200
    Dump File Size : 281,896
    ==================================================
      My System SpecsSystem Spec

  9. #9


    Fairfield County, CT
    Posts : 348
    Windows 7 SP1


    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_111612-26859-01.zip\111612-26859-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    Machine Name:
    Kernel base = 0xfffff802`ab687000 PsLoadedModuleList = 0xfffff802`ab951ae0
    Debug session time: Fri Nov 16 22:03:39.704 2012 (UTC - 5:00)
    System Uptime: 0 days 0:00:41.512
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {f6, 158, fffff98067998940, fffff802abac7e85}
    
    Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 00000000000000f6, Referencing user handle as KernelMode.
    Arg2: 0000000000000158, Handle value being referenced.
    Arg3: fffff98067998940, Address of the current process.
    Arg4: fffff802abac7e85, Address inside the driver that is performing the incorrect reference.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_f6
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff802abcce1ac to fffff802ab701740
    
    STACK_TEXT:  
    fffff880`0ad9d038 fffff802`abcce1ac : 00000000`000000c4 00000000`000000f6 00000000`00000158 fffff980`67998940 : nt!KeBugCheckEx
    fffff880`0ad9d040 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!VerifierBugCheckIfAppropriate+3c
    fffff802`abcce1ac cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50875b31
    
    FAILURE_BUCKET_ID:  X64_0xc4_f6_VRFK_nt!VerifierBugCheckIfAppropriate+3c
    
    BUCKET_ID:  X64_0xc4_f6_VRFK_nt!VerifierBugCheckIfAppropriate+3c
    
    Followup: MachineOwner
    ---------

    Strange I looked at the report and it does not agree with your post

    If we go by your post that driver is a Micorosoft Driver and very, very unlikely the cause of the BSOD
      My System SpecsSystem Spec

  10. #10


    Quote Originally Posted by richc46 View Post
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_111612-26859-01.zip\111612-26859-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    Machine Name:
    Kernel base = 0xfffff802`ab687000 PsLoadedModuleList = 0xfffff802`ab951ae0
    Debug session time: Fri Nov 16 22:03:39.704 2012 (UTC - 5:00)
    System Uptime: 0 days 0:00:41.512
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {f6, 158, fffff98067998940, fffff802abac7e85}
    
    Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 00000000000000f6, Referencing user handle as KernelMode.
    Arg2: 0000000000000158, Handle value being referenced.
    Arg3: fffff98067998940, Address of the current process.
    Arg4: fffff802abac7e85, Address inside the driver that is performing the incorrect reference.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_f6
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff802abcce1ac to fffff802ab701740
    
    STACK_TEXT:  
    fffff880`0ad9d038 fffff802`abcce1ac : 00000000`000000c4 00000000`000000f6 00000000`00000158 fffff980`67998940 : nt!KeBugCheckEx
    fffff880`0ad9d040 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!VerifierBugCheckIfAppropriate+3c
    fffff802`abcce1ac cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50875b31
    
    FAILURE_BUCKET_ID:  X64_0xc4_f6_VRFK_nt!VerifierBugCheckIfAppropriate+3c
    
    BUCKET_ID:  X64_0xc4_f6_VRFK_nt!VerifierBugCheckIfAppropriate+3c
    
    Followup: MachineOwner
    ---------

    Strange I looked at the report and it does not agree with your post

    If we go by your post that driver is a Micorosoft Driver and very, very unlikely the cause of the BSOD
    What do you mean? I used bluescreenview and it showed it as volmgrx.sys. Anything else I should do?
      My System SpecsSystem Spec

Page 1 of 4 123 ... LastLast
Bluescreen Error 9F caused by hal.dll
Related Threads
BSOD error 0x0000009f caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hello! My first BSOD occured on my 1-month-old ASUS GL551JM laptop while I was opening the Task Manager. It was running on battery while I was playing Don't Starve Together on Steam. I closed Don't Starve Together and plugged in the charger. 5 minutes later, I noticed the computer being a little...
Bluescreen Error after few hours in BSOD Crashes and Debugging
Hello Guys, i have a problem with my new Gamer Laptop (MSI GE70 2Pe Apache Pro) and get all day after few hours a bluescreen with different errors. INTERRUPT_EXCEPTION_NOT_HANDLED or an IQRL_ Error.. The last error is that 56373 I asked MSI but they didn't known how to solve that problem.....
I believe it's a problem with the amd driver but was unsure on what to do, will attach minidump and sf files. This forum has been very helpful to me in the past and I know it will be and thank you for all of your help. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124...
Windows 8.1 unknown bluescreen error in BSOD Crashes and Debugging
Hey guys, Just joined these forums because I have had ongoing bluescreen and freezing issues with windows 8.1, I just flashed the bios on my system to the recent version to eliminate that as the issue. I would appreciate any help, seems to be no rhyme or reason to my crashes.
BlueScreen Error on Windows 8 in BSOD Crashes and Debugging
Hi guys, i have a problem with my desktop PC: a week ago i've installed some new components on my desktop (motherboard, video card, RAM and power source). I've also installed an new operating system - Windows 8, and components drivers (video, audio, ethernet) - all up-to-date, compatible with...
Solved 8.1 updated caused error in logilda.dll in Windows Updates & Activation
After upgrading to 8.1, this morning, when I booted up I would get an error about the Logitech updater. I tried several things to get rid of it, as suggested on searches, but none would get rid of the error. I finally deleted the logilda.dll with my Win Patrol. Here was the error message. ...
Bluescreen error 0xC000021A in BSOD Crashes and Debugging
Hello, I have installed Windows 8 Pro on my PC and on my Laptop. The problem is since yesterday the laptop ist showing the error 0XC000021A. It only writes that my PC ran into a problem and needs to restart. After a restart it just writes the system must be recovered and if I click on "Recover" it...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook