Computer Crashing/bsod Infrequently

Discussion in 'Hardware' started by jkman, Apr 13, 2018.

  1. jkman

    jkman Private E-2

    Hi everyone. I have a computer that's crashing infrequently. Some days it could be 10+ times and others just a few. I mostly just do web browsing, often with multiple tabs open, youtube, and windows games on it. I use Firefox browser.

    About the computer:
    Windows 7 Professional 64-bit
    CPU: AMD athlon II x4 640
    Mobo: M4A89GTD-PRO/USB3
    GPU: Radeon HD 4290 (integrated in mobo)
    RAM: DDR3 32GB

    I went through reliability monitor and found this report from the most recent crash from today:

    Source
    Windows

    Summary
    Shut down unexpectedly

    Date
    ‎4/‎13/‎2018 1:32 PM

    Status
    Report sent

    Problem signature
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033

    Extra information about the problem
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA800DEF48F8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
    Bucket ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
    Server information: 908899b4-970d-4c0f-8627-e501c93c7cd6


    Any help is appreciated. Thanks!
     
  2. harmless

    harmless Staff Sergeant

  3. baklogic

    baklogic The Tinkerer

    I agree with harmless on the ram- I would check the timings,( if you have overclocked) , as from what I have seen it appears that the cpu is calling for a bug check, (perhaps ram and cpu timings need adjusting) but beyond that, I cannot help.
    Perhaps someone else may be able to help on that.
     
  4. jkman

    jkman Private E-2

    So I ran the memtest and video memtest. The computer crashed before the ramtest could be completed and the video mem test didn't report anything wrong. The computer parts are close to 10 years old so nothing has been overclocked. I did install new RAM late last year, maybe Oct/Nov. But the computer crashes didn't start happening until a couple months ago. Is there some other diagnostic tool I can use or maybe a crash log I can find somewhere that would better explain the problem?
     
  5. baklogic

    baklogic The Tinkerer

    In command prompt admin, type sfc /scannow press enter-let it run and when it finishes, type EXIT .
    Look in Event viewer to see what has been playing up- Many problems will give a link to Microsoft, and often there is an answer(not always)
    Sart, run ----- CHKDSK /R
    Those three actions can find many faults.
    As it is also possible to be a driver conflict, you could right lick computer , left click manage, click device manager, and see if there are any exclamation marks in the device list.(conflicting, or, bad drivers could show.....)
     
  6. TimW

    TimW MajorGeeks Administrator - Jedi Malware Expert Staff Member

  7. baklogic

    baklogic The Tinkerer

  8. satrow

    satrow Major Geek Extraordinaire

    The AMD CPU is self-reporting an error in its cache memory, often a hardware error (CPU, or possibly motherboard/RAM) but it can also be triggered by a 'logjam' - too much info waiting to be processed which results in a 'time out' by a waiting thread with a fixed 'reply by' period.

    Changing BIOS power states might workaround it, disallowing C6 and/or disabling (specific to AMD) Cool'n'Quiet would be my starting points.
     
  9. jkman

    jkman Private E-2

    So I ran the system file checker and it came back with nothing. I downloaded whocrashed and got the report from the log below. I can try and disable those you mentioned satrow if these logs aren't conclusive. If the problem is in fact hardware and not fixable, would the solution be easy as just getting a new processor? Thanks again.

    Crash dump directories:
    C:\Windows
    C:\Windows\Minidump

    On Mon 4/30/2018 2:07:05 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-29094-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x48C8BC)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DD458F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 4/30/2018 1:55:11 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-35147-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DD6A028, 0xF60F2000, 0x135)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 4/30/2018 1:45:04 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-26364-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x48C8BC)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DE138F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 4/30/2018 1:32:15 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-30513-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DEF8028, 0xF60F2000, 0x135)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 4/30/2018 1:17:51 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-30482-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x48C8BC)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DDF5038, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 4/30/2018 1:02:32 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-28267-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x48C8BC)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DDE32E8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 4/30/2018 12:50:44 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-27424-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DD83028, 0xB665C000, 0x135)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 4/30/2018 12:41:11 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043018-30825-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x48C8BC)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DEBA8F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 4/13/2018 2:23:53 PM your computer crashed or a problem was reported
    crash dump file: C:\Windows\DUMPe7f0.DMP
    This was probably caused by the following module: ntoskrnl.exe (nt+0x48C7EC)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800DD7B718, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




    Conclusion
    9 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
     
  10. satrow

    satrow Major Geek Extraordinaire

    With uptimes as little as 8-9 minutes, it's quite likely to be faulty hardware; I'd definitely try changing the C states and/or Cool'n'Quiet as you have so little time in Windows atm that it would be a very frustrating experience trying to gather logs, upload dumps, etc. with the PC crashing so soon after boot.

    I'd also want to check for overheating, open the case up to check there's no fluff and dust bunnies congregating in the heatsink/s and boot into the BIOS to check that all the fans are at full speed - creating noise and shifting air around - be careful not to touch anything internally with it powered up.

    While it's in the BIOS, check the temperature/voltage screens and log the main stats, 3.3v, 5v, 12v and any temps given. You could also leave it on the BIOS screen overnight to see if it freezes/crashes there.

    It's consistently a 0x124; I could never get to grips with the range of different steps required for those BSODs as the debugging was often just too lengthy and complex for me to keep track of.
     
  11. baklogic

    baklogic The Tinkerer

    I would follow satrow's advice, overheating could be part of the problem- as Looking at this post,
    https://www.tenforums.com/bsod-cras...ng-playing-gta-v-bf1-error-0x124-0x3b-12.html
    they tried changing mobo, cpu, and then going back to original, and miraculously, the fault stopped, but the bios screen shows as warning of temperatures.
    Cleaning heat-sink might be the start, but might I suggest that the cpu is removed, and new thermal paste used, and reseated, as this often reduces the temperatures.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds