Windows 8 and 8.1 Forums


BSOD usually while Gaming,WHEA_UNCORRECTABLE_ERROR Evt. 41

  1. #1


    Posts : 12
    Win 8.1 x64 Student Pro

    BSOD usually while Gaming,WHEA_UNCORRECTABLE_ERROR Evt. 41


    I'm at a point where I can't figure out anymore. My new build is giving me BSODs randomly, but usually only while tasking my PC while running games like WoW. Running WhoCrashed, I'm seeing a recurring theme of BugCheck code 0x124, Parameter 1 0x0, Parameter 2 Varies, Parameter 3 0xBF800000, Parameter 4 0x124, and probably caused by hal.dll.

    Now this is a new Corsair RM1000w PSU, 4790k i7, Asus Maximus VII Hero, Sapphire R9 290x, Intel SSD, and Win 8.1 Student Pro Full. I've updated my drivers, I've had this persist through 2 Bios revisions, and metered wall power to check for variations. Nothing changes. As I only have a small window to return faulty hardware, I'd like to get this figured out ASAP. I ran both tools required on the forums, and I'll upload the logs. Thank you in advance for your help.

    One thing I'll mention, that may help. I initially installed Win8.1 on a backup drive, booted to it, copied my files off of my SSD, and then reformatted and installed Windows from boot on the SSD. However, when I installed Windows on my SSD, I didn't remove my backup drive from the system. It left the bootloader and system partiton on the backup drive. Even though it would boot to my SSD, if I removed the backup drive, I got the old hal.dll missing or corrupted errors. Using a partition program, I copied the system partition from the backup drive to the SSD, and it has worked without the backup drive installed. I'm not sure if moving this partition caused the problems, if I need to install windows fresh and have it make a new system partition from disk, if it can be repaired, or if it's even the issue. I simply thought I should make it known in the interest of disclosure. Thanks!
    Last edited by evolutionadam; 10 Oct 2014 at 09:36. Reason: added attachment w/ driver verifier bsod dump

      My System SpecsSystem Spec

  2. #2


    Posts : 2,480
    Windows 10 Pro x64


    In you are doing ANY over-clocking stop all until the issues are resolved.

    BCCode: 124 0x00000124

    This is usually heat related, defective hardware, memory or even processor though it is
    "possible" that it is driver related (rare). Remove ALL power and reseat all cards, memory
    and cables (on both ends) - actually remove and replace - do not just snug. Make sure
    the system has adequate ventilation - add a small fan blowing into intakes. Carefully
    inspect the motherboard and other cards for damage. Pay attention to the fatal hardware
    error
    implication.You may need a real computer shop.

    Check the processor seatting, heat sink, and the compound between the processor and
    the heat sink which are common causes.

    There have been a few instances where Norton/Symantec and other antivirus/security
    programs have caused this error.

    BCCode: 124 0x00000124

    The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. 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).
    Run memTest : RAM - Test with Memtest86+ - Windows 7 Help Forums
    Post Back.
      My System SpecsSystem Spec

  3. #3


    Posts : 12
    Win 8.1 x64 Student Pro


    Also, once the computer reboots from the BSOD, my Linksys AE2500 wireless adapter does not work until I unplug it and plug it back in. It simply says it can't find any network. Everything else works to my knowledge. I'm not overclocking at all. Everything is set to factory settings.
      My System SpecsSystem Spec

  4. #4


    Posts : 2,480
    Windows 10 Pro x64


    I looked all over their website and it appears that there is no Win 8 driver yet. The latest one is for W7 dating back to 2011. Try this method: https://community.linksys.com/t5/Wir.../497576/page/2
      My System SpecsSystem Spec

  5. #5


    Posts : 12
    Win 8.1 x64 Student Pro


    I installed the Win7 driver for the NIC. It allowed me to connect to my 5.8 ghz band, as before I was only able to conenct to my 2.4ghz band, though both appeared. It had been running whatever driver windows installed automatically. Is there a chance that the AE2500 was causing the crashes? I ran Heaven Benchmark at max settings for 3 hours, Intel SSD toolbox checked my drive w/ no errors, prime95 ran for 3 hours w/ no errors. Going to run memtest overnight tonight.
      My System SpecsSystem Spec

  6. #6


    Posts : 2,480
    Windows 10 Pro x64


    It is possible that a driver is causing this. Yes.
      My System SpecsSystem Spec

  7. #7


    Posts : 12
    Win 8.1 x64 Student Pro


    Still happening with new NIC drivers. Where should I be at now? Wipe and re-install windows? Then breadboard the whole desktop again?
      My System SpecsSystem Spec

  8. #8


    Posts : 2,480
    Windows 10 Pro x64


    Please enable Driver Verifier. When your system crashes again post a new BSOD dump file with Driver Verifier enabled.
      My System SpecsSystem Spec

  9. #9


    Posts : 12
    Win 8.1 x64 Student Pro


    Enabled driver verifier and had BSOD w/ driver verifier instead of the WHEA_UNCORRECTABLE. Attached it as Evolutionadam2.zip. Thanks!
      My System SpecsSystem Spec

  10. #10


    Posts : 2,480
    Windows 10 Pro x64


    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
    Arg2: ffffe000d4b427e8, name of the driver having the issue.
    Arg3: ffffe000d4b42620, verifier internal structure with driver information.
    Arg4: 0000000000000002, total # of (paged+nonpaged) allocations that weren't freed.
        Type !verifier 3 drivername.sys for info on the allocations
        that were leaked that caused the bugcheck.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_62
    
    IMAGE_NAME:  avgtpx64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b146c5
    
    MODULE_NAME: avgtpx64
    
    FAULTING_MODULE: fffff80065335000 avgtpx64
    
    VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffe000d4b42620
    Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  DriverInstalle
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff803c5af46b0 to fffff803c55d2ca0
    
    STACK_TEXT:  
    ffffd000`e0cf84e8 fffff803`c5af46b0 : 00000000`000000c4 00000000`00000062 ffffe000`d4b427e8 ffffe000`d4b42620 : nt!KeBugCheckEx
    ffffd000`e0cf84f0 fffff803`c5af8c52 : fffff800`65335000 ffffe000`d4b42730 00000000`00000000 00000000`ffffffff : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`e0cf8530 fffff803`c562d4b0 : 00000000`00000000 00000000`00001000 0000007f`00000001 ffffe000`d0044750 : nt!VfPoolCheckForLeaks+0x4a
    ffffd000`e0cf8570 fffff803`c5ae609c : fffff803`c572e630 fffff803`c572e630 ffffe000`d4b42730 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4a300
    ffffd000`e0cf8600 fffff803`c593fef2 : 00000000`00000000 ffffe000`d4b42730 00000000`00000000 ffffe000`d4b42110 : nt!VfDriverUnloadImage+0x34
    ffffd000`e0cf8630 fffff803`c593fe5c : 00000000`00000010 ffffe000`d4b42730 ffffe000`d4b42110 00000000`00000018 : nt!MiUnloadSystemImage+0x7e
    ffffd000`e0cf86b0 fffff803`c59406da : 00000000`00000000 ffffe000`d00a2900 ffffe000`d4b42110 00000000`00010286 : nt!MmUnloadSystemImage+0x20
    ffffd000`e0cf86e0 fffff803`c586fec4 : 00000000`00000000 ffffe000`d4b42110 ffffe000`d00a2900 ffffc000`5946f368 : nt!IopDeleteDriver+0x4e
    ffffd000`e0cf8720 fffff803`c54ce91f : 00000000`00000000 ffffd000`e0cf8840 ffffe000`d4b42110 ffffe000`d4b42110 : nt!ObpRemoveObjectRoutine+0x64
    ffffd000`e0cf8780 fffff803`c5619515 : ffffe000`d4afb420 ffffcf81`a3596e00 ffffe000`d4b42110 fffff803`00000000 : nt!ObfDereferenceObject+0x8f
    ffffd000`e0cf87c0 fffff803`c5502c76 : ffffe000`d4afb420 00000000`00000000 ffffe000`d4afb420 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36365
    ffffd000`e0cf8880 fffff803`c58548bf : ffffe000`d88e35c0 00000000`00000000 ffffcf81`a3596ea0 00000000`00000000 : nt!IopDecrementDeviceObjectRef+0xee
    ffffd000`e0cf88c0 fffff803`c586fec4 : 00000000`00000000 ffffe000`d88e35c0 ffffe000`d00a37a0 ffffe000`d88e3590 : nt!IopDeleteFile+0x19b
    ffffd000`e0cf8940 fffff803`c54cea2f : 00000000`00000000 ffffd000`e0cf8a99 ffffe000`d88e35c0 ffffe000`d00a37a0 : nt!ObpRemoveObjectRoutine+0x64
    ffffd000`e0cf89a0 fffff803`c5853bb4 : ffffe000`d88e3590 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0x8f
    ffffd000`e0cf89e0 fffff803`c55de4b3 : 00000000`00000008 ffffffff`ffffffe0 00000000`00000000 00000000`00000000 : nt!NtClose+0x204
    ffffd000`e0cf8b00 00007ffe`a6cd176a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0058f718 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`a6cd176a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_avgtpx64.sys
    
    BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_avgtpx64.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc4_62_vrf_leaked_pool_image_avgtpx64.sys
    
    FAILURE_ID_HASH:  {a6894198-e67a-9c4a-f34e-4ac8372d8d49}
    
    Followup: MachineOwner
    ---------
    AVG Secure Search is causing the crash : Driver Reference Table - avgtpx64.sys
    Please remove AVG using this tool: http://download.avg.com/filedir/util..._2015_5501.exe
    After having done all that report back.
      My System SpecsSystem Spec

