Windows 10: BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update

Discus and support BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update in Windows 10 BSOD Crashes and Debugging to solve the problem; So basically i started getting intermittent reboots with bugcheck 0x000000ea error. The machine has been very stable until the fall update and has... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by titch, Nov 3, 2017.

  1. titch Win User

    BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update


    So basically i started getting intermittent reboots with bugcheck 0x000000ea error.

    The machine has been very stable until the fall update and has BSOD'd at least once a day almost every day barring two since installing the fall update(it did not bugcheck the day after or yesterday) On both occasions it did not bugcheck this could easily have been down to the fact it wasnt on long enough or sitting idle long enough to error.

    This usually happens about once a day and after the system has been on for a while and then running idle(sleep is not set but screen timeout is 5 minutes.

    The quickest this has happened has been after about 2 hours and tonight the computer was on for over 8 hours and idle for estimate 2/3 hours.

    So far i have ensured the video drivers are the latest version, and older pre issue version and the AMD fall update beta version. The sound card drivers Realtek HD have been updated via device manager. I was previously running avast and removed this to run Windows Defender(just to rule out any issues).

    I have now changed the power settings to screen timeout 3m and sleep mode after 30m to see if this has any impact.

    Posting this looking for both assistance with this error and to see if anyone else has experienced any similar issues since the fall update.

    Cheers

    :)
     
    titch, Nov 3, 2017
    #1
  2. PCuseless Win User

    Windows 10 bugcheck 0x000000ea

    Same f problem

    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ea (0xffffc08721a75080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6eab03b4-1aab-4830-a984-334021b8b087.
    1 week pc with win 10 anniversary update rx 480 nitro+ oc 8gb/fx 8350 cpu
     
    PCuseless, Nov 3, 2017
    #2
  3. Windows 10 bugcheck 0x000000ea

    Hi Pativet,

    Haven't found anything that definitely fixes it. I've had the latest drivers from AMD's site installed for a couple of days now, and no bugcheck yet. But I'm pretty sure I tried the same version earlier and still experienced the problem. I noticed a link
    for reporting driver problems
    here
    that I will use if I hit this again.

    Are you running the latest driver release (not the beta)? If not, try that and see if the bugchecks stop. Otherwise I'd file a report at the above site.

    Good luck!
     
    Easy Rhino, Nov 3, 2017
    #3
  4. zbook New Member

    BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update

    Hi titch ,

    Welcome to Ten Forums BSOD forum.

    Please update the system specs in the "My Computer" section:

    How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums General Tips Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums


    Open administrative command prompt and copy and paste this command:
    Code: copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"[/quote] The files will appear on the desktop. Use one drive or drop box share links to post into the thread.


    The debugging indicated problems related to the graphics card.

    Bugcheck 0xEA: THREAD_STUCK_IN_DEVICE_DRIVER

    This indicates that a thread in a device driver is endlessly spinning.

    A device driver is spinning in an infinite loop, most likely waiting for hardware to become idle.

    This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. Frequently, this is the result of a bad video card or a bad display driver.

    The plan is to update the video card driver and then stress test the video card.

    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan
    4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    5) Find the memory dump file and post a one drive or drop box share link into the thread:
    memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP
    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    6) Make sure that there is no over clocking while troubleshooting.
    7) Sometimes there are problems in the bios that produce bsod.
    8) The BIOS: Version F5 Release 05/30/2014
    9) Please check to see if this is the most up to date version.
    10) To ensure that there are no improper bios settings please reset the bios.
    11) Sometimes there can be failure to boot after resetting the bios.
    12) So please make sure your files are backed up.
    13) Please make a backup image with Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Your Image is Everything
    Macrium Software | Macrium Reflect Free
    14) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    15) The misbehaving drivers were:
    atikmdag.sys
    atikmpag.sys

    Perform the following steps:
    16) Uninstall everything AMD using Display driver uninstaller and install new drivers from the computer manufacturer's/motherboard manufacturer's website or the AMD website.
    17) The computer manufacturer's/motherboard manufacturer's website is preferred.
    18) Enter the computer's serial or product number and the operating system to view available drivers.
    19) If you use the AMD web site be sure the "clean install" box is checked and only install the graphics driver.
    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller Download version 17.0.7.2
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    AMD Support and Radeon Software Driver Download
    AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums

    20) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:

    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Speccy - System Information - Free Download


    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID


    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    21) a) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab click startup and recovery > post an image into the thread.
    b) on the advance tab click under performance click on settings > under performance options click on the advanced tab > under virtual memory click on change > post an image into the thread.

    22) For any new BSOD please post an updated zip:
    BSOD - Posting Instructions - Windows 10 Forums






    Code: 26/10/2017 14:33 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffff848bcb540700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102617-8031-01.dmp \\?\C:\WINDOWS\TEMP\WER-9578-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A96.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A97.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AA8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_13e59763b53eadda8eaee458b9dfed65c69046f_00000000_cab_02ec4aa5 Analysis symbol: Rechecking for solution: 0 Report ID: f184ee40-74d2-41d5-8a73-ed883eaa1674 Report Status: 4 Hashed bucket: 24/10/2017 17:50 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffff8a8846188080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102417-7906-01.dmp \\?\C:\WINDOWS\TEMP\WER-9437-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46A2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46A6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46B6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_a22394c8f082bbe18adc14ce858074c6c71fc1_00000000_cab_02e046ad Analysis symbol: Rechecking for solution: 0 Report ID: 0a1d22f6-c4d9-47f5-9529-145e68b5ffa7 Report Status: 4 Hashed bucket: 01/11/2017 21:02 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffa90eaf47c080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110117-8328-01.dmp \\?\C:\WINDOWS\TEMP\WER-10031-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45F2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4631.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_af43b3c3696cd04d1834966b2c2fbddadcc26a8e_00000000_cab_03484630 Analysis symbol: Rechecking for solution: 0 Report ID: 6ebc0c3b-57df-4dd7-8ebe-c90174720ea9 Report Status: 4 Hashed bucket: 26/10/2017 20:22 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffb30c1ba80080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102617-7843-01.dmp \\?\C:\WINDOWS\TEMP\WER-9375-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4547.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4548.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4549.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_d89cdcdecaedf46359efbcf18d393453cb3db_00000000_cab_02f44556 Analysis symbol: Rechecking for solution: 0 Report ID: d05b14b8-deee-4680-a32d-acda8fb47810 Report Status: 4 Hashed bucket: 30/10/2017 01:13 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffb60be20dc300 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-10765-01.dmp \\?\C:\WINDOWS\TEMP\WER-12593-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5044.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5046.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5057.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_6b7e56c578c7a7999115cf5a315ba65382f950ee_00000000_cab_02f05052 Analysis symbol: Rechecking for solution: 0 Report ID: 4bfb3ab8-1731-47d1-8609-5a559c5a32bc Report Status: 4 Hashed bucket: 04/11/2017 01:03 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffc50e1a315080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110417-8250-01.dmp \\?\C:\WINDOWS\TEMP\WER-9921-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4268.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4277.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42A7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_63874ea35dd5585ee7bbfcfad2d4841d3b84583_00000000_cab_02e042a6 Analysis symbol: Rechecking for solution: 0 Report ID: e786a982-2540-4ae2-be85-637db4d09a6b Report Status: 4 Hashed bucket: 25/10/2017 18:52 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffcb0028697700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102517-7906-01.dmp \\?\C:\WINDOWS\TEMP\WER-9421-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_1ec453d158b37266e9a88790bdf4faf1e0563_00000000_cab_02e445d3 Analysis symbol: Rechecking for solution: 0 Report ID: 32452c3d-32f6-43d5-b02e-1e4c72481890 Report Status: 4 Hashed bucket: 30/10/2017 21:03 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffd88c961f7300 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-8359-01.dmp \\?\C:\WINDOWS\TEMP\WER-10062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4873.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4874.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4895.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_559789dc290298f115dd4c6f7258385137445cd_00000000_cab_02f84892 Analysis symbol: Rechecking for solution: 0 Report ID: c0eb2f96-d88b-4c6a-a58f-250b8f1d78e4 Report Status: 4 Hashed bucket: 28/10/2017 19:42 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffde8019db6700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102817-8140-01.dmp \\?\C:\WINDOWS\TEMP\WER-9671-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4826.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4828.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4839.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_dac08db0c9c0fa27e746628b1df1f45fe119068_00000000_cab_02e44834 Analysis symbol: Rechecking for solution: 0 Report ID: dd58b8ad-fd09-4a5d-8be1-861736b06ce7 Report Status: 4 Hashed bucket: 24/10/2017 23:00 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffdf8c0cbba700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102517-8593-01.dmp \\?\C:\WINDOWS\TEMP\WER-10140-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AE4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AE5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AF6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_ceafa6181195baf62ca8b8610844e7d4d352db3_00000000_cab_02e04af3 Analysis symbol: Rechecking for solution: 0 Report ID: 28ac7660-48eb-481d-96a4-c5e913c339c0 Report Status: 4 Hashed bucket: 31/10/2017 19:01 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: ea P2: ffffe60be94ca080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103117-8218-01.dmp \\?\C:\WINDOWS\TEMP\WER-9937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46E2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46F3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_7078a119ce89671f85523b45bd228a2da4e1856_00000000_cab_02f446ec Analysis symbol: Rechecking for solution: 0 Report ID: 7025c0ae-faef-4e50-aa34-c86f163fc1ee Report Status: 4 Hashed bucket: 24/10/2017 19:24 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: deac2459-7a26-43e3-8e3f-d0dd99c75ff3 Problem signature: P1: ea P2: ffff8a8846188080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102417-7906-01.dmp \\?\C:\WINDOWS\TEMP\WER-9437-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46A2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46A6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46B6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ea_a22394c8f082bbe18adc14ce858074c6c71fc1_00000000_cab_02e046ad Analysis symbol: Rechecking for solution: 0 Report ID: 0a1d22f6-c4d9-47f5-9529-145e68b5ffa7 Report Status: 4 Hashed bucket:[/quote] Code: 28/10/2017 20:29 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 26c3722b-50de-4a61-846c-4aac7cea68a4 Problem signature: P1: ea P2: ffffde8019db6700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102817-8140-01.dmp \\?\C:\WINDOWS\TEMP\WER-9671-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4826.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4828.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4839.tmp.txt \\?\C:\Windows\Temp\WER5583.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_dac08db0c9c0fa27e746628b1df1f45fe119068_00000000_cab_08d8590c Analysis symbol: Rechecking for solution: 0 Report ID: dd58b8ad-fd09-4a5d-8be1-861736b06ce7 Report Status: 268435456 Hashed bucket: 30/10/2017 17:22 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 37d39eda-baa8-4d78-a9bb-9245c91947da Problem signature: P1: ea P2: ffffb60be20dc300 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-10765-01.dmp \\?\C:\WINDOWS\TEMP\WER-12593-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5044.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5046.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5057.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_6b7e56c578c7a7999115cf5a315ba65382f950ee_00000000_cab_1fe6d423 Analysis symbol: Rechecking for solution: 0 Report ID: 4bfb3ab8-1731-47d1-8609-5a559c5a32bc Report Status: 268435456 Hashed bucket: 26/10/2017 21:21 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 4ab7cca9-01ab-417d-bddf-dc0c21c2cee0 Problem signature: P1: ea P2: ffffb30c1ba80080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102617-7843-01.dmp \\?\C:\WINDOWS\TEMP\WER-9375-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4547.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4548.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4549.tmp.txt \\?\C:\Windows\Temp\WERDF54.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_d89cdcdecaedf46359efbcf18d393453cb3db_00000000_cab_08d5bc27 Analysis symbol: Rechecking for solution: 0 Report ID: d05b14b8-deee-4680-a32d-acda8fb47810 Report Status: 268435456 Hashed bucket: 24/10/2017 23:00 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 54261fd0-5ebc-4b60-a257-1b4221226cfd Problem signature: P1: ea P2: ffffdf8c0cbba700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102517-8593-01.dmp \\?\C:\WINDOWS\TEMP\WER-10140-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AE4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AE5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AF6.tmp.txt \\?\C:\Windows\Temp\WER64A6.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_ceafa6181195baf62ca8b8610844e7d4d352db3_00000000_cab_154c684f Analysis symbol: Rechecking for solution: 0 Report ID: 28ac7660-48eb-481d-96a4-c5e913c339c0 Report Status: 268435456 Hashed bucket: 31/10/2017 19:01 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 631db554-b27b-4283-b63a-9a966d408ec1 Problem signature: P1: ea P2: ffffe60be94ca080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103117-8218-01.dmp \\?\C:\WINDOWS\TEMP\WER-9937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46DF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46E2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46F3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_7078a119ce89671f85523b45bd228a2da4e1856_00000000_cab_16fc6159 Analysis symbol: Rechecking for solution: 0 Report ID: 7025c0ae-faef-4e50-aa34-c86f163fc1ee Report Status: 268435456 Hashed bucket: 04/11/2017 01:03 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 782740ee-90ea-420a-8d00-3b25ca9e501e Problem signature: P1: ea P2: ffffc50e1a315080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110417-8250-01.dmp \\?\C:\WINDOWS\TEMP\WER-9921-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4268.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4277.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42A7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_63874ea35dd5585ee7bbfcfad2d4841d3b84583_00000000_cab_14a46bba Analysis symbol: Rechecking for solution: 0 Report ID: e786a982-2540-4ae2-be85-637db4d09a6b Report Status: 268435456 Hashed bucket: 01/11/2017 21:33 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 7f8f3a8f-297a-4038-be75-65b6f699370b Problem signature: P1: ea P2: ffffa90eaf47c080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110117-8328-01.dmp \\?\C:\WINDOWS\TEMP\WER-10031-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45F2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4631.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_af43b3c3696cd04d1834966b2c2fbddadcc26a8e_00000000_cab_0978949e Analysis symbol: Rechecking for solution: 0 Report ID: 6ebc0c3b-57df-4dd7-8ebe-c90174720ea9 Report Status: 268435456 Hashed bucket: 26/10/2017 15:05 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 977f3487-1d20-4e1b-a7fd-866c0ecd6e83 Problem signature: P1: ea P2: ffff848bcb540700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102617-8031-01.dmp \\?\C:\WINDOWS\TEMP\WER-9578-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A96.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A97.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4AA8.tmp.txt \\?\C:\Windows\Temp\WER49FD.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_13e59763b53eadda8eaee458b9dfed65c69046f_00000000_cab_16454d19 Analysis symbol: Rechecking for solution: 0 Report ID: f184ee40-74d2-41d5-8a73-ed883eaa1674 Report Status: 268435456 Hashed bucket: 26/10/2017 09:21 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: bdc9ad9a-7c2a-44ca-9b95-3386ad19b557 Problem signature: P1: ea P2: ffffcb0028697700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102517-7906-01.dmp \\?\C:\WINDOWS\TEMP\WER-9421-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D6.tmp.txt \\?\C:\Windows\Temp\WER812C.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_1ec453d158b37266e9a88790bdf4faf1e0563_00000000_cab_2f93983d Analysis symbol: Rechecking for solution: 0 Report ID: 32452c3d-32f6-43d5-b02e-1e4c72481890 Report Status: 268435456 Hashed bucket: 24/10/2017 19:27 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: deac2459-7a26-43e3-8e3f-d0dd99c75ff3 Problem signature: P1: ea P2: ffff8a8846188080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102417-7906-01.dmp \\?\C:\WINDOWS\TEMP\WER-9437-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46A2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46A6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46B6.tmp.txt \\?\C:\Windows\Temp\WER7D6D.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_a22394c8f082bbe18adc14ce858074c6c71fc1_00000000_cab_13e180d7 Analysis symbol: Rechecking for solution: 0 Report ID: 0a1d22f6-c4d9-47f5-9529-145e68b5ffa7 Report Status: 268435460 Hashed bucket: 30/10/2017 21:16 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: e0dcb246-388e-4a3f-9f98-b8122ce83a2d Problem signature: P1: ea P2: ffffd88c961f7300 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\103017-8359-01.dmp \\?\C:\WINDOWS\TEMP\WER-10062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4873.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4874.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4895.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ea_559789dc290298f115dd4c6f7258385137445cd_00000000_cab_0624977d Analysis symbol: Rechecking for solution: 0 Report ID: c0eb2f96-d88b-4c6a-a58f-250b8f1d78e4 Report Status: 268435456 Hashed bucket:[/quote] Code: Name AMD Radeon R7 200 Series PNP Device ID PCI\VEN_1002&DEV_6658&SUBSYS_72601682&REV_00\4&1286464&0&0008 Adapter Type AMD Radeon Graphics Processor (0x6658), Advanced Micro Devices, Inc. compatible Adapter Description AMD Radeon R7 200 Series Adapter RAM (2,147,483,648) bytes Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\c0318962.inf_amd64_0a178257fb861d6f\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\c0318962.inf_amd64_0a178257fb861d6f\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\c0318962.inf_amd64_0a178257fb861d6f\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\c0318962.inf_amd64_0a178257fb861d6f\amdxc64.dll Driver Version 23.20.768.9 INF File oem11.inf (ati2mtag_R505DS section) Colour Planes Not Available Colour Table Entries 4294967296 Resolution 1920 x 1080 x 60 hertz Bits/Pixel 32 Memory Address 0xE0000000-0xFEAFFFFF Memory Address 0xF0000000-0xF07FFFFF I/O Port 0x0000E000-0x0000EFFF Memory Address 0xF7E00000-0xF7EFFFFF IRQ Channel IRQ 4294967289 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\c0318962.inf_amd64_0a178257fb861d6f\atikmpag.sys (23.20.768.9, 532.52 KB (545,296 bytes), 13/10/2017 17:32)[/quote] Code: Event[2750]: Log Name: System Source: Microsoft-Windows-Resource-Exhaustion-Detector Date: 2017-11-01T17:42:35.725 Event ID: 2004 Task: Resource Exhaustion Diagnosis Events Level: Warning Opcode: Contains the results of the diagnosis. Keyword: Events related to exhaustion of system commit limit (virtual memory). User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Boyd-Main Description: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: chrome.exe (10880) consumed 527138816 bytes, chrome.exe (6540) consumed 485486592 bytes, and chrome.exe (10404) consumed 439259136 bytes. Event[2751]: Log Name: System Source: Microsoft-Windows-Resource-Exhaustion-Detector Date: 2017-11-01T17:51:41.857 Event ID: 2004 Task: Resource Exhaustion Diagnosis Events Level: Warning Opcode: Contains the results of the diagnosis. Keyword: Events related to exhaustion of system commit limit (virtual memory). User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Boyd-Main Description: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: chrome.exe (6540) consumed 490872832 bytes, chrome.exe (10404) consumed 440528896 bytes, and chrome.exe (10880) consumed 415936512 bytes.[/quote] Code: Event[2752]: Log Name: System Source: Application Popup Date: 2017-11-01T17:55:00.086 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Boyd-Main Description: Application pop-up: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.[/quote]
     
    zbook, Nov 4, 2017
    #4
  5. titch Win User
    Hi zbook,

    Thanks for the info - i've completed a fresh w10 install after messing up a setting in the Component Services administrative tool when trying to resolve a DCOM error yesterday.

    I will run the computer as normal and see how things go tonight. If i still get the same bugcheck i will work my way through your instructions.
     
    titch, Nov 4, 2017
    #5
  6. titch Win User
    titch, Nov 4, 2017
    #6
  7. zbook New Member
    The misbehaving driver was the graphics driver.
    See the above post for removing and reinstalling this driver using DDU.

    If possible run the DM log collector as it will automatically collect the useful files. Then zip to post into the thread.
    BSOD - Posting Instructions - Windows 10 Forums

    Code: <Details><![CDATA[Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: f66168d3-f2fd-473f-8ccc-70fbc01ff9fa Problem signature: P1: 100000ea P2: ffffae08eb3eb700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\110517-8718-01.dmp \\?\C:\Windows\TEMP\WER-13609-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4110.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4140.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_b592037ffc3843e9c8b165d2c6e5d2161c1ada_00000000_cab_119c67e1 Analysis symbol: Rechecking for solution: 0 Report ID: 3953c289-ac55-46ba-a141-3097205106f4 Report Status: 268435456 Hashed bucket:]]></Details></Data><Data><Time><![CDATA[05/11/2017 19:27]]></Time><Type><![CDATA[Windows Error Reporting]]></Type><Details><![CDATA[Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 100000ea P2: ffffae08eb3eb700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\110517-8718-01.dmp \\?\C:\Windows\TEMP\WER-13609-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4110.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4140.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_b592037ffc3843e9c8b165d2c6e5d2161c1ada_00000000_cab_02b4414e Analysis symbol: Rechecking for solution: 0 Report ID: 3953c289-ac55-46ba-a141-3097205106f4 Report Status: 4 Hashed bucket:]]></Details></Data>[/quote]
     
    zbook, Nov 4, 2017
    #7
  8. titch Win User

    BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update

    Microsoft Windows [Version 10.0.16299.19](c) 2017 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.19[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.

    C:\Windows\system32>chkdsk /scanThe type of the file system is NTFS.

    Stage 1: Examining basic file system structure ... 225536 file records processed.File verification completed. 3198 large file records processed. 0 bad file records processed.
    Stage 2: Examining file name linkage ... 3867 reparse records processed. 309630 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 3867 reparse records processed.
    Stage 3: Examining security descriptors ...Security descriptor verification completed. 42048 data files processed.CHKDSK is verifying Usn Journal... 41728952 USN bytes processed.Usn Journal verification completed.

    Windows has scanned the file system and found no problems.

    No further action is required.
    116589567 KB total disk space.
    39032424 KB in 184844 files.
    115944 KB in 42049 indexes.
    0 KB in bad sectors.
    337687 KB in use by the system.
    65536 KB occupied by the log file.
    77103512 KB available on disk.
    4096 bytes in each allocation unit.
    29147391 total allocation units on disk.
    19275878 allocation units available on disk.
    C:\Windows\system32>
     
    titch, Nov 4, 2017
    #8
  9. titch Win User
    Uploaded .zip as requested also copied file to same one drive share. Edit this is pre driver update

    Again thanks for your assistance
     
    titch, Nov 4, 2017
    #9
  10. titch Win User
    Current MS installed AMD driver removed DDU safe mode and installed latest minimal AMD driver 17.7.2

    Will now leave on test.

    Thanks again
     
    titch, Nov 5, 2017
    #10
  11. zbook New Member
    Please run though the steps in the earlier post by number.
    Let us know which steps you were or not able to complete.
    Also post a URL into the link for the website for drivers for the PC.
     
    zbook, Nov 5, 2017
    #11
  12. titch Win User
    System properties info as requested - cheers

    BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update [​IMG]
     
    titch, Nov 5, 2017
    #12
  13. zbook New Member

    BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update

    In the system failure section un-check automatically restart.
    This will give you time to view the BSOD window.
    At times in addition to the bugcheck you may be able to see the misbehaving driver in the form *.sys
     
    zbook, Nov 5, 2017
    #13
  14. titch Win User
    1) - 4) Done - See attached info on previous post

    5) Find the memory dump file and post a one drive - posted to same one drive

    6) Make sure that there is no over clocking while troubleshooting. - Done

    7) - 14) Still running an older version of BIOS - BIOS Settings are still default from original install - will carry out BIOS upgrade tomorrow when time is less restictive. Files are already backed up on other drive so clean install is no issue.

    15) - 19) All done#

    20) Installed all three - Speccy log file and HWInfo text file both uploaded to one drive shared folder
     
    titch, Nov 5, 2017
    #14
  15. titch Win User
    GA-Z97P-D3 (rev. 1.0) | Motherboard - GIGABYTE


    link to mobo drivers

    Thanks again

    Changed automatic boot setting and will report back on next failure.

    As this is very intermittent this will most likely not happen again till tomorrow night although another failure is possible so will post info also memory dump file has now uploaded to one drive

    Thanks again.
     
    titch, Nov 5, 2017
    #15
