PC BSOD while gaming

[ModernDarpa]

Been gaming on my PC for about 2 months after upgrading to Windows 10. It started a week ago and only happened on Shadow of Mordor. Needless to say that it started happening on other games such as Fallout 4 and even smaller games like CS:GO and TF2.


I've tried updating my mobo drivers and same for my gpu. And it still crashes. I've consulted Ten Forums and they said that it could be my hard drive, so I ran SeaTools for windows10 and the hard drive passed.

My PC parts are:

AMD10-5800k
XFX Radeon R9 380 black edition
ASRock FM2A68M-HD+ MicroATX
Mushkin ECO2 8gb (4x2)
Seagate Barracuda 1TB
Cooler Master Elite V2 550w


I have a .zip file that I posted on TenForums that contains some info that could be useful.
https://drive.google.com/open?id=0Bx6m-emhMWA8b0JybUIyMkFrdHc

Any ideas and or suggestions?

 

[johnbl]

since the component that called the bugcheck is often a target of malware attacks I would also
start cmd.exe as an admin and run

sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth

as well as updating the drivers below and the bios version
i don' think it will be your hard drive, simply because the data corruption looks wrong.
The error code looked like a process handle. Something you would see if a driver or malware overwrote memory.
--------------
most current bugcheck was caused because something corrupted the data for a critical windows process.
the status code was bogus, it looks like something running as a service corrupted memory that was being used by csrss.exe

i would suspect your MAD CATZ INC drivers but I have no proof. (mainly because USB drivers get messed up so easily)

to prove it you would run verifier.exe and change the memory dump type to kernel.
kernel dumps will have the USB info saved and the correct internal logs saved in the memory dump.


to run veifier.exe start cmd.exe as an admin (windows key +x, then type A)
run
verifier.exe /all /standard

reboot your system. verifier will attempt to check your device drivers for common bugs and will bugcheck the system if it finds any problem.
The memory dump will name the driver.

Note: turn off verifier.exe when done testing. ie run:
verifier.exe /reset

know how to get into safe mode, so you can turn off verifier if it bugchecks during boot.
here is info on how to change the memory dump type:
https://community.sophos.com/kb/en-US/111474

a kernel memory dump will include internal error logs, and info on all running device drivers.
a minidump only shows the stack trace of the process that was running during the bugcheck.

some problem going on with your network driver
rt640x64.sys Thu Jul 23 01:53:50 2015
: Realtek NICDRV 8169 PCIe GBE Family Controller driver
I would update it:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

looks like your motherboard sound driver should also be updated.

i would update the lan and audio driver and the bios from the motherboard website:
http://www.asrock.com/mb/AMD/FM2A68M-HD+/?cat=Download&os=Win1064


machine info:
BIOS Version P1.60
BIOS Starting Address Segment f000
BIOS Release Date 05/05/2015
Manufacturer ASRock
Product FM2A68M-HD+
Processor Version AMD A10-5800K APU with Radeon(tm) HD Graphics
Processor Voltage 8dh - 1.3V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3800MHz

 

[ModernDarpa]

After the boot, it gave me multiple bsods in a row with the error code of "driver verifier iomanager violation". After accessing into safemode, i did the verifier,exe/reset command.

So how do I find the kernel dump?

 

[johnbl]

if verifier finds any problem it will immediately bugcheck the system with the error you got and will save a memory dump.

you have to boot into safe mode (F8 or shift+f8) and run
verifier.exe /reset

this will turn off verifier and allow the system to boot.
then you can get the last memory dump, copy it to a server like microsoft onedrive, share it, and post a link.

mini dumps are stored in c:\windows\minidump directory
kernel dumps are stored in c:\windows\memory.dmp file

you will need to copy the files up to a server like google docs, media fire, or microsoft onedrive,
then share them as public and post a link.

I tried using the verifier command in admin mode and after reboot, I got a BSOD saying driver "verifier iomanager violation" twice in a row. Then Automatic repair came in. It's taking a while, so I'll keep you updated.

After about 2 more bsods of the same error, I was able to access the troubleshoot. What now after this?

 

[ModernDarpa]

if verifier finds any problem it will immediately bugcheck the system with the error you got and will save a memory dump.

you have to boot into safe mode (F8 or shift+f8) and run
verifier.exe /reset

this will turn off verifier and allow the system to boot.
then you can get the last memory dump, copy it to a server like microsoft onedrive, share it, and post a link.

mini dumps are stored in c:\windows\minidump directory
kernel dumps are stored in c:\windows\memory.dmp file

I tried using the verifier command in admin mode and after reboot, I got a BSOD saying driver "verifier iomanager violation" twice in a row. Then Automatic repair came in. It's taking a while, so I'll keep you updated.

After about 2 more bsods of the same error, I was able to access the troubleshoot. What now after this?

Okay, doing it right now

 

[ModernDarpa]

https://drive.google.com/open?id=0Bx6m-emhMWA8anJob3ZZYVpNYjA

Here's the .dmp file

 

[johnbl]

overall I would suspect it is a bug in the saitek (software)
--------
this could also be a bug in the USB drivers or the BIOS of the machine.
there is a new BIOS update for the motherboard:
http://www.asrock.com/mb/AMD/FM2A68M-HD+/?cat=Download&os=BIOS

you might try updating the amd all and one driver but I am not sure it will help (just based on the file dates)
http://www.asrock.com/mb/AMD/FM2A68M-HD+/?cat=Download&os=Win1064