Page 1 of 3 123 LastLast
BSOD usually while Gaming,WHEA_UNCORRECTABLE_ERROR Evt. 41
Related Threads
Bsod whea_uncorrectable_error in BSOD Crashes and Debugging
Bought computer from a friend and been running into this issue and struggling to figure out what exactly is causing it. I've nailed it down to either drivers or hardware but I don't know where to go from here to fix the problem. The issue doesn't seem to occur during any certain action. Gaming,...
BSOD whea_uncorrectable_error in BSOD Crashes and Debugging
Hello. I have been getting random BSOD while i surf on the internet. This is not the first time it happen. this is +15 times now and it broke my PC 3 times. i had to waste my whole time to re-format my PC 3 times. The BSOD WHEA_UNCORRECTABLE_ERROR is extremely dangerous because it can broke...
BSOD WHEA_UNCORRECTABLE_ERROR out of nowhere in BSOD Crashes and Debugging
Hello I have a problem with my PC getting the WHEA_UNCORRECTABLE_ERROR bsod. It is a few months old pc. I am not overclocking or changing anything in bios, but sometimes (this is my third time) I get this bsod out of nowhere. This last time I was just watching some stream on twitch when the pc...
Bsod whea_uncorrectable_error (124) in BSOD Crashes and Debugging
Hello, I've had problems with my PC for a while. Used Windows 7 before, it oftenly crashed(especially while playing games). I used to get 0x124 BSOD. I thought it there might be a problem with cooling. My case was broken and one side couldn't be fully closed. I bought a new case, dusted away as...
WHEA_UNCORRECTABLE_ERROR BSOD help! in BSOD Crashes and Debugging
Edited for proper format! Hi, I recently moved my computer from one house to another and with now hardware/software changes I've been getting BSOD everyday since I set it up and running at the new house. I hadn't changed anything. I also checked to make sure everything was seated properly...
BSOD - whea_uncorrectable_error in BSOD Crashes and Debugging
Hello everyone :D Im new to Windows 8. My computer crash while surfing on news sites with video or in computer games after 10 sek in there. The computer is brand new! See my attachment please
Eight Forums Android App Eight Forums IOS App Follow us on Facebook