Thema:

BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update

Loading...
  1. BSOD on Idle, Bugcheck 0x000000ea daily since Fall Update - Similar Threads - BSOD Idle Bugcheck

  2. Computer freezing daily since last update

    in Windows 10 BSOD Crashes and Debugging
    Computer freezing daily since last update: My machine has been freezing daily since the last update, it never did that before. I tried looking online to see how to diagnose the issue but have not been successful. Has anyone else been having the same problem? Is Microsoft aware of this? Any plans to fix or diagnose it?...
  3. BSODs daily since installation of Win10

    in Windows 10 BSOD Crashes and Debugging
    BSODs daily since installation of Win10: Ever since I installed Windows 10, in a newly built computer, I have been getting the same 5 or 6 BSoDs and crashes every time I start my machine. It starts with Kernel_Security_Failure, then Page_Fault, then something else, then something else. I've been dealing with this...
  4. The bugcheck was: 0x000000ea (0xffff9e8bc25ae700, 0x0000000000000000). A dump was saved in:...

    in Windows 10 BSOD Crashes and Debugging
    The bugcheck was: 0x000000ea (0xffff9e8bc25ae700, 0x0000000000000000). A dump was saved in:...: Good Morning everybody, My DESKTOP PC Intel Celeron CPU G93930, 8 GB ram , AMD Radeon graphic card, suddenly stop responding for a few seconds then suddenly restarted. and on a daily (or even more often) basis when i checked the dump files , the error appears...
  5. Low gaming fps since Fall Creators update.

    in Windows 10 Gaming
    Low gaming fps since Fall Creators update.: what do you use to stream? shadowplay? if so.. turn it off and see how your game runs.
  6. AutoComplete not working in Edge Since Fall Creators Update?

    in Browsers and Email
    AutoComplete not working in Edge Since Fall Creators Update?: Hello, I remember before the Fall Creators Update, Edge would autofill certain pages addresses that I visited before when I start typing a word of the subject that the page is discussing (thus not necessarily the address itself). This does not seem to work anymore...
  7. BSOD Usually While Idle (variety of BugChecks)

    in Windows 10 BSOD Crashes and Debugging
    BSOD Usually While Idle (variety of BugChecks): General Info About The Issue: -My system usually crashes while 1)idle or 2) under light usage (like web-browsing, etc.) -It does not crash while gaming which is my primary use for the machine. -There are a variety of Bugchecks (see attached) -I can't seem to put my...
  8. BSOD 'Thread stuck in device driver' error code 0x000000EA

    in Windows 10 BSOD Crashes and Debugging
    BSOD 'Thread stuck in device driver' error code 0x000000EA: My system freezes for a few seconds and then BSOD gets displayed showing 'Thread stuck in device driver'. This happens randomly. I updated the BIOS version but the problem still persists. All the other drivers are updated. I am using AMD E1-6010 APU with AMD Radeon R2...
  9. Multiple daily BSOD since Upgrade to Win10

    in Windows 10 BSOD Crashes and Debugging
    Multiple daily BSOD since Upgrade to Win10: Hi, I am losing my mind and have run out of places to check for help, so hoping someone here can assist: I installed Win 10 on 8/8. Since then receiving the same 2 BSOD multiple times every day, but no indication as to the cause. I have updated every driver I can think...
  10. Daily BSOD in hal.dll with bugcheck code 133 since last windows update

    in Windows 10 BSOD Crashes and Debugging
    Daily BSOD in hal.dll with bugcheck code 133 since last windows update: I need help identifying the driver causing the BSOD in Windows 10.0.14393.206. It seems that every other set of MS updates causes this BSOD after I upgraded to Windows 10 about a year ago. My computer was stable for a few months, then an update would cause random crashes,...

Users found this page by searching for:

  1. the computer has rebooted from a bugcheck. the bugcheck was: 0x000000ea (0xffffc485bff7b0c0 0x0000000000000000 0x0000000000000000 0x0000000000000000). a dump was saved in: c:\windows\memory.dmp. report id: c64cac00-d191-4f02-9994-0c1813786486.

    ,
  2. The bugcheck was: 0x000000ea (0xffff868805d95700 0x0000000000000000 0x0000000000000000 0x0000000000000000).