I'm getting BSOD every so often

Page 1 of 2 12 LastLast

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

    I'm getting BSOD every so often


    I've been getting a lot BSOD's lately mostly when playing games,while Producing music and while rendering videos. I've had them a few times even while idle but rarely while idle.

    I've linked the Diagnostic tool results here: Attachment 283020

    I've updated all my drivers to the latest drivers I found.
      My Computer


  2. Posts : 4
    windows 7 x64
       #2

    huh this is sounding suspicious.. do you have an amd card? I just posted a thread like this. Maybe a driver 12.104.0.0 problem?
      My Computer


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

    futurista said:
    huh this is sounding suspicious.. do you have an amd card? I just posted a thread like this. Maybe a driver 12.104.0.0 problem?
    I've got a screenshot here of my specs http://puu.sh/49KHW.png
      My Computer


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

    This was my latest blue screen if it helps in anyway

    Attachment 283056
      My Computer


  5. Posts : 3,056
    Windows 10
       #5

    jimentoez, welcome to SF :).

    All your bugchecks are reporting (0x124) a hardware error.
    Code:
    WHEA_UNCORRECTABLE_ERROR (124)
    
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80086884f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    • A fatal hardware error has occurred.

    Argument 1 is telling us that the CPU has detected an error and has risen the red flag
    to initiate a bugcheck in-order to protect the data.
    Keep in mind that although the the CPU is the one which detected the fault doesn't
    mean he is to blame.


    We can use !errrec on the second argument to get more information about the error:

    Code:
    2: kd> !errrec fffffa80086884f8
    ===============================================================================
    Common Platform Error Record @ fffffa80086884f8
    -------------------------------------------------------------------------------
    Record Id     : 01ce9f30519de544
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 8/22/2013 12:08:40 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008688578
    Section       @ fffffa8008688650
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Data Write
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100fa0
    Processor ID  : 0x0000000000000004
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa80086885c0
    Section       @ fffffa8008688710
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000004
    CPU Id        : a0 0f 10 00 00 08 06 04 - 09 20 80 00 ff fb 8b 17
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ fffffa8008688710
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008688608
    Section       @ fffffa8008688790
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL1_DWR_ERR (Proc 4 Bank 0)
      Status      : 0xb600400034000145
      Address     : 0x00000001ceadb600
      Misc.       : 0x0000000000000000
    We can see that the error type is Cache error and it is Fatal.
    Although this doesn't mean much it gives as a clue as to what might be going on.

    Steps to try before we move on:

    • fill out you System Specifications completely.
    • If any component of your PC overclocked revert it back to stock settings.
    • Check for dust accumulation inside the case and around the fan intakes.
    • Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.




    Good places to start:


      My Computer


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

    1. I filled out my specification page on my profile.
    2. Nothing is overclocked.
    3. I've got all of the dust of my pc that I could with compressed air.
    4. Screenshots of Speedfan:
    While Idle my temps are: http://puu.sh/4a0ts.png
    While in game these are my temps: http://puu.sh/4a0e1.png
      My Computer


  7. Posts : 3,056
    Windows 10
       #7

    Did you clean the PC before or after those Bugchecks occurred?
    Also what is the make and model of your PSU?
    Is the BIOS set to its optimized defaults?
      My Computer


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

    1. I cleaned my PC when the BSOD's started happening which was a couple weeks ago but it seems to of done nothing.
    2. PSU is FPS Group Inc. Model No. FPS450-60APN
    3. I've not changed my BIOS so I'm guessing it will still be default, unless something has changed it.
      My Computer


  9. Posts : 3,056
    Windows 10
       #9

    The generic nature of the 0x124 (Arg1=0) stop code means we would have to take
    the trail & error approach.

    Do you have any spear parts (or another PC) to test with, mainly a PSU?
    The usual suspect of this kind of BCCode is the CPU but it's often not the the case which is why we need
    to test other components to rule them out as the cause.
    How old are your components?

    Fill out this form and post back the result.


    Start by opening up the case and re-seating all types of connection.

    • SATA Cables (HDD/SSD/ODD).
    • SATA-Power.
    • Motherboard 24-pin.
    • Motherboard 4/8-pin (CPU).
    • Re-seat the RAM.
    • Re-seat the GPU.

    Make sure that every slot / cable head is free of dust or other obstruction.
    Make sure that every connection is seating properly and firmly in-place.

    I still insist on uploading a screenshot of the summary screen of Speccy.
    • Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

    Did you read the links I've linked above?
      My Computer


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

    Everything but the RAM is just under 3 years old. the RAM is 2 months old. Also I don't have part parts or a PC only a Laptop.

    Calculator Result: http://puu.sh/4axGp.png

    Reconnected all the leads

    Speccy at Idle: http://puu.sh/4axPX.png

    Speccy with CPU load: http://puu.sh/4aybf.png

    Speccy with GPU load: http://puu.sh/4axZF.png
      My Computer


 
Page 1 of 2 12 LastLast

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 03:33.
Find Us