Dear all,
I'm an avid gamer (as you will see in the attached file). Today my computer crashed with the error CRITICAL SYSTEM CORRUPTION for the, I think, third time now in several months. The other two times were a while ago when running RASnes (SNES emulator) and trying to start foobar (a music player, I assumed then that RASnes does not like the UAC that foobar calls because it needs admin rights and caused the crash), today the both programs ran together for about an hour before the crash. I'm starting to think they somehow caused the crash by somehow hating each other.
Other programs running were Skype, Steam, Firefox, Radeon Settings, possibly Thunderbird and possibly Sandboxie (without any active sandboxes).
I don't have any third party CD/DVD drive emulators installed which are a common cause for the issue, such as Daemon Tools, Alcohol and whatnot. I installed two CD tools recently for testing purposes with Sandboxie but did not permanently save any changes so there should have been nothing installed into the system [if you still find any traces of them, let me know, as they are most likely the culprit then]. (I have my CDs in a proprietary format from a program called "VirtualCD" I got many years ago for free with a magazine, but that can't be read by Windows. I could not convert anything and will have to do at some point with my Windows XP partition. This only for info.)
Apologies for the huge list to go through, but I have a lot of games installed. :-) Maybe you find something that causes the crash, maybe it just was random, but I would like to be sure that experts find nothing. Any ideas would be appreciated.
Many thanks for your time in advance!
(Also, in the hours before the crash both Skype and the AMD drivers did an update. Not sure if it is relevant.)
Your dumpfile isSo the dumpfile is not really helpful.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a01f58cfc6851c, b3b72bdf22473e4d, 6, 18} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
The only outdated driver in the driver module is
yk63x64 Wed Jan 09 16:46:56 2013
Driver Description: NDIS6.30 Miniport Driver for Marvell Yukon Ethernet Controller
Driver Update Site: Marvell - Support - Driver Downloads
There are no windows 10 drivers for your mobo.
See if there are windows 10 drivers.
If not it might be that this device is not compatible with windows 10.
Thanks!
The Ethernet controller seems to work fine, however, as I am connected to the internet through it, and disabling it will disable my internet access as well. Unfortunately there are also seem to be no newer drivers for it.
Bugcheck x 109 are usual causes; device driver, Hardware (Memory in particular)
Memory Test.
Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+" to stress test the RAM.
How to run "Memtest"
MemTest86+ - Test RAM - Windows 10 blog
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool
You can stop the test even if a single error is found during the test. Otherwise continue the test for 8-10 passes and post a screenshot with next reply. 8 passes is the recommended bare minimum but more passes will give better result.
Okay, I will ask someone to bring me an USB stick, but it can take a few days. If any further BSODs occur, I will reply here as well. But usually it happens once in several weeks only.Bugcheck x 109 are usual causes; device driver, Hardware (Memory in particular)
