BSoD running Maplestory

[Habbelfisk]

Hello, I'm not sure I'm posting this under the right category but I'll go ahead and describe my issue since I've seen related issues on these forums.

First off I've been talking to both NexonEu support and Microsoft, neither could help me out. I'm hoping someone has any experience. Nexon told me they tried all their solutions and Microsoft had to use advanced troubleshooting tools which I could not pay for, they told me they'd send them over so I could do it myself but they did not.

My issue consists of Blue screens, when running maplestory for a couple of minutes. I've been able to play it earlier on this PC but then I experienced issues with Maplestory shutting down after about an hour but then it was easy enough to simply restart. I wanted to run the game for pure nostalgia but now I'm just determined to fix it since I can't stand the fact of a stone age game crashing my PC.

Drivers are all up to date according to Gigabyte, AMD, Driver Booster and Windows Update.
I've ran WDC diagnostics, full and ALL tests as well as Seatools tests for. (Both HDD's tested with both programs.)
I'm positive the temps are not an issue, I've been monitoring temps on way more demanding games and Cpu stays around 40 while Gpu is around 56. (recently renewed thermal paste as well)
I've been overclocking before but those were disabled and software removed. (AMDOverDrive and MSI Afterburner)
Ram is not yet tested but then I believe BlueScreenView would point me in another direction?
Malware Scans and registry cleans have been ran, Malware scan found a few issues but was resolved. I then re-installed the game with the same results.

- Specs and Dumpfiles
http://

I might have forgot something but I think I got most of it, not sure at all what to do any longer. For the record Maplestory is the only application that has crashed my PC except Exporting in Cinema4D but that gives no Blue Screen nor dumps in neither MEMORY.dmp or Minidump which makes me think it's the program malfunctioning.

 

[johnbl]

third bugcheck 0x101 memory dump corrupted, could not read correctly with debugger.
try and update the BIOS and various usb drivers.
-------------
update BIOS to current version
your version F9 dated 10/13/2011
current version F14e dated 2014/09/09
http://www.gigabyte.com/products/product-page.aspx?pid=3901#bios

update your AMD chipset drivers to get USB 2.x fixes
update Etron USB 3.0 Driver to get USB 3.0 fixes (2014/01/09)
from here:
http://www.gigabyte.com/products/product-page.aspx?pid=3901#driver

this will give your system the best chance to get the dualshock driver to work.
reboot and see if you still bugcheck.
----
remove or update scpvbus.sys
it looks like you have two thread running plug and play. One thread was setting up the driver and the other was waiting on the first thread. the first thread became idle but never released the lock, this prevented the second thread from completing and it retried until a timer went off and the system thought your processor was hung and called a bugcheck 0x101.
12289 attempts to get to use the resource before the system gave up and called a bugcheck.
I assume this is a usb device, you would update the driver but it can also be a bug in the USB support in BIOS or the USB support in your chipset for usb 3.0

 

[Habbelfisk]

third bugcheck 0x101 memory dump corrupted, could not read correctly with debugger.
try and update the BIOS and various usb drivers.
-------------
update BIOS to current version
your version F9 dated 10/13/2011
current version F14e dated 2014/09/09
http://www.gigabyte.com/products/product-page.aspx?pid=3901#bios

update your AMD chipset drivers to get USB 2.x fixes
update Etron USB 3.0 Driver to get USB 3.0 fixes (2014/01/09)
from here:
http://www.gigabyte.com/products/product-page.aspx?pid=3901#driver

this will give your system the best chance to get the dualshock driver to work.
reboot and see if you still bugcheck.
----
remove or update scpvbus.sys
it looks like you have two thread running plug and play. One thread was setting up the driver and the other was waiting on the first thread. the first thread became idle but never released the lock, this prevented the second thread from completing and it retried until a timer went off and the system thought your processor was hung and called a bugcheck 0x101.
12289 attempts to get to use the resource before the system gave up and called a bugcheck.
I assume this is a usb device, you would update the driver but it can also be a bug in the USB support in BIOS or the USB support in your chipset for usb 3.0

So I should flash my BIOS?

Also I'd rather just get rid of that driver. I will update my USB ports but I know what that driver is and will never use it again.

I deleted the scpvbus.sys driver the first time you told me, why is it still causing things if it's the issue? I can not see it in C:\Windows\System32\drivers ...

 

