BSOD on new components need help finding out why?

Page 3 of 5 FirstFirst 12345 LastLast

  1. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #21

    022612-24429-01.dmp was another Hardware Stop 0x124. Stop 0x124 - what it means and what to try

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\022612-26410-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*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 Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c9d670
    Debug session time: Sun Feb 26 04:58:06.591 2012 (UTC - 7:00)
    System Uptime: 0 days 0:06:13.183
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa80074cd028, b6004000, 2a000175}
    
    Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athurx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athurx.sys
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    3: 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: fffffa80074cd028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b6004000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000002a000175, 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:  svchost.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`02fdda88 fffff800`02a21a3b : 00000000`00000124 00000000`00000000 fffffa80`074cd028 00000000`b6004000 : nt!KeBugCheckEx
    fffff880`02fdda90 fffff800`02be5513 : 00000000`00000001 fffffa80`07a44d30 00000000`00000000 fffffa80`07a44d80 : hal!HalBugCheckSystem+0x1e3
    fffff880`02fddad0 fffff800`02a21700 : 00000000`00000728 fffffa80`07a44d30 fffff880`02fdde30 fffffa80`08651a00 : nt!WheaReportHwError+0x263
    fffff880`02fddb30 fffff800`02a21052 : fffffa80`07a44d30 fffff880`02fdde30 fffffa80`07a44d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02fddc80 fffff800`02a14e8f : fffffa80`08668a90 00000000`00000001 fffff880`02fddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02fddcc0 fffff800`02ad352c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`02fddcf0 fffff800`02ad3393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`02fdde30 fffff880`0461b805 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`009b0a10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : athurx+0x9805
    
    
    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
    ---------
    Ah, but the preceding one was actually due to your wireless USB adapter... I think we've narrowed down the hardware crashes as well to your USB adapter.
      My Computer


  2. Posts : 22
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #22

    So its more than likely the adapter, it must have a problem with this OS then because it was great on my previous computers vista?
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #23

    Many of the adapters that worked in Vista do not work in 7. In most cases the drivers have not been updated to work with 7, but I do not know if that is the case with your adapter. It appears to have the proper drivers. It's possible that Windows 7 does something different with the power constraints for wireless adapters, and the USB connection is not enough to handle it.
      My Computer


  4. Posts : 22
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #24

    Another error report here could be different not sure :/
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #25

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\022712-28563-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 Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02a1e000 PsLoadedModuleList = 0xfffff800`02c63670
    Debug session time: Mon Feb 27 15:57:20.822 2012 (UTC - 7:00)
    System Uptime: 0 days 7:12:19.414
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {28, 2, 0, fffff880044025cd}
    
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSetState+35 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880044025cd, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ccd100
     0000000000000028 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    USBPORT!USBPORT_Xdpc_iSetState+35
    fffff880`044025cd 4c394a28        cmp     qword ptr [rdx+28h],r9
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88002f1bae0 -- (.trap 0xfffff88002f1bae0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880044025cd rsp=fffff88002f1bc70 rbp=fffffa8009b062b0
     r8=fffffa8007c7b1a0  r9=0000000000000000 r10=00000000ffffffff
    r11=fffffa8007c7b1a0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    USBPORT!USBPORT_Xdpc_iSetState+0x35:
    fffff880`044025cd 4c394a28        cmp     qword ptr [rdx+28h],r9 ds:ffff:00000000`00000028=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a9a1e9 to fffff80002a9ac40
    
    STACK_TEXT:  
    fffff880`02f1b998 fffff800`02a9a1e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f1b9a0 fffff800`02a98e60 : fffffa80`09741730 fffffa80`07c7b101 00000000`00000002 fffffa80`07c7bd28 : nt!KiBugCheckDispatch+0x69
    fffff880`02f1bae0 fffff880`044025cd : fffff880`009eef40 00000000`00000022 00000000`00000000 00000000`ffffffff : nt!KiPageFault+0x260
    fffff880`02f1bc70 fffff880`04402f89 : fffffa80`07c7b050 00000000`00000000 fffffa80`07c7bd02 fffffa80`07c7bd28 : USBPORT!USBPORT_Xdpc_iSetState+0x35
    fffff880`02f1bca0 fffff800`02aa60ac : fffff880`009ea180 fffffa80`07c7bd28 fffffa80`07c7bd40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`02f1bcd0 fffff800`02a9296a : fffff880`009ea180 fffff880`009f4fc0 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x1bc
    fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    USBPORT!USBPORT_Xdpc_iSetState+35
    fffff880`044025cd 4c394a28        cmp     qword ptr [rdx+28h],r9
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  USBPORT!USBPORT_Xdpc_iSetState+35
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: USBPORT
    
    IMAGE_NAME:  USBPORT.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08
    
    FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35
    
    BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35
    
    Followup: MachineOwner
    ---------
    USB related crash. Different from the hardware crash, but still likely due to the USB wireless...
    You did have a few more of the 0x124 crashes, as well.
      My Computer


  6. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #26

    After looking at your CPUZ tabs, there are a couple things that may be causing your crash issues.

    Attachment 200716
    Attachment 200715 Attachment 200714

    Your motherboard site Gigabyte GA-A55M-DS2 is showing a RAM fix (may not apply), Update CPU code and Improve system compatibility, BIOS updates. Newest version is F6, never use any Beta BIOS.
    Don't like to recommend updating BIOS unless absolutely necessary, so may come back to this later.

    Searching your RAM didn't find the exact match on the G. Skill site but, the other F3-12800CL9D-4GBXL and F3-12800CL9Q-16GBXL, XL part numbers are 'Designed For 2nd Generation Intel® Core™ Processors'.
    This is a known issue for AMD systems, there is no mention of these kits being able to run on an AMD system and no mention of any AMD boards as compatible.
    The 'XMP' listing on the CPUZ tab was the indication that these are Intel optimized RAM as 'XMP' is an Intel RAM timing setting.
    Also no listing of the Mode, which should be 'Unganged', no NB frequency listed.
    These are all important as there is another known issue with AMD systems and RAM frequency above 1333MHz.
    I hope AMD has got this sorted out by now but, haven't seen any confirmation yet.

    Can you RMA the RAM and get AMD RAM for your system?

    This would be the first thing to do, with compatible RAM your system will be more stable and hopefully solve the crashing issues.
      My Computer


  7. Posts : 22
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #27

    Well I actually bought it as a motherboard bundle from a trusted shop called CCL online and I have a 3 year warranty etc

    http://www.cclonline.com/product/736...MBB-AMDEL-ENT/
      My Computer


  8. Posts : 22
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #28

    Would it be an idea to remove my adapter and clock it back up to default settings and play a few games to stress test it?
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #29

    I think that is a good idea. Load Setup Defaults in the BIOS and remove the USB adapter. See if it runs stable.

    I think it is a good idea to look into the RAM compatibility as well.
      My Computer


  10. Posts : 22
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #30

    Should I update my BIOS It only seems to make sense, is there any reason not to?
      My Computer


 
Page 3 of 5 FirstFirst 12345 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 09:21.
Find Us