------------
I would be looking for a update from saitek:
http://www.saitek.com/uk/down/drivers.php

or maybe uninstall the saitek software drivers and try a new keyboard and mouse

bugcheck was in Saitek Magic Mini driver
Image path: \SystemRoot\System32\drivers\SaiMini.sys
Image name: SaiMini.sys
Timestamp: Thu Oct 01 02:24:52 2015

(kind of strange that the copyright is in 2009)

3: kd> lmvm SaiMini
start end module name
fffff800`2eba0000 fffff800`2eba3f00 SaiMini (deferred)
Image path: \SystemRoot\System32\drivers\SaiMini.sys
Image name: SaiMini.sys
Timestamp: Thu Oct 01 02:24:52 2015 (560CFBE4)
CheckSum: 0000CD7D
ImageSize: 00003F00
File version: 7.0.45.2
Product version: 7.0.45.2
File flags: 0 (Mask 17)
File OS: 4 Unknown Win32
File type: 0.0 Unknown
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Saitek
ProductName: Configuration Software
InternalName: SaiMini.sys
OriginalFilename: SaiMini.sys
ProductVersion: 7.0.45.2
FileVersion: 7.0.45.2
FileDescription: Saitek Magic Mini Driver
LegalCopyright: Copyright (C) Saitek plc 2009



it looks like the driver is responding to packets that it does not own.
It is confusing because the system thinks there are no other usb devices on the system. they are initialized but not configured.
the system shows:
SaitekMagicBus\SaitekHotKeys
SaitekMagicBus\SaitekMouse
SaitekMagicBus\SaitekKeyboard



machine info:
BIOS Version P1.60
BIOS Release Date 05/05/2015
Manufacturer ASRock
Product FM2A68M-HD+

 

[ModernDarpa]

I have updated my bios via my UEFI as instructed by ASRock. But after the BIOS update, I still encounter the bsods.

But something did show up that is more interesting.

Whilst steam was updating some games, one by one, they stopped. And then I noticed the cause of it. Disk Write Error.
After looking up, steam suggested that it could be a failing hard drive. Which could make sense, since I've had multiple problems even before this post, and I know it isn't the RAM since I replaced them about a month ago.


But then again, I've scanned the drive with SeaTools for Windows and the drive passes the scan. Which is odd.

Any suggestions at this point?

 

[johnbl]

go into bios and look under the usb menus, try to find something related to usb extensions
( extensible host controller) and change it so it does not load any extensions.

then see if your saitek driver works correctly.

when you bugcheck often data being written to disk will not be completed and it will show up as a disk write error.
(you can not trust the error if it was produced near the time a bugcheck or loss of power)


[

quotemsg=18253595,0,2247198]I have updated my bios via my UEFI as instructed by ASRock. But after the BIOS update, I still encounter the bsods.

But something did show up that is more interesting.

Whilst steam was updating some games, one by one, they stopped. And then I noticed the cause of it. Disk Write Error.
After looking up, steam suggested that it could be a failing hard drive. Which could make sense, since I've had multiple problems even before this post, and I know it isn't the RAM since I replaced them about a month ago.


But then again, I've scanned the drive with SeaTools for Windows and the drive passes the scan. Which is odd.

Any suggestions at this point?
[/quotemsg]

 

[ModernDarpa]

go into bios and look under the usb menus, try to find something related to usb extensions
( extensible host controller) and change it so it does not load any extensions.

then see if your saitek driver works correctly.

when you bugcheck often data being written to disk will not be completed and it will show up as a disk write error.
(you can not trust the error if it was produced near the time a bugcheck or loss of power)

I went into the bios and the closest thing that I could configure on the usb ports are to disable the 3.0 ports. So I did.
I disabled the saitek applications from startup ad turned them off manually.
As well as scanned my drive for errors since windows was suggesting it.

I'm able to update my games, which is good to see. But I have yet to test if it's gonna crash again if I go into chrome or try to play a game.

 

[ModernDarpa]

Okay. So I've tested it for a bit, and I was able to play some easy to run games such as CS:GO.
Although I had a crash when I tried on something a bit more demanding.

I tried compressing the latest .dmp file but it just gives an error of "file not found or read permission"


______

Update: Right after the crash, I received a critical_process_error crash shortly after starting a game.
Though this one scared me a bit more since it closed the game and brought me to the desktop with nothing on it but the Recycle Bin before getting the error message.

 

[johnbl]

you do not have write permissions for the default directory that a memory dump is stored in.
you would have to make a copy to a new location before you could .zip the file.

windows system owns the original copy location of the memory dumps.
these get crashes reported to microsoft as part of the Windows error reporting. Microsoft fixes problems related to their code and will push out fixes. Bugs in oem drivers would be reported to the driver owner, they would make a fix and put it on their website. You would have to figure out the problem and pick up the updated driver, most likely on your motherboard vendors website.

Okay. So I've tested it for a bit, and I was able to play some easy to run games such as CS:GO.
Although I had a crash when I tried on something a bit more demanding.

I tried compressing the latest .dmp file but it just gives an error of "file not found or read permission"


______

Update: Right after the crash, I received a critical_process_error crash shortly after starting a game.
Though this one scared me a bit more since it closed the game and brought me to the desktop with nothing on it but the Recycle Bin before getting the error message.