Code:
BugCheck 101, {41, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
A stop 0x101 is too hard to determine the root cause. And the crash dumps are nicely silent for this particular crash dump, which makes the troubleshooting process even harder.
Let us accept the fact that we will not have the root cause clearly stated. But we have to troubleshoot it.
I will point you to
an old forum post by an old member H2SO4 :
H2SO4 said:
What you're looking for will be in one of the following categories:
a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
Let us try from the beginning, and proceed steadily.
Update the BIOS to Version 1.40 from
ASRock > A55M-HVS ... your present BIOS is 1.20.
If any hardware is overclocked, set them all to stock settings.
Also, we see that the graphics driver is failing there.
Code:
fffff880`0b31e8c8 fffff880`110907a3Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
atikmdag+0x377a3
The graphics is AMD Radeon HD 6530D, integrated processor graphics, Integrated AMD Radeon HD 65XX/64XX graphics in Llano (AMD A6-3500) APU. Try the latest driver there ....
Desktop
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of
Speccy. Alternatively, you can publish a Speccy snapshot too:
Speccy - Publish Snapshot of your System Specs .
Also, Stress test the CPU.
It saves the result as a .txt file in the prime95's folder.
Upload the file for us.
Let us know the results.