PC is randomly freezing

Page 1 of 2 12 LastLast

  1. Posts : 19
    Windows 7 32 bit
       #1

    PC is randomly freezing


    So it all started to happen few days ago. My pc started to randomly freeze and after freeze, i got windows has recovered from crash message. Under details it said reason for crash was bsod with code 124. First thing i thought is that the reason is some kind of hardware issue. So i ran memtest, everything was fine. Then i ran prime95 but prime95 worked fine and pc didn't froze. I noticed that pc doesn't freeze in safe mode, so i thought it must be a software issue, but verifier and sfc scan gave no results. Today, it started to freeze in safe mode too. Also, my external hdd and usb sometimes don't get recognized. And, at last, it sometimes takes a restart or two to even run the pc properly(monitor doesn't turn on, nothing is going on, only fans are spinnin). So, what is it? Is it PSU issue? Or maybe cpu issue? How to even determine what is it?

    EDIT: Attached two minidumps from today's crashes.
    Last edited by Kingofthehill; 21 Jun 2013 at 10:16.
      My Computer


  2. Posts : 26,863
    Windows 11 Pro
       #2

    If you are overclocking anything, reset everything to defaults. Go into bios and set optimized defaults. Set your ram timings, frequency and voltage to manufacturer's specs, set the boot order save and exit. 0X124 is a general hardware fault but is not very specific. If you have temp monitoring programs keep a watch on the CPU temp and GPU temps. If you don't have programs, you can use Core Temp for the CPU and MSI Afterburner for your GPU. Afterburner is an overclocking software for the Gpu, but it has good monitoring features. You said you ran memtest, how long did you run it? It needs to be run 1 stick at a time in each slot for 8 full passes. Each pass has 10 tests and each pass tests something different. It will take several hours to run 8 passes, best to run overnight. Also run Furmark, but keep close watch on GPU temps and shut it down if they get too high. Video Card - Stress Test with Furmark. Let us know how everything goes.

    If you continue having problems, read and follow this Blue Screen of Death (BSOD) Posting Instructions and start a thread in https://www.sevenforums.com/bsod-help-support/ Putting the file resulting from the test above in your first post. You should also go to C:/Windows/minidump copy that folder and paste it on your desktop (you'll have to provide admin permissions) right click the file on your desktop, select send to and click compressed zip folder. Upload that along with the Seven Forums diagnostic report zip file.

    EDIT: I have requested this post be moved to the BSOD help forum, linked to above.
      My Computer


  3. Posts : 19
    Windows 7 32 bit
    Thread Starter
       #3

    so, i tried to do memtest again, and it got stuck at 51%. Yes, memtest froze, time wasn't moving or anything, i couldn't use hotkeys, only thing that was happening is that the + was still blinking. So yea, i don't think this is a ram issue.
      My Computer

  4.    #4
      My Computer


  5. Posts : 19
    Windows 7 32 bit
    Thread Starter
       #5

    hi bluerobot, sorry about not putting mindump, my thread was moved here. Anyway, I added those minidumps now.
      My Computer

  6.    #6

    Don't worry, can you please follow the instructions, so we can narrow down the possible cause.
      My Computer


  7. Posts : 19
    Windows 7 32 bit
    Thread Starter
       #7

    Ok, I got my first real bsod. It didn't just froze, I actually saw bsod screen, but this time it's a different error code. Here is the dump:
      My Computer


  8. Posts : 26,863
    Windows 11 Pro
       #8

    Kingofthehill, What brand PSU do you have? With your graphics card, AMD recommends a 400Watt PSU. You have listed in your specs, a 430W PSU. That puts it right on the border line. Depending on the manufacturer, many PSU's really won't put out their rated values and if they do, will only do it for a short time. They will also degrade after some time. If you have a friend who has another PSU, I would try that to either determine the PSU as the problem or rule it out as the problem. I would certainly try to borrow one rather than spend money on something you don't know for sure is the issue.

    Memtest runs out of ram, it has nothing to do with the OS. If you froze while doing the memtest, it does not necessarily rule out ram as the issue. But, it does for the most part, indicate a hardware issue.
      My Computer

  9.    #9

    Code:
    BugCheck 1000008E, {c0000005, 949ce5da, a3552ab0, 0}
    
    Probably caused by : memory_corruption
    Code:
    Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
    Code:
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
        949ce5d9 - win32k!RGNOBJ::vCopy+8
    	[ 7d:fd ]
    1 error : !win32k (949ce5d9)
    Code:
    1: kd> !chkimg -lo 50 -db !win32k
    1 error : !win32k (949ce5d9)
    949ce5d0  90  8b  ff  55  8b  ec  56  57  8b *fd  08  8b  07  83  c0  30 ...U..VW.......0
    We can see that the module has become corrupted for some reason, I highly suspect hardware.

    I managed to find this driver within the raw stack:

    Code:
    1: kd> lmvm atikmdag
    start    end        module name
    93024000 9395a000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 06 02:44:39 2012 (4F7E4A87)
        CheckSum:         008EDADD
        ImageSize:        00936000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Please update to the latest WHQL driver available from here: AMD Graphics Drivers & Software

    WHQL
    Release Date: April 24th 2013
    Version: 13.4
    In Device Manager: 12.104
    Code:
    BugCheck 124, {0, 84f564dc, 0, 0}
    
    Probably caused by : GenuineIntel
    Code:
    Usual causes:  Hardware, Incompatibility, May be driver corruption
    Code:
    1: kd> !errrec 84f564dc
    ===============================================================================
    Common Platform Error Record @ 84f564dc
    -------------------------------------------------------------------------------
    Record Id     : 01ce6e7d6ae867cb
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 6/21/2013 12:47:02 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ 84f5655c
    Section       @ 84f56634
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x86
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x0000000000000f34
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ 84f565a4
    Section       @ 84f566f4
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 34 0f 00 00 00 08 02 00 - 1d 44 00 00 ff fb eb bf
                    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  @ 84f566f4
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ 84f565ec
    Section       @ 84f56774
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Internal timer (Proc 0 Bank 0)
      Status      : 0xa200000084010400
    The first parameter or argument has the value of 0x0, which is a Machine Check Exception, which means the CPU has detected a hardware problem and the address points to a processor error because the CPU has found one, so it could be a different form of hardware which is causing the issue.

    In such a situation, it is best to use these steps:


    All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.
      My Computer


  10. Posts : 19
    Windows 7 32 bit
    Thread Starter
       #10

    anyway, today, after a couple of freezes, it worked fine for like 3-4 hours, then it froze, and since then i can't turn it on. Fans are spinning, keyboard seems to work too, but monitor doesn't turn on and nothing seems to happen.
      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 19:36.
Find Us