BSOD Since Upgrading from 7 to 10.


  1. Posts : 4
    Windows 10
       #1

    BSOD Since Upgrading from 7 to 10.


    BSOD has only been occurring since the upgrade to Windows 10.

    When: Happens all the time -- Immediately on start up, while browsing on internet (Edge, Chrome), while watching videos (DVD on VLC player), or while browsing explorer folders. All the time.

    What I've done so far: Windows Updates, Malwarebytes (Cleaned everything), Windows Memory Diagnostic (no issues), chkdsk (no issues but have done a reinstall of Windows 10 --keeping personal files). WhoCrashed revealed that it's the "hal.dll" with Bugcheck code: 0x124. Used Tweakbit Driver Updater (haven't updated yet) and it found 13 outdated drivers that I'll list below:

    1: Microsoft ACPI-Compliant Control Method Battery
    2: Quaalcomm Atheros AR8162/8166/8168 PCI-E Fast Ethernet Controller (NDIS 6.30)
    3: Realtek RTL8188CE Wireless LAN 802.11n PCI-E NIC
    4: Toshiba Firmware Linkage Driver
    5: Realtek High Definition Audio
    6: PCI standard ISA bridge
    7: Toshiba x6 ACPI-Compliant Value Added Logical and General Purpose Device
    8: PCI Express Root Complex
    9: Standard SATA AHCI Controller
    10: Realtek USB 2.0 Card Reader
    11: AMD High Definition Audio Device
    12: High Definition Audio Controller
    13: Standard PS/2 Keyboard

    Used Coretemp but with this processor the temp just shows 0. Went into BIOS and set to default in case anything was changed (which I don't think it was). That's about it.

    Any help is much appreciated.

    Thank you.
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    warning   Warning
    Programs that claim to update your drivers install either the wrong or corrupted drivers.

    Remove Tweakbit a.s.a.p.

    The fetched data on the level 1 cache were corrupted when the CPU tried to execute it.
    Code:
    0: kd> !errrec ffffe00072212028
    ===============================================================================
    Common Platform Error Record @ ffffe00072212028
    -------------------------------------------------------------------------------
    Record Id     : 01d11b4caecb69a6
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 11/10/2015 19:41:32 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000722120a8
    Section       @ ffffe00072212180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Instruction Execute
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000610f01
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000722120f0
    Section       @ ffffe00072212240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 01 0f 61 00 00 08 04 00 - 0b 32 98 3e 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  @ ffffe00072212240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00072212138
    Section       @ ffffe000722122c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : ICACHEL1_IRD_ERR (Proc 0 Bank 1)
      Status      : 0xb080000000060151
    The errors are 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
    This means that there are problems with your hardware, but this error is also caused by overclocking, faulty drivers or BIOS problems.



    STOP 0x124 Troubleshooting

    Read carefully before proceeding.



    warning   Warning
    If you're overclocking your system, revert back to stock clocks now.

    Note   Note
    Test the system once the overclock is removed before continuing with the steps outlined below.


    Part One: CPU Stress Test
    Part Two: MemTest86+ RAM Diagnostic
    Part Three: Hard Drive Diagnostics
    Part Four: GPU Stress Test




    ONE

     CPU TEST


    Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.





    TWO

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking forzero errors here. Even a single error will indicate RAM failure.





    THREE

     HDD TEST


    Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html




    FOUR

     GPU TEST


    Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

    Note   Note
    Run Furmark for around 30 minutes.

    warning   Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.


    Old drivers:
    Code:
    FwLnk        Tue Jul 10 10:35:43 2012 (4ffbe95f)        FwLnk.sys    
    TVALZ_O        Thu Jul 26 01:23:25 2012 (50107fed)        TVALZ_O.SYS    
    RTKVHD64        Wed Dec 05 12:58:07 2012 (50bf36cf)        RTKVHD64.sys    
    L1C63x64        Mon Apr 01 05:15:17 2013 (5158fbc5)        L1C63x64.sys    
    AODDriver2        Tue Feb 11 12:06:52 2014 (52fa044c)        AODDriver2.sys
    Check your manufacturer for driver updates (links added so you might easier know what they belong to)
    Driver Reference Table - FwLnk.sys
    Driver Reference Table - TVALZ_O.SYS
    Driver Reference Table - RTKVHD64.sys


    Remove AODDriver2, it is a driver known for causing BSOD's.
    Code:
    C:\program files\ati technologies\ati.ace\fuel\amd64\aoddriver2.sys
      My Computers


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    Removed Tweakbit.

    Ran Prime95 and everytime it hasn't been able to finish because of the BSOD.

    Ran Memtest86+ and everything was good.

    Ran Seatools for the Short Drive Test and Short Generic Test with no errors but Long Generic wasn't able to finish without BSOD.

    Haven't tried the FurMark GPU Test yet.

    Updated Drivers and Removed "AODDriver2".

    Restart Laptop now and if the BSOD's continue I will try what I haven't done thus far.

    Thank you for your help.
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4

    Keep me posted
      My Computers


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    Ran FurMark and passed with flying colors.

    Was finally able to run the Long Generic test for SeaTools which was pretty surprising as I couldn't get passed 30 something % in all the previous attempts without a BSOD. (Fixed?! maybe??)

    Last test I have is the Prime95 and I've had tons of BSOD attempts with it before.

    Will update you when finished.

    Thanks again for your help.
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #6

    You're welcome :)

    Please let me know how it goes.
      My Computers


  7. Posts : 4
    Windows 10
    Thread Starter
       #7

    And again amazingly Prime95 has finished testing all the way through (3 hours) without BSOD.

    I will now turn the laptop off and hand over to it's owner for regular use (internet/video, etc.) to see if there's any BSOD in the next few days. If there isn't I think we'll be able to Mark as Solved. q

    Thanks and will keep ya posted.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:29.
Find Us




Windows 10 Forums