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

See post #2 steps #8 and #9.
There have been 4 bios updates that were missed.
Please update to the latest bios.
And view all other available drivers so that the computer environment has the latest drivers.

The bios update can be done at any time. The sooner the better.
Where is the link to the memory dump?
Please repost the one drive or drop box share link.

Also remember to reset the bios after the upgrade.

 

Cheers - see below for the memory dump link - i will get the BIOS updated asap and include a reset plus drivers.

OneDrive

 

Bios has now been updated to F8

F9b is available as this is beta it was preferred not to update to this version unless otherwise recommended.

Cheers

I will check other drivers and update

Thanks again

 

Checked the drivers - only driver that is older is the lan driver which i have now updated.

I think that is everything caught up now.

Cheers

 

Nice progress.
So now you can watch and wait to see if there are any more bsod.
If there are more bsod they can be troubleshooted.
Alternatively the hardware can be stress tested.

Use the computer as you usually do an perhaps use the graphics playing games to check the performance.

If the graphics is stressed you would check for temperature changes, freezing, display artifacts, bsod, etc.

 

Cheers will do - strangely enough the computer runs fine when in use.

I have only had the issue when the pc is idle - will watch some tv and leave it on tonight and see how things go.

Once again thanks for your assistance.

 

Well so far i have had no 0xEA bugchecks or crashes.

The only difference i have at present is that the machine goes into sleep mode after 30m instead of the screen just switching off.

I have previously had the machine crash in a short timescale 5-45min so its not unreasonable to assume that it could crash before the machine goes into sleep mode but so far this hasnt happened. I will continue to test as is and then do some further testing by removing sleep mode.

 

Post a new zip and I'll check the logs to see if there were any problems reported related to fast startup, hibernation, or sleep.

BSOD - Posting Instructions - Windows 10 Forums

 

Literally couldnt make it up - saw your post via email on my phone - came down to post the zip and the machine was sitting with power but no display. Had to force a reboot and checked the logs on logon and have a 0xEA error...

I've re-ran dm_log collected and attached the latest zip

Cheers again

Unfortunately there is no visible BSOD as the display is off.

Edit ive also disconnected the HDMI cable to my TV so the system is only running on a single screen

 

There was 1 BSOD mini dump today.
Debugging this BSOD displayed misbehaving graphic card drivers:
atikmdag.sys
atikmpag.sys

Perform the following steps:
1) Uninstall everything AMD using Display driver uninstaller and install new drivers from the AMD website.
2) 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
3) It may be possible to look for an older driver to see if there is computer stability or instability.
4) If there are recurrent BSOD related to the graphics card plan to remove the card and use only the Intel graphics.
5) And at the same time look for a friend, neighbor, relative, local store to swap the video card. Then evaluate the computer's card in the the new computer and evaluate another video card in this computer.



Code: 05/11/2017 19:27 Windows Error Reporting 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: 08/11/2017 23:04 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 100000ea P2: ffffd80d05a10080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\110817-8375-01.dmp \\?\C:\Windows\TEMP\WER-13234-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3EFD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F0C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F2C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_a08b9b64fc9d98c531f62628b9c64a828c19dce_00000000_cab_02e83f2b Analysis symbol: Rechecking for solution: 0 Report ID: b0a9731c-0c6a-481b-885b-0168cefe9664 Report Status: 4 Hashed bucket:[/quote] Code: 08/11/2017 23:05 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 67a630d5-376b-409d-b9bb-5da85f5d421a Problem signature: P1: 100000ea P2: ffffd80d05a10080 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\110817-8375-01.dmp \\?\C:\Windows\TEMP\WER-13234-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3EFD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F0C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F2C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_a08b9b64fc9d98c531f62628b9c64a828c19dce_00000000_cab_126487ae Analysis symbol: Rechecking for solution: 0 Report ID: b0a9731c-0c6a-481b-885b-0168cefe9664 Report Status: 268435456 Hashed bucket: 05/11/2017 19:27 Windows Error Reporting 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:[/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\c0316467.inf_amd64_3d8fbd78102e53d7\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0316467.inf_amd64_3d8fbd78102e53d7\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0316467.inf_amd64_3d8fbd78102e53d7\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0316467.inf_amd64_3d8fbd78102e53d7\amdxc64.dll Driver Version 22.19.662.4 INF File oem6.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-0xF07FFFFF Memory Address 0xF0000000-0xF07FFFFF I/O Port 0x0000E000-0x0000EFFF Memory Address 0xF7D00000-0xF7DFFFFF IRQ Channel IRQ 4294967293 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\c0316467.inf_amd64_3d8fbd78102e53d7\atikmpag.sys (22.19.662.4, 536.91 KB (549,800 bytes), 26/07/2017 23:05)[/quote]

 

Yeah that is the one that just happened in between my initial no problems so far post about 1 hour ago and looking to reply to your request to post a new zip file

 

Zbook - thanks again for the assistance.

I have once again installed the latest driver as per the instructions.

Unfortunately at present i do not have access to a spare video card to test the issue.

If the problem persists with more frequent BSOD i will go down the route of testing with the intel graphics.

Hopefully this is just a new driver related issue which has yet to be resolved.

Looking back through AMD and other forums this issue previously existed with another round of Windows & AMD Driver updates.

 

The current driver is 22.19.662.4
If there are no further BSOD you are set.
If there are further BSOD then for trial and error look for an older driver:
Previous


Ensure the GPU is free from dust build up and that the fan is working correctly.Reseat the GPU and check all connections are securely made.

In the BIOS check the PSU voltages: what are each 3.3v, 5v, and 12v values?
What are the CPU voltage and frequency?

 

Status update.

About to give the system the kiss of death with a report of no further BSOD - and i hasten to add YET.

System is currently set to sleep after 15m which is cutting down the previous screen time off to sleep by half.

Obviously my current usage with bringing in sleep is changing how i used the pc and tbh it makes more sense to use it this way i dont need it running in the background burning electricity doing nothing just now.

I've also disconnected the hdmi and will only connect when in use as access is quite easy.

I have previously had a BSOD with the current setup so i dont think the issue is cured yet but the pc isnt staying on long enough with the screen off for the problem to show.

Due to current time restrictions I am going to wait for new drivers and see if anyone else is reporting the issue elsewhere before retesting everything again under the previous conditions or if there is nothing out within a reasonable timescale i am going to do some further tests under previous test conditions to ensure the BSOD issue still exists.

If it still exists i will roll back to a older driver - there is some reference to a 2016 driver being more stable with the current windows release for other issues so will roll back to that.

GPU has been thoroughly cleaned and re-seated, fan is running ok too.

Will check psu voltages and report back.

My gut feeling is that this is a issue with the driver and 1709 but time will tell.

Once again thanks for all your assistance.

 

Oh well got back from my run only to find my pc wouldnt wake up from sleep.

Powered on and 0xEA...

At least i have ruled out the hdmi being plugged in - going to roll back to an old driver that has been recommended elsewhere and see how things go.