[johnbl]

BIOS versions before early 2013 tend to have issues with their support of USB hardware. Your device drivers have already been updated but to ensure the best chance of working you will want to update the BIOS also.


scpvbus.sys: It depends on how you removed it, if you just removed the device and it is a usb device it does not get removed only hidden in device manager. If you removed the driver and left the device plugged in, then plug and play will attempt to install it again. I think this was the case when I looked at your memory dump the other day if I recall correctly.

if you just deleted the driver from your system, the system may have a hidden copy in a hidden directory called a driverstore. When the system detects the driver is missing, it will replace if from the hidden copy in the driverstore. You have to remove that copy also. here is info on how to remove: https://technet.microsoft.com/en-us/library/cc730875.aspx

You may want make windows device manager show hidden devices:
You can google for info or here is a link:http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html

You can also remove the .inf file for the device to prevent it from being reinstalled.
start cmd.exe as an admin, then run
pnputil.exe /e
this will list all of the oem.inf files, look through the list and find the one pertaining to the device and then get the file name and run the commnad.
pnputil.exe -f -d oemxxx.inf
this will force the deletion of the named oemfile.inf

third bugcheck 0x101 memory dump corrupted, could not read correctly with debugger.
try and update the BIOS and various usb drivers.
-------------
update BIOS to current version
your version F9 dated 10/13/2011
current version F14e dated 2014/09/09
http://www.gigabyte.com/products/product-page.aspx?pid=3901#bios

update your AMD chipset drivers to get USB 2.x fixes
update Etron USB 3.0 Driver to get USB 3.0 fixes (2014/01/09)
from here:
http://www.gigabyte.com/products/product-page.aspx?pid=3901#driver

this will give your system the best chance to get the dualshock driver to work.
reboot and see if you still bugcheck.
----
remove or update scpvbus.sys
it looks like you have two thread running plug and play. One thread was setting up the driver and the other was waiting on the first thread. the first thread became idle but never released the lock, this prevented the second thread from completing and it retried until a timer went off and the system thought your processor was hung and called a bugcheck 0x101.
12289 attempts to get to use the resource before the system gave up and called a bugcheck.
I assume this is a usb device, you would update the driver but it can also be a bug in the USB support in BIOS or the USB support in your chipset for usb 3.0

So I should flash my BIOS?

Also I'd rather just get rid of that driver. I will update my USB ports but I know what that driver is and will never use it again.

I deleted the scpvbus.sys driver the first time you told me, why is it still causing things if it's the issue? I can not see it in C:\Windows\System32\drivers ...

 

[Habbelfisk]

I'm pretty sure I got rid of it now,
also deleted 2x AODDriver drivers which is for Amd OverDrive, I'm aware of AOD drivers that have been causing issues for others.

I've been going to C:/windows/system32/drivers and deleting the drivers from there earlier. Now I found AOD drivers, Apple charging drivers and the Scarlett Productions V bus driver in Device Manager and uninstalled all, made sure they're gone in C:/windows/system32/drivers as well.

"If you removed the driver and left the device plugged in, then plug and play will attempt to install it again. I think this was the case when I looked at your memory dump the other day if I recall correctly."

*Got a comment on that, as far as I know the SCP driver origins from the site you posted earlier which I used for being able to use my PS3 Dual Shock controller on PC. So the scpvbus driver is no official driver at all as far as I recall it, the interface of required programs and such seemed really homemade.
However, I've not had my PS3 controller plugged into my PC for a really long time, and I uninstalled all the software which enabled me to use it. I'm guessing it just left the drivers.

It seems gone now however, and I never liked it... It seemed so sketchy using that software to enable me to use my controller, it worked by simulating an Xbox controller. (fyi) 😉

I flashed my BIOS to f14e, updated chipset and Etron 3.0.

Will try running the game now, also updated my DxDiag if you're interested.

*Update, found the .inf files in cmd by doing as you said, got rid of:
1. motioninjoy driver (used for PS3 controller software)
2. scarlett productions driver (also used for PS3 controller software)

 

[Habbelfisk]

I believe this solved it, I've ran the game for a good while and I can only see one PlugPlay service running in my Activity Manager.
I'll notice soon enough if it's not working, but no crash today.