BSOD and Memory Dump in Windows 7 Ultimate Caused by driver hal.dll

Discussion in 'Windows 64bit' started by Robert Guadagnoli, Sep 1, 2009.

  1. I just got a Dell XPS 435MT the other day and it has been crashing with BSOD
    like 50 times a day. I am new at looking at the mini dump file. can anyone
    interpret this?

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [c:\windows\minidump\083109-22744-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    WARNING: Inaccessible path: 'c:\windows\i386'
    Symbol search path is: srv*c:\symbols*Symbol information
    Executable search path is: c:\windows\i386
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0340b000 PsLoadedModuleList = 0xfffff800`03648e50
    Debug session time: Mon Aug 31 13:11:46.119 2009 (GMT-5)
    System Uptime: 0 days 21:08:41.993
    Loading Kernel Symbols
    ................................................................
    .................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa800842a028, fe000000, 300136}

    Probably caused by : hardware

    Followup: MachineOwner
    ---------

    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of
    error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800842a028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000300136, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: WLXPGSS.SCR

    CURRENT_IRQL: f

    STACK_TEXT:
    fffff880`02f6cb58 fffff800`039fa903 : 00000000`00000124 00000000`00000000
    fffffa80`0842a028 00000000`fe000000 : nt!KeBugCheckEx
    fffff880`02f6cb60 fffff800`03591513 : 00000000`00000001 fffffa80`0840cea0
    00000000`00000000 fffffa80`0840cef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`02f6cba0 fffff800`039fa5c8 : 00000000`00000728 fffffa80`0840cea0
    fffff880`02f6cf30 fffff880`02f6cf00 : nt!WheaReportHwError+0x263
    fffff880`02f6cc00 fffff800`039f9f1a : fffffa80`0840cea0 fffff880`02f6cf30
    fffffa80`0840cea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02f6cd50 fffff800`039f9dd5 : 00000000`00000008 00000000`00000001
    fffff880`02f6cfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02f6cd90 fffff800`039ede88 : 00000000`01c30000 00000000`04f94800
    00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`02f6cdc0 fffff800`0347b7ac : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`02f6cdf0 fffff800`0347b613 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`02f6cf30 00000000`74603c6b : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0008da34 00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : 0x74603c6b


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

    Followup: MachineOwner
    ---------
    My System SpecsSystem Spec Edit/Delete Message Reply With Quote Multi-Quote
    This Message
    OS Windows 7 Ultimate




    Default
    A STOP 0x124 error message is a bear to debug. Most often (IME) it's due to
    an incompatibility with the system - but it can also be due to hardware
    issues.

    In this case, you've got the generic 0x124 (vs the 0x124 with the first
    parameter of 4, which is the PCIe error).

    I would start with inventorying what you've installed on the system
    (hardware and software) between the time that you installed Windows 7 and
    the time that the BSOD's occurred.

    Also, use this free tool to check your drivers (to see how old they are):
    BlueScreenView - View blue screen of death (STOP error) information. At
    times it's results differ from WinDbg - so I'd advise using it with caution.
    But the driver dates have proven accurate for me - so that'll tell you if
    anything is excessively old (2007 or earlier).

    Finally, run the Windows 7 Upgrade Advisor to see if it can point out any
    incompatibilities on the system:
    http://www.microsoft.com/downloads/d...displaylang=en
    My System SpecsSystem Spec



    this system is 5 days old, It came with Vista x64 and it Blue screened
    within the first hour I turned it on. I have Windows 7 Ultimate because I am
    a Microsoft alumni and have access to it so I decided to try that out to see
    if I could get rid of the BSOD. Same issue. I have updated the drivers for
    all the devices that I could. I havent added any hardware other than a HP
    printer. Also, before I even added the printer, it BSOD.

    I will look at those other utilities.


    Default
    BlueScreenView provided me with this

    Caused by driver hal.dll
    My System SpecsSystem Spec Edit/Delete Message Reply With Quote Multi-Quote
    This Message
    OS Windows 7 Ultimate


    Default
    Ran the Windows 7 upgrade adviser with no issues to report.
    Robert Guadagnoli, Sep 1, 2009
    #1
    1. Advertising

  2. Robert Guadagnoli

    R. C. White Guest

    Hi, Robert.

    I'm no techie, either, but I've got 30 years of experience with
    microcomputers, so I've managed to learn a couple of things. I'm still no
    good at reading dump files.

    > WARNING: Inaccessible path: 'c:\windows\i386'


    This does not look right. There is NO such folder in my installed Win7.
    C:\Windows\i386 is a folder on the installation DVD-ROM.

    > this system is 5 days old, It came with Vista x64 and it Blue screened
    > within the first hour I turned it on.


    It looks to me like Win7 was not properly installed. It might have been
    aborted before the install was completed. Since it is a brand new machine,
    I would be hurrying back to the vendor for a warranty replacement.

    RC
    --
    R. C. White, CPA
    San Marcos, TX

    Microsoft Windows MVP
    Windows Live Mail 2009 (14.0.8089.0726) in Win7 Ultimate x64

    "Robert Guadagnoli" <> wrote in message
    news:...
    > I just got a Dell XPS 435MT the other day and it has been crashing with
    > BSOD like 50 times a day. I am new at looking at the mini dump file. can
    > anyone interpret this?
    >
    > Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    > Copyright (c) Microsoft Corporation. All rights reserved.
    >
    >
    > Loading Dump File [c:\windows\minidump\083109-22744-01.dmp]
    > Mini Kernel Dump File: Only registers and stack trace are available
    >
    > WARNING: Inaccessible path: 'c:\windows\i386'
    > Symbol search path is: srv*c:\symbols*Symbol information
    > Executable search path is: c:\windows\i386
    > Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    > Product: WinNt, suite: TerminalServer SingleUserTS
    > Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

    <SNIP most of Dump File>


    It is not clear to me (RC) which of the following text is from you, Robert,
    and which is from someone trying to help you:

    > Followup: MachineOwner
    > ---------
    > My System SpecsSystem Spec Edit/Delete Message Reply With Quote
    > Multi-Quote This Message
    > OS Windows 7 Ultimate
    >
    >
    > Default
    > A STOP 0x124 error message is a bear to debug. Most often (IME) it's due
    > to an incompatibility with the system - but it can also be due to hardware
    > issues.
    >
    > In this case, you've got the generic 0x124 (vs the 0x124 with the first
    > parameter of 4, which is the PCIe error).
    >
    > I would start with inventorying what you've installed on the system
    > (hardware and software) between the time that you installed Windows 7 and
    > the time that the BSOD's occurred.
    >
    > Also, use this free tool to check your drivers (to see how old they are):
    > BlueScreenView - View blue screen of death (STOP error) information. At
    > times it's results differ from WinDbg - so I'd advise using it with
    > caution. But the driver dates have proven accurate for me - so that'll
    > tell you if anything is excessively old (2007 or earlier).
    >
    > Finally, run the Windows 7 Upgrade Advisor to see if it can point out any
    > incompatibilities on the system:
    > http://www.microsoft.com/downloads/d...displaylang=en
    > My System SpecsSystem Spec
    >
    >
    >
    > this system is 5 days old, It came with Vista x64 and it Blue screened
    > within the first hour I turned it on. I have Windows 7 Ultimate because I
    > am a Microsoft alumni and have access to it so I decided to try that out
    > to see if I could get rid of the BSOD. Same issue. I have updated the
    > drivers for all the devices that I could. I havent added any hardware
    > other than a HP printer. Also, before I even added the printer, it BSOD.
    >
    > I will look at those other utilities.
    >
    >
    > Default
    > BlueScreenView provided me with this
    >
    > Caused by driver hal.dll
    > My System SpecsSystem Spec Edit/Delete Message Reply With Quote
    > Multi-Quote This Message
    > OS Windows 7 Ultimate
    >
    >
    > Default
    > Ran the Windows 7 upgrade adviser with no issues to report.
    R. C. White, Sep 1, 2009
    #2
    1. Advertising

  3. that error was erroneous because I was using the debugging tools to view the
    minimum file, so that can be ignored. This system came with Windows Vista
    x64. I turned it on and it BSOD within 2 hours. It did it dozens of times
    over the next 24 hours. Then that is when I installed Windows 7. It
    installed start to finish flawlessly. There were no bings or bangs :) in
    device manager when I was done. This did not change the anything though. I
    still received dozens of BSOD'a over the next few days. I got the latest
    nvidia driver for this card, still had issue. Then I got the video driver
    from Dell, who I bought this from, it was one revision earlier. Still same
    issue. But then I started debugging and noticed that it crashed on hal.dll
    that is where I need the help because that is part of the OS and not
    hardware specific.

    "R. C. White" <> wrote in message
    news:...
    > Hi, Robert.
    >
    > I'm no techie, either, but I've got 30 years of experience with
    > microcomputers, so I've managed to learn a couple of things. I'm still no
    > good at reading dump files.
    >
    >> WARNING: Inaccessible path: 'c:\windows\i386'

    >
    > This does not look right. There is NO such folder in my installed Win7.
    > C:\Windows\i386 is a folder on the installation DVD-ROM.
    >
    >> this system is 5 days old, It came with Vista x64 and it Blue screened
    >> within the first hour I turned it on.

    >
    > It looks to me like Win7 was not properly installed. It might have been
    > aborted before the install was completed. Since it is a brand new
    > machine, I would be hurrying back to the vendor for a warranty
    > replacement.
    >
    > RC
    > --
    > R. C. White, CPA
    > San Marcos, TX
    >
    > Microsoft Windows MVP
    > Windows Live Mail 2009 (14.0.8089.0726) in Win7 Ultimate x64
    >
    > "Robert Guadagnoli" <> wrote in message
    > news:...
    >> I just got a Dell XPS 435MT the other day and it has been crashing with
    >> BSOD like 50 times a day. I am new at looking at the mini dump file. can
    >> anyone interpret this?
    >>
    >> Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    >> Copyright (c) Microsoft Corporation. All rights reserved.
    >>
    >>
    >> Loading Dump File [c:\windows\minidump\083109-22744-01.dmp]
    >> Mini Kernel Dump File: Only registers and stack trace are available
    >>
    >> WARNING: Inaccessible path: 'c:\windows\i386'
    >> Symbol search path is: srv*c:\symbols*Symbol information
    >> Executable search path is: c:\windows\i386
    >> Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    >> Product: WinNt, suite: TerminalServer SingleUserTS
    >> Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

    > <SNIP most of Dump File>
    >
    >
    > It is not clear to me (RC) which of the following text is from you,
    > Robert, and which is from someone trying to help you:
    >
    >> Followup: MachineOwner
    >> ---------
    >> My System SpecsSystem Spec Edit/Delete Message Reply With Quote
    >> Multi-Quote This Message
    >> OS Windows 7 Ultimate
    >>
    >>
    >> Default
    >> A STOP 0x124 error message is a bear to debug. Most often (IME) it's due
    >> to an incompatibility with the system - but it can also be due to
    >> hardware issues.
    >>
    >> In this case, you've got the generic 0x124 (vs the 0x124 with the first
    >> parameter of 4, which is the PCIe error).
    >>
    >> I would start with inventorying what you've installed on the system
    >> (hardware and software) between the time that you installed Windows 7 and
    >> the time that the BSOD's occurred.
    >>
    >> Also, use this free tool to check your drivers (to see how old they are):
    >> BlueScreenView - View blue screen of death (STOP error) information. At
    >> times it's results differ from WinDbg - so I'd advise using it with
    >> caution. But the driver dates have proven accurate for me - so that'll
    >> tell you if anything is excessively old (2007 or earlier).
    >>
    >> Finally, run the Windows 7 Upgrade Advisor to see if it can point out any
    >> incompatibilities on the system:
    >> http://www.microsoft.com/downloads/d...displaylang=en
    >> My System SpecsSystem Spec
    >>
    >>
    >>
    >> this system is 5 days old, It came with Vista x64 and it Blue screened
    >> within the first hour I turned it on. I have Windows 7 Ultimate because I
    >> am a Microsoft alumni and have access to it so I decided to try that out
    >> to see if I could get rid of the BSOD. Same issue. I have updated the
    >> drivers for all the devices that I could. I havent added any hardware
    >> other than a HP printer. Also, before I even added the printer, it BSOD.
    >>
    >> I will look at those other utilities.
    >>
    >>
    >> Default
    >> BlueScreenView provided me with this
    >>
    >> Caused by driver hal.dll
    >> My System SpecsSystem Spec Edit/Delete Message Reply With Quote
    >> Multi-Quote This Message
    >> OS Windows 7 Ultimate
    >>
    >>
    >> Default
    >> Ran the Windows 7 upgrade adviser with no issues to report.

    >
    Robert Guadagnoli, Sep 1, 2009
    #3
  4. When you buy a new system and you have problems as described you should
    go back to Dell with your problems. The system is under warranty and
    you're not going to fix hardware [problems in a forum for Windows
    operating system.

    Contact Dell about your problems!


    Robert Guadagnoli wrote:
    > this system is 5 days old, It came with Vista x64 and it Blue screened
    > within the first hour I turned it on. I have Windows 7 Ultimate because
    > I am a Microsoft alumni and have access to it so I decided to try that
    > out to see if I could get rid of the BSOD. Same issue. I have updated
    > the drivers for all the devices that I could. I havent added any
    > hardware other than a HP printer. Also, before I even added the printer,
    > it BSOD.
    >
    Bobby Johnson, Sep 1, 2009
    #4
  5. His system is under warranty if he returns it with the original Vista
    configuration. Seeing as how Windows 7 has not been released yet, I doubt
    that the vendor or the manufacturer will accept it for warranty repair as it
    it now (with Windows 7 installed).

    --

    Richard Urban
    Microsoft MVP
    Windows Desktop Experience


    "Bobby Johnson" <> wrote in message
    news:...
    > When you buy a new system and you have problems as described you should go
    > back to Dell with your problems. The system is under warranty and you're
    > not going to fix hardware [problems in a forum for Windows operating
    > system.
    >
    > Contact Dell about your problems!
    >
    >
    > Robert Guadagnoli wrote:
    >> this system is 5 days old, It came with Vista x64 and it Blue screened
    >> within the first hour I turned it on. I have Windows 7 Ultimate because I
    >> am a Microsoft alumni and have access to it so I decided to try that out
    >> to see if I could get rid of the BSOD. Same issue. I have updated the
    >> drivers for all the devices that I could. I havent added any hardware
    >> other than a HP printer. Also, before I even added the printer, it BSOD.
    >>
    Richard Urban, Sep 1, 2009
    #5
  6. This may be true, but this is not the place to get his hardware fixed.
    He had problems with Vista installed and now he is having problems with
    Win 7 installed.

    Hardware problems are not going to get fixed in an OS forum. One way or
    another he is going to have to get the hardware fixed, but this is not a
    Repair Shop.


    Richard Urban wrote:
    > His system is under warranty if he returns it with the original Vista
    > configuration. Seeing as how Windows 7 has not been released yet, I
    > doubt that the vendor or the manufacturer will accept it for warranty
    > repair as it it now (with Windows 7 installed).
    >
    Bobby Johnson, Sep 1, 2009
    #6
  7. Robert Guadagnoli

    XS11E Guest

    "Richard Urban" <> wrote:

    > His system is under warranty if he returns it with the original
    > Vista configuration. Seeing as how Windows 7 has not been released
    > yet, I doubt that the vendor or the manufacturer will accept it
    > for warranty repair as it it now (with Windows 7 installed).


    Let's hope he has the restore CDs or restore partition?



    --
    XS11E, Killing all posts from Google Groups
    The Usenet Improvement Project:
    http://twovoyagers.com/improve-usenet.org/
    XS11E, Sep 1, 2009
    #7
  8. I do have the repair to get it back to original... I am not an armature.

    There seems to be a lot of condensation in this thread, typical. I came here
    for some clues, not to show me how big your dick is technically.

    Dell came out and replaced the motherboard and processor, I have not had a
    BSOD since then.

    Thanks for your time. You are just extremely awesome and I will never be
    able to compare to you, even though I have been in IT for 15 years now...

    "XS11E" <> wrote in message
    news:Xns9C7953EE48450xs11eyahoocom@127.0.0.1...
    > "Richard Urban" <> wrote:
    >
    >> His system is under warranty if he returns it with the original
    >> Vista configuration. Seeing as how Windows 7 has not been released
    >> yet, I doubt that the vendor or the manufacturer will accept it
    >> for warranty repair as it it now (with Windows 7 installed).

    >
    > Let's hope he has the restore CDs or restore partition?
    >
    >
    >
    > --
    > XS11E, Killing all posts from Google Groups
    > The Usenet Improvement Project:
    > http://twovoyagers.com/improve-usenet.org/
    Robert Guadagnoli, Sep 1, 2009
    #8
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. John

    Ghost restore and HAL.DLL is missing?

    John, Oct 2, 2005, in forum: Computer Support
    Replies:
    4
    Views:
    6,015
    FullName
    Oct 3, 2005
  2. Dennis Gordon

    OT: Missing hal.dll and C unreadable

    Dennis Gordon, Apr 27, 2006, in forum: Windows 64bit
    Replies:
    6
    Views:
    516
    Charlie Russel - MVP
    Apr 28, 2006
  3. Snoopy
    Replies:
    16
    Views:
    3,007
    Mainlander
    Aug 25, 2003
  4. Dan C

    Re: BSOD caused by SpyWare

    Dan C, Jan 5, 2011, in forum: Computer Support
    Replies:
    0
    Views:
    816
    Dan C
    Jan 5, 2011
  5. richard

    Re: BSOD caused by SpyWare

    richard, Jan 5, 2011, in forum: Computer Support
    Replies:
    6
    Views:
    968
    G. Morgan
    Jan 6, 2011
Loading...

Share This Page