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

PSU Voltages, etc thanks again for your assistance

Also installed Radeon 16.2.1 which has been suggested as a driver that resolved some other unrelated issues - thought it was worthwhile in the first instance going quite far back with an older driver and see what happens

 

So things are progressing today but for the worse - i have had my first crash whilst using the computer.

Removed and refitted the GPU one final time ensuring good connection and installed the latest drivers released today.

Apart from rolling back to the version before 1709 and running the system using the mobo gpu im pretty much done and looking at replacing the GPU. Can't really afford it and with the price of video cards just now i know i aint going to get vfm.

Uploaded the latest zip which i doubt will say anything different.

Thanks again for the assistance.

 

When you viewed the older drivers what were the available drivers?

This is the driver that just BSOD: 23.20.788.0
The prior driver that had BSOD was: 22.19.662.4

Older AMD drivers: Previous
atikmpag.sys
atikmdag.sys

1) Turn off Windows updates of non-Microsoft drivers.


Enable or Disable Driver Updates in Windows Update in Windows 10 Windows Update Activation Tutorials


2) Install the older driver again if the driver number was different from 23.20.788.0

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\c0320046.inf_amd64_8e8f6af872d98101\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320046.inf_amd64_8e8f6af872d98101\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320046.inf_amd64_8e8f6af872d98101\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320046.inf_amd64_8e8f6af872d98101\amdxc64.dll Driver Version 23.20.788.0 INF File oem5.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\c0320046.inf_amd64_8e8f6af872d98101\atikmpag.sys (23.20.788.0, 523.88 KB (536,456 bytes), 02/11/2017 19:12)[/quote]

 

I went back to the following drivers which are older than the ones listed.

AMD Radeon Software Crimson Edition 16.2.1


Previously i had tried -

Crimson ReLive Edition 17.9.1 Optional
Crimson-Beta-Fall-Update-Oct16
crimson-relive-17.10.3

Are you recommending to go through the different drivers individually to see if any make a difference from the following page?

Previous


Thanks again for your assistance

 

If you can find a stable driver then you do not need to replace the graphics card.
So turn off Windows updates of non-Microsoft drivers and use trial and error to find a stable driver.

Alternatively if you can find a friend, neighbor, relative, or local computer store to swap graphics cards you will then have information about the status of the card.

The other option is to remove the Nvidia graphics card and just use the Intel graphics.

 

Cheers - i will work my way through the various drivers looking for a stable(hopefully) version.

Additionally when time permits i will remove the AMD gpu and run from the intel to ensure this error doesnt occur with the AMD gpu removed.

I have some friends that get additional hardware now and again so will keep a look out for a spare card.

Thanks again for your assistance.

 

Oh well another 'fix' crossed off the list as a failure.

Got a GPU firmware upgrade from the manufacturer and the system had been pretty stable for a while albeit with sleep after 10m.

Left it running spotify for about 1.5hours for it to crash with the same error - back to trying it without the GPU i guess.

 

Please post an updated zip:
BSOD - Posting Instructions - Windows 10 Forums

 

I will happily post the updated zip but unfortunately one of the bugchecks this time is
1005 - 'Unable to produce a minidump file from the full dump file.'

AMD have released a new video driver version which i have installed after the running the log collector.

Thanks again

Edit next crash(assuming the latest driver hasnt fixed it) i will upload a zip.

Cheers

 

Perform the following steps
1) Open administrative command prompt and type or copy and paste:
powercfg.exe /hibernate off

2) Update all of the chip set drivers

3) Run HDTune:
HD Tune website
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials

4) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 8 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

5) Download and install Whocrashed
Resplendence Software - WhoCrashed, automatic crash dump analyzer
6) Above analyze click on tools > crash dump test > type: ACCEPT
7) click analyze > look for dead or deaddead
8) post a new zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums

