Blue Screen of Death, BIG problem!!!

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 professional 32 bit
       #1

    Blue Screen of Death, BIG problem!!!


    Hello,

    Let me introduce myself, i'm Sander from the Netherlands, 23 years old and i'm experiencing a major problem. There is this BSOD I just can't get rid off. You guys probably all know this BSOD cause i'm not the only one with this problem. Anyway, this is the code: Problem signature:Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48Locale ID: 1043

    I googled this error up, but it's so hard to find a good solution. It's very important for me that this problem is going to be fixed, cause I make professional music on this computer and I lost to many work due this BSOD. So please, please, please, HELP ME! Here is the link to my Minidump in .zip -> Minidump zip

    Greets,

    Sander
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    All of your .dmp files are reporting a 0x124 hardware error. This is a general hardware error, but does not specify exactly what piece of hardware is faulting... Please read this thread for possible solutions ... Stop 0x124 - what it means and what to try..

    Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 00000000, Machine Check Exception
    Arg2: 85e6c024, Address of the WHEA_ERROR_RECORD structure.
    Arg3: f609c000, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000135, 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
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
    
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, 85f3f4dc, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    *******************************************************************************
    *                                                                             *
    *                        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: 00000000, Machine Check Exception
    Arg2: 85ecf024, Address of the WHEA_ERROR_RECORD structure.
    Arg3: b271c000, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000175, 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
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
    These drivers are outdated and should be updated...

    Code:
    9018f000 90190420   ASACPI   ASACPI.sys   Thu Aug 12 22:52:52 2004 (411C2D04) ... Asus ATK0110 ACPI Utility (a known BSOD maker). ... ASUSTeK Computer Inc.-Support-
    90871000 908b9000   netr61   netr61.sys   Thu Aug 24 23:55:21 2006 (44EE74A9) ... Most likely a Linksys Wireless Adapter (RaLink chipset) ... Support and Services	
    88c27000 88c4c000   nvstor   nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9) ... nVidia Storage Drivers ... Drivers - Download NVIDIA Drivers
    88d64000 88d6d0c0   PxHelp20 PxHelp20.sys Mon Dec 10 18:48:39 2007 (475DD057) ... Sonic CD/DVD driver (used by many different CD/DVD programs) ... pxHelp20.sys programs ... Go to C:\Windows\System32\drivers and rename PxHelp20.sys to PXHelp20.BAK
    This will break your CD/DVD program, but can easily be renamed after we've finished.
      My Computer


  3. Posts : 10
    Windows 7 professional 32 bit
    Thread Starter
       #3

    Thanks for the fast reply, I will try all of this and will let you know if it worked! Anyway, you made my day
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Wtfunk said:
    Hello,

    Let me introduce myself, i'm Sander from the Netherlands, 23 years old and i'm experiencing a major problem. There is this BSOD I just can't get rid off. You guys probably all know this BSOD cause i'm not the only one with this problem. Anyway, this is the code: Problem signature:Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48Locale ID: 1043

    I googled this error up, but it's so hard to find a good solution. It's very important for me that this problem is going to be fixed, cause I make professional music on this computer and I lost to many work due this BSOD. So please, please, please, HELP ME! Here is the link to my Minidump in .zip -> Minidump zip

    Greets,

    Sander

    Hi and welcome. Thanks for the introduction

    Your DMPs are being caused by hardware (BCC 124) Please read the below

    Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

    Thanks


    Ken
      My Computer


  5. Posts : 11,840
    64-bit Windows 8.1 Pro
       #5

    Be sure to let us know how it comes out...
      My Computer


  6. Posts : 2,528
    Windows 10 Pro x64
       #6

    Tews said:
    All of your .dmp files are reporting a 0x124 hardware error. This is a general hardware error, but does not specify exactly what piece of hardware is faulting...
    Actually, that's not entirely true - it does, if you look at the error record (!errrec <param 2> from a stop 0x124). For example, the first dump in the minidump folder shows this:
    Code:
    0: kd> !errrec 85e6c024
    ...
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ 85e6c134
    Section       @ 85e6c2bc
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL1_DRD_ERR (Proc 0 Bank 0)
      Status      : 0xf609c00000000135
      Address     : 0x00000000001d5248
      Misc.       : 0x0000000000000000
    It's an L1 cache error in Proc 0. Unfortuantely, the SMBIOS structures weren't in the memory captured in this dump so the sysinfo extension won't help us easily detect the CPU, but you can still look at the raw CPU info with !cpuinfo:
    Code:
    0: kd> !sysinfo cpuinfo
    sysinfo: could not find necessary interfaces.
    sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
    
    0: kd> !cpuinfo
    CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
     0 15,67,3 AuthenticAMD 3013 0000000000000000                   a01d7fff
    From that (Family 15, Model 67, Stepping 3) we can deduce it's an Athlon64 X2 6000+ (~3GHz), and it's dual core. So, the first of the two cores has an L1 cache issue, so either the CPU is faulty, or there are BIOS issues. If the OP hasn't updated or touched the BIOS (or otherwise changed hardware, and thus any timings, before this occured), we can be fairly certain the CPU is going bad (it's not overclocked either, so that's another clue it's probably overheating or has been damaged by heat if it is the CPU). All of the other dumps show L1 cache errors as well, so it's pretty clear that CPU is reporting a bad L1 cache if nothing changed on the system before this started occurring.
      My Computer


  7. Posts : 11,840
    64-bit Windows 8.1 Pro
       #7

    Thanks for the additional info Cluberti!
      My Computer


  8. Posts : 10
    Windows 7 professional 32 bit
    Thread Starter
       #8

    He Cluberti,

    I've been monitoring my CPU's temperature and all the temperatures are stable(45-49 celsius), so that's not the problem I guess...I never tried to remove my CPU and never touched it. I will try the solutions mentioned above and will post the results this week(not experiencing a BSOD every day, mostly 2 times a week).
      My Computer


  9. Posts : 10
    Windows 7 professional 32 bit
    Thread Starter
       #9

    Well, I tried the things Tews suggested like the SPTD uninstaller and the driver updates, but I still get this BSOD... Should I post more information or something, cause I reeeeeally want to get rid off this problem! Please help, thanks.
      My Computer


  10. Posts : 1,870
    MS Windows 7 Professional 64-bit SP1
       #10

    System Specs would be nice.
      My Computer


 
Page 1 of 2 12 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:36.
Find Us