PDN and BSOD

Page 2 of 2 FirstFirst 12

  1. Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       #11

    Hello again,
    Dump still points to 0x124 (Hardware)
    Bugcheck 0x124 = Hardware WHEA = Hardware Failure

    Download and install Speedfan, tell us the temperatures of the components: SpeedFan - Access temperature sensor in your computer

    Take pictures of the BIOS Settings (CPU, RAM, Voltages, Etc. . .) and upload the pictures in your next reply.

    Dean
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Dean\Desktop\042411-17578-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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`03247e90
    Debug session time: Mon Apr 25 05:20:38.158 2011 (UTC + 12:00)
    System Uptime: 0 days 0:02:25.283
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8007fee028, f60f2000, 135}
    
    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: fffffa8007fee028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000f60f2000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  WinSAT.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`0316ca88 fffff800`035fea3b : 00000000`00000124 00000000`00000000 fffffa80`07fee028 00000000`f60f2000 : nt!KeBugCheckEx
    fffff880`0316ca90 fffff800`0318f7d3 : 00000000`00000001 fffffa80`07fc6e30 00000000`00000000 fffffa80`07fc6e80 : hal!HalBugCheckSystem+0x1e3
    fffff880`0316cad0 fffff800`035fe700 : 00000000`00000728 fffffa80`07fc6e30 fffff880`0316ce30 00000000`00000000 : nt!WheaReportHwError+0x263
    fffff880`0316cb30 fffff800`035fe052 : fffffa80`07fc6e30 fffff880`0316ce30 fffffa80`07fc6e30 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`0316cc80 fffff800`035f1e8f : 00000000`00000001 00000000`00000001 fffff880`0316ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`0316ccc0 fffff800`03080f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`0316ccf0 fffff800`03080d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`0316ce30 000007fe`f015702f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0a9eeb70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f015702f
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 24,479
    Windows 7 Ultimate X64 SP1
    Thread Starter
       #12

    Attachment 151205

    Here's is some Furmark, Speedfan and BIOS pics. Memtest ran for 8 hours with no errors. I see there is something in speedfan reporting a 81C temp. No idea what the heck that is.
    Last edited by Britton30; 17 May 2011 at 14:17.
      My Computer


  3. Posts : 24,479
    Windows 7 Ultimate X64 SP1
    Thread Starter
       #13

    Hello Dean, I think I have it now. I made my new sig with Paint.NET over a 3 hour period and no BSOD! If you notice in my pics of my BIOS I had some CPU settings cranked up a bit, which overclocked the RAM along with the CPU. It may be one of those causing the problem. I'll be doing "science experiments" over the next several days until I crash again.
    I'm still unsure what the 81C temp is from. No heat radiating from the PC case.

    Thanks so much for your patient help!
      My Computer


  4. Posts : 24,479
    Windows 7 Ultimate X64 SP1
    Thread Starter
       #14

    I have re-installed paint.NET and the problem has gone away. Don't know why unless one of the MS .NET updates was fooling with me.
      My Computer


 
Page 2 of 2 FirstFirst 12

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 06:24.
Find Us