AMD graphics drivers used:
23.20.768.9
23.20.788.0

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:14/11/2017 21:51 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 100000ea P2: ffffd207e1f0f040 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\111417-8031-01.dmp \\?\C:\Windows\TEMP\WER-13531-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4853.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4883.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_edc43f36eeb4c123407e269816be94b655a2d_00000000_cab_02ec4882 Analysis symbol: Rechecking for solution: 0 Report ID: 18c5d528-6a47-42c9-ac8f-da8de385f8ec 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:13/11/2017 20:16 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 100000ea P2: ffffdb0155d96700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\111317-7390-01.dmp \\?\C:\Windows\TEMP\WER-11687-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3902.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3903.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3914.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_67fbc52ab162074161d83a163e46fca52356d70_00000000_cab_02e83911 Analysis symbol: Rechecking for solution: 0 Report ID: efcfbfab-31c8-4772-990e-e86744572d19 Report Status: 4 Hashed bucket:12/11/2017 21:31 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 100000ea P2: ffffe5804d954040 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\111217-8359-01.dmp \\?\C:\Windows\TEMP\WER-13062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DF3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E03.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E32.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_f265e5eac5c4729393ea66bbaa90584b1dd97fb2_00000000_cab_02ec3e31 Analysis symbol: Rechecking for solution: 0 Report ID: 08afa054-972a-4a5a-9757-cd08e3738667 Report Status: 4 Hashed bucket:[/quote] Code: 13/11/2017 20:17 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 46f844c3-ec71-453c-8ae8-7f558954f306 Problem signature: P1: 100000ea P2: ffffdb0155d96700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\111317-7390-01.dmp \\?\C:\Windows\TEMP\WER-11687-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3902.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3903.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3914.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_67fbc52ab162074161d83a163e46fca52356d70_00000000_cab_125c7436 Analysis symbol: Rechecking for solution: 0 Report ID: efcfbfab-31c8-4772-990e-e86744572d19 Report Status: 268435456 Hashed bucket:14/11/2017 21:51 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 5458ebfa-1d3a-48c2-99d4-82459a7764ae Problem signature: P1: 100000ea P2: ffffd207e1f0f040 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\111417-8031-01.dmp \\?\C:\Windows\TEMP\WER-13531-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4853.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4883.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_edc43f36eeb4c123407e269816be94b655a2d_00000000_cab_09e0473a Analysis symbol: Rechecking for solution: 0 Report ID: 18c5d528-6a47-42c9-ac8f-da8de385f8ec Report Status: 268435456 Hashed bucket: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:12/11/2017 21:31 Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 79ee18d3-d4d7-427f-ac45-3454ed4857ae Problem signature: P1: 100000ea P2: ffffe5804d954040 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\111217-8359-01.dmp \\?\C:\Windows\TEMP\WER-13062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DF3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E03.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E32.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_f265e5eac5c4729393ea66bbaa90584b1dd97fb2_00000000_cab_12746ca4 Analysis symbol: Rechecking for solution: 0 Report ID: 08afa054-972a-4a5a-9757-cd08e3738667 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: Event[3743]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-11-12T21:31:25.652 Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: BOYD-MAIN Description: Windows failed to resume from hibernate with error status 0xC0000001.[/quote] Code: Event[4398]: Log Name: System Source: volmgr Date: 2017-11-13T02:17:41.981 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: BOYD-MAIN Description: Dump file creation failed due to error during dump creation.[/quote] Code: Name AMD Radeon R7 200 SeriesPNP 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\c0320046.inf_amd64_8e8f6af872d98101\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320046.inf_amd64_8e8f6af872d98101\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320046.inf_amd64_8e8f6af872d98101\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320046.inf_amd64_8e8f6af872d98101\amdxc64.dll Driver Version 23.20.788.0 INF File oem5.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\c0320046.inf_amd64_8e8f6af872d98101\atikmpag.sys (23.20.788.0, 523.88 KB (536,456 bytes), 02/11/2017 19:12)[/quote]

 

I know you said to run the checks above but i have waited until another bugcheck.

Please find attached the logs from log collector.

Please note i have now (after the latest bugcheck) disabled my AMD GPU and am now using the onboard HDMI.

Thanks again

 

The latest bugcheck was consistent with the prior bugchecks and displayed the same misbehaving AMD graphics drivers:
atikmpag.sys
atikmdag.sys

When available please post the progress and results with the steps in post #38

 

So ive been quiet for a bit since i haven't had the same bug check since the 22nd.

I got a different bug check on the 23rd which suggested memory tests which passed and remove and re-seating the ram - i had already carried this out so swapped the ram over so stick 1(previously slot 1) was and slot 3 and stick 2(previously slot 3) was in slot 1 and the computer has behaved itself until now where i have got a different bugcheck - 0x00000019.

I thought i would post this info out of interest to see if it is still pointing to either ram or gpu.

Cheers

 

The windbg indicated corruption with 1 hardware driver:
atikmdag.sys

This is the driver that just BSOD: 23.20.793.0
The prior drivers that had BSOD were: 22.19.662.4; 23.20.788.0

The BAD_POOL_HEADER bug check has a value of 0x00000019. This indicates that a pool header is corrupt.

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\c0320421.inf_amd64_3172c820718ebf21\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320421.inf_amd64_3172c820718ebf21\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320421.inf_amd64_3172c820718ebf21\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\c0320421.inf_amd64_3172c820718ebf21\amdxc64.dll Driver Version 23.20.793.0 INF File oem19.inf (ati2mtag_R505DS section) Colour Planes Not Available Colour Table Entries 4294967296 Resolution 1920 x 1080 x 59 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\c0320421.inf_amd64_3172c820718ebf21\atikmpag.sys (23.20.793.0, 533.02 KB (545,808 bytes), 16/11/2017 20:07)[/quote]

 

Still related to GPU then - cheers