BSoD running Maplestory

Habbelfisk · Apr 25, 2015

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 · Apr 26, 2015

note: if this happens while running a browser based game, try and turn off 3d graphics acceleration in the browser.
if the game runs then your GPU is not getting proper power. (or is not getting cooled correctly, make sure the fan is spinning)

notes: all the bugchecks show the same cause. 8 to 11 seconds during the boot process the CPU detects bad a internal error from its memory controller and shuts the system down.

your system most likely rebooted because of a power fluctuation to the CPU, the power dropped too low and the CPU reset,
Your Power supply/motherboard combination did not check the power quality (or the PSU lied and said the power was good) and the CPU restarted before the power level was stable. This resulted in the CPU getting a error in its cache memory controller and this was reported to the CPU and the CPU shutdown with a bugcheck 0x124 (total uptime of 8 seconds)

Look for a power supply that is under powered, overheating, look for overclocked GPU or CPU. Look for GPU that does not set proper power on its supplemental power connections from the PSU directly to the GPU. Look for bad connections on these same cables, Make sure the GPU is not overheating, blow out any dust. Increase the GPU fan speed. Blow out dust from the PSU and check the fan in the PSU.

first bugcheck was bugcheck 0x124
called by the CPU becausae of internal error on the CPU bus
Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 0)
your system up time is 8 seconds

note: I can not check much of the memory dump because the CPU was doing a panic shutdown of the system because of the power problem.

Habbelfisk · Apr 27, 2015

johnbl :

Thanks for the reply, I'm curious to know what you mean system up time is 8 seconds since my PC often have been on for several hours before I try running the game, which is when it would crash. And why would it happen ONLY when running Maplestory if the power is the issue? And could it be related to having 2 monitors, 1 PC and 1 speaker to all to 1 power outlet if power is the problem? I'm positive the GPU is not overheating since I've been monitoring temps on many more demanding applications, BF4 for instance. My videocard can handle high temps around 100*C, so being around 58 shouldn't be an issue.

It would make sense if the outlet is the issue, since in my last house when I could run Maplestory I only had 2 monitors and drawing less power through the outlet. The issue has only occurred in my current apartment. Adding to this, I usually have my phone charger connected to the same outlet which if I remember correctly I've had every time except the last try to run Maple. I was 2 minutes into the game expecting a crash but didn't get one, the thought hit me to put my phone on charge but I decided not to because maybe that could be the reason. However, with my phone on charge I could run the game for 2-5 minutes but I could do about 30 minutes last time I tried, not sure if that's because I didn't have my phone on charge but worth saying. I still can't make sense of Maplestory being the only application to crash my PC tho.
Thanks

johnbl · Apr 27, 2015

nope, you were running the game, you had a power failure to the CPU and the CPU reset and your power supply did not put out a signal to prevent the CPU from restarting before the power was again stable. (common problem for cheaper power supplies) your CPU restarted on unstable power, the CPU memory controller detected internal cache memory errors and told the CPU, the CPU told windows to shutdown. The whole process took 8 seconds after the reset.

from your perspective you were playing a game, got a black screen for a second or two then a bluescreen.
(black screen was the BIOS starting a reboot sequence) if you had a better power supply most likely you would get the reboot and a black screen. (no bluescreen)

Habbelfisk · Apr 27, 2015

Yes that itself makes sense, so the outlet has nothing to do with that? The scenario you explain makes sense and fits with the past check-ups I did as well, what I don't get is why it only happens when I'm playing Maplestory. But most importantly what can I do? I'll have a look at my Psu and cables when I shut down but I doubt things are sitting loose.

And looking at the power outlet idea as I said earlier, are you sure it can't be the issue? As far as I know that could be the reason, if my other hardwares (monitors, speakers, chargers etc) are also connected then they will be splitting the power from the outlet. For instance, you connect 2x phone chargers to the same and they will charge slower than they would do if they were connected alone? If I'm not completely off that would make my PC crash when the PSU can't keep up with demanding apps since it's also splitting? Sorry for drawing out so much but that would make sense as far as I know, I'll check it up myself.

So what can I do if it's not the outlet, but the PSU/connection/cpu/motherboard?
Thanks alot for helping

johnbl · Apr 27, 2015

do you have 2 video cards in this system?

a amd 6800 series card: 75 watts from pci/e bus
75 watts from the first 6 pin connector
75 watts from the second 6 pin connector

I would confirm that both the first and second 6pin connector are providing power and are not on the same rail of the power supply. (not a issue if you have a power supply with a single rail design)

any overheating of a GPU causes the power requirements to increase, and the extra power causes the GPU to heat up more (kind of feeds on itself) You increase the GPU fans to max and you get extra time before your system resets.

if either of the 6 pin connectors are not providing proper power, the gpu will attempt to pull too much power from the motherboard PCI/e slot, A good motherboard will shutdown, a crappy one just catches on fire and melts the bus.
your motherboard might be reseting the CPU as a protection mechanism. The PSU it self should also try to protect your system with a power_ok signal but cheap power supplies just skip the circuit and hard wire the logic to true.

for a 6800 card you would want a 500 watt psu and then you would also have to add extra depending on the rating of the power supply and what other components you have (CPU, spinning drives,...)

Also, any overclocking of the graphics will make the power useage increase significantly. (even factory overclocks)

if you have two 6800 cards your min power supply is 600watts.

Habbelfisk :

Habbelfisk · Apr 28, 2015

johnbl :

I only have one 6870 which is running at 900mhz core and 1090 memory with overclocking turned off. Also my PSU is 550W and the only upgrades I did to this PC was adding an HDD, a case fan and a CPU fan but that seemed to be no problem for my PSU, and also that was quite some time ago. I cleaned my case after my last post and opened up my PSU to clean it up aswell. All went well, I unplugged RAMs, PSU and Video Card just to make sure there was no dust or w/e blocking ports etc. My Video card is running alot more silent but it didn't fix the problem. I tried booting my PC with only one RAM stick after I cleaned it, I ran it with Stick 2 in slot 4 where it's always been and got a crash just as usual, decided to test my other stick in an unused port. Stick 1 in Port 3 and was able to run Maplestory for more than an hour before I had to leave, so no crash.

It makes sense if Stick 2 / port 4 is corrupt or broken in some way since I never got Memtest86+ to run. So far so good, I'll probably buy another stick if this proves to not crash my PC. I'll try playing this afternoon and hope for no crash.

Habbelfisk · Apr 28, 2015

It was not the solution, I crashed loading up the game. However I did end up getting a dump in MEMORY.DMP instead of Minidump.

"On Tue 2015-04-28 14:44:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88002D64180)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002D64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT"

johnbl · Apr 28, 2015

generally external RAM will not cause a bugcheck 0x124
the only exception I can think of to the rule would be older processors that has external memory controllers that directly connect to the CPU. The external memory controllers would overheat and the CPU would get the error and shutdown.

That should not apply to your system. AMD fx-4170 came out in 2012.

certain malware/viruses/rootkits can cause driver corruption and bugcheck 0x124
but you don't get a reboot and a error on your internal CPU bus that you are getting.
BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 0)
Error Type : BUS error

you do have a CPU that takes a lot of power 125W
and a GPU that takes a lot of power (recommends 500W)

you have a PSU rated at 550 Watts but it also depends on the efficiency rating of the device as to how much power is available and the design determines which leads get the power.
for example: 550 watts at 90% efficiency = 495 watts available
80% efficiency = 440 watts
unrated supplies might have a 65% efficiency.

Oh, I have seen people that did have power strips that would cause problems so if you have problems make sure your main power is plugged into a wall outlet. You might even check the voltage of the wall outlet to make sure it is as expected.

you might also monitor your temps while you run the game, just to see if they are getting too high.

Habbelfisk · Apr 29, 2015

johnbl :

Oh alright, yeah I'll put my PC directly to an outlet and the monitors to another using the strip, will also monitor temps playing a few different games. I've checked temps during Maplestory already and those are really low and is the only game which causes crashes so I'd doubt temps are the issue, I'll doublecheck however. I might have to look into a new PSU if nothing else works...

However as of what I understand, whatever the issue is, it's causing a cache error when playing Maple and causing my pc to shut down? I did read about alot of people with blue screens with different solutions, they all had the same issue in common though. The only game that could crash their PCs no matter how beefy was Maple. It's an outdated game, so drivers was the first thing that came to my mind but they're all updated. Could I have some old drivers lurking in my HDDs I need to get rid off? Just considering possibilities, don't know alot about software causing hardware errors.

johnbl · Apr 29, 2015

Just to be clear, your bugcheck 0x124 was not directly caused by your Game.
At the time of the bugcheck the game was not running. Remember your system was only booted 8 seconds.
The most direct cause of your bugcheck 0x124 was the power supply or motherboard not preventing the CPU starting up while the power was unstable. Your main problem was why the power to the CPU dropped low enough to trigger the reset.

You could get a 500 watt power supply that correctly implements the power_ok signal and you would not get a blue screen (bugcheck 0x124) but your system would still reboot because of the power fluctuation in to the CPU.
You would most likely just get a black screen with no errors.

It would be better to get a PSU that has some excess power, or a newer GPU that uses lower power than the one you have. AMD CPUs and AMD graphics cards use more power than their direct competitors. (intel CPUs and nvidia GPUs) I tended to go with a excessive power supply when I had AMD GPUs. Also, not all power supplies are the same, the cheaper ones use multi rails for example 3 leads that can allow 20 amps each. If one lead needs 22 amps for a spike it can not get it. single rail designs of PSU are much more forgiving. (oh, make sure your supplemental power connectors are not hooked into the same rail on the powersupply, and make sure the connections are good)

Habbelfisk :

Habbelfisk · Apr 29, 2015

"your bugcheck 0x124 was not directly caused by your Game.
At the time of the bugcheck the game was not running. Remember your system was only booted 8 seconds."

This is what I don't understand though.. Since I've never gotten a crash during boot or as you say, with only 8 seconds uptime. I'm positive my PC crashes or blue screens whenever I'm running the game. I guarantee this occurs whenever I run the game and not randomly. I'll record a crash and put up a video if you want.

You might be reading a crash where I first: Ran the game and crashed, 2nd: The pc automatically rebooted but I shut it off manually cause I had to leave (somewhat surrounding 8 seconds after start of reboot.)

Recently I've only been getting these, might be leading more in the right direction?
(posted this earlier)
"On Tue 2015-04-28 14:44:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88002D64180)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002D64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT"

Thankful for your time

johnbl · Apr 29, 2015

note: all of the crashes were during boot, you just did not know that the voltage to your CPU reset pin dropped to a logic zero for long enough to reset the CPU. The motherboard may have detected too much power being used by the GPU bus and reset the CPU. The better ones will do that. The crappy ones will just let your graphics card and PCI/e slot catch on fire. Even a good power supply when overloaded will tell the motherboard and reset the CPU as an attempt to fix the problem before it catches on fire.

CLOCK_WATCHDOG_TIMEOUT
can be a processor not responding like a GPU, it can also be a USB device failing to load via plug and play where plug and play just keeps trying to load the driver over and over and the system thinks one if its core is hung and causes a bugcheck. (common with certain USB wireless ethernet drivers) You have to have a kernel memory dump to figure out these problems.

You can also get this problem with some bugs in device drivers, for those you also need a kernel memory dump and to have run cmd.exe as an admin then
verifier.exe /standard /all
it will do extra error checking and tracking to help catch common driver problems. If it finds a problem it will bugcheck the system so the memory dump can be looked at.
use verifier.exe /reset to turn off the extra tracking.

Habbelfisk :

Habbelfisk · Apr 29, 2015

johnbl :

I understand what you're saying but I can't agree with all the crashes occurring during system boot. I've never had issues with crashes till I decided to try out this game again which is what I'm looking for a solution to. I'll take your advices and keep trying them but I can't relate to whatever the dumpfiles say is happening about 8 second uptime since every crash I have is in Maple or C4D.

I'll try out the advices you listed, how can I determine which USB connection could be the reason? How do I get kernel dumps and have a look at them?
BlueScreenView told me my earlier minidumps were "Caused by driver: ntoskrnl.exe"when running maple.

Nexon support told me I had to take a look at my HDD which I did, they also told me it could be driver related. Then they didn't have any further advice.
Microsoft support told me it was likely to be driver related as well but could not troubleshoot it for me, I'd have to do it myself but didn't get my hands on the files.

johnbl · Apr 29, 2015

if you have C:\Windows\memory.dmp put it on a server and post a link. only saw the minidumps you posted.
-------
The debugger really does not care what anyone says, it just shows what is going on and why the system was shut down.
It can have mistakes but not at this basic level. All of your bugchecks that I looked at show a system that is in the process of being rebooted, and shut down because the CPU told it to shutdown. I can see the various timers, I can see the partial loading of drivers, I can see the error that the CPU is reporting and dump the info. This information just would not be in the memory dumps if it was not the state your machine was in. Even if the system uptimer was incorrect, all of the supporting debug info would also have to be incorrect. Just highly unlikely to be true.

here is a link on how to change the memory dump type using a UI:
http://www.mcci.com/mcci-v5/support/howtos2.html
(reboot after you make the change, and make sure you have space for the larger file on your drive)

I would also run cmd.exe as an admin and run
verifier.exe /standard /all
to turn on extra driver checking and force a memory dump if driver errors are found.
Note: it bugcheck on the first error found, not alway the problem you are looking for.
use
verifier.exe /reset
to turn of the extra driver checking after you bugcheck or your system will run slowly until you do.

Habbelfisk :

Habbelfisk · Apr 30, 2015

johnbl :

if you have C:\Windows\memory.dmp put it on a server and post a link. only saw the minidumps you posted.
-------
The debugger really does not care what anyone says, it just shows what is going on and why the system was shut down.
It can have mistakes but not at this basic level. All of your bugchecks that I looked at show a system that is in the process of being rebooted, and shut down because the CPU told it to shutdown. I can see the various timers, I can see the partial loading of drivers, I can see the error that the CPU is reporting and dump the info. This information just would not be in the memory dumps if it was not the state your machine was in. Even if the system uptimer was incorrect, all of the supporting debug info would also have to be incorrect. Just highly unlikely to be true.

here is a link on how to change the memory dump type using a UI:
http://www.mcci.com/mcci-v5/support/howtos2.html
(reboot after you make the change, and make sure you have space for the larger file on your drive)

I would also run cmd.exe as an admin and run
verifier.exe /standard /all
to turn on extra driver checking and force a memory dump if driver errors are found.
Note: it bugcheck on the first error found, not alway the problem you are looking for.
use
verifier.exe /reset
to turn of the extra driver checking after you bugcheck or your system will run slowly until you do.

Habbelfisk :

Alright, I'm guessing those are some secondary crash then which I'm not noticing? Perhaps a reboot shortly after the reboot sequence is starting after the crash as I recognize it? However, the MEMORY dump is the same one that I posted 2 times now.
I'll put the file up on my Dropbox, link is in my first post on this thread. (when I figure out how to allow windows to upload the file.)

Habbelfisk · Apr 30, 2015

"I would also run cmd.exe as an admin and run
verifier.exe /standard /all
to turn on extra driver checking and force a memory dump if driver errors are found.
Note: it bugcheck on the first error found, not alway the problem you are looking for.
use
verifier.exe /reset
to turn of the extra driver checking after you bugcheck or your system will run slowly until you do."

This had some effects, I'm running my PC through "run Windows with last working settings" (or something like that, can't remember exact text).

I get Blue Screens every time I boot my PC normally now, I have go into advanced startup and then run it in either safe mode or as I stated above. So yes, I do have a driver issue, which one I don't know, whether Microsoft and Nexon could see that I don't know either, if it's the reason for my game crash I don't know either but there is a faulty driver. Most likely all above are true, meaning this driver doesn't interfere or cause crashes in other games or applications.

This would seem correct since the x101 states: Is most likely caused by a driver issue. And I've only been getting x101's in my Memory.dmp.
Also, as of what I know, and x124 can also occurr when drivers are faulty but causing hardware errors.

Any advice on how I can get a safe boot?

"verifier.exe /reset" doesn't work in this mode because it backtracks settings as of where my PC last ran fine and therefore "verifier.exe /standard /all" is not applied (even though in real time it is)

*Notice* I whipped out my camera fast enough to capture the BS and updated my Dropbox with the Blue Screen.
Also how can I get my Memory.dmp file shared? It won't allow me to upload it anywhere, I checked admin settings and such but can't find anything.

Positive if I can sort this driver out I'll be fine, maybe the x101 is causing the ntoskrnl.exe driver crash and therefore an x124 in the minidumps?

johnbl · Apr 30, 2015

the driver listed in the photo is
Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
from http://forums.pcsx2.net/Thread-XInput-Wrapper-for-DS3-and-Play-com-USB-Dual-DS2-Controller?pid=186161#pid186161

the time code of 5186cfae = Time: Sun May 05 14:31:26 2013

normally you hit f8 or shift+f8 to get to safe mode, then you should be able to clear the verifier.exe flags with
verifier.exe /reset

or go delete the driver and try to boot with versifier on again.

it looks like a driver that talks to a running service that is started on your machine, you could also stop the service.
the driver ils listed as a "wrapper for ds3 and play.com usb dual ds2 controller"

the one that is listed at the latest version had a file date of 5-19-2013

Habbelfisk · Apr 30, 2015

johnbl :

I deleted the driver, went into safe mode and reset it and can now normally boot up again.
I do remember downloading those drivers though they never seemed to work, I did uninstall the program itself but the drivers seemed to be stuck there.

I tried running the game, crashed again without blue screens. Have not been getting any BS's lately from crashing the game itself.

Still haven't figured out how to share my MEMORY.dmp files.

Any chance I might get lucky by trying driversweeper or some other similar program?

*Updated Dropbox once again*, one is a minidump of the latest attempt of running the game. It shows the same as the other minidumps so not sure if that will be any help. The other is a LiveKernelReport\Watchdog dump if that is any help.

For the record, I changed my PC to be alone connected directly to an outlet and the monitors etc to another via power strip, they could be paired still but in case they would not be.

johnbl · May 2, 2015

the new bugcheck was bughcek 0x117 VIDEO_TDR_TIMEOUT_DETECTED
basically the graphics adapter/hardware failed to respond and directx called a bugcheck because of it.

it is a minidump, and verifier is not on. this can not be debugged with a minidump.

suspect drivers list:
update or remove this USB apple device charger driver (memory corruption)
AppleCharger.sys Mon Jan 10 01:57:29 2011

BitDefender AntiVirus FS filter driver
bdfsfltr.sys Wed Mar 23 06:52:33 2011 (too old, remove)

update your razer drivers (memory corruption problems)
rzdaendpt.sys Tue Nov 06 23:49:58 2012
rzudd.sys Tue Nov 06 23:49:47 2012
rzvkeyboard.sys Tue Nov 06 23:49:55 2012

PowerISO Virtual Drive driver (update)
SCDEmu.SYS Sun Dec 09 00:46:41 2012

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver (I think this failed verifier, or was it updated?)
ScpVBus.sys Sun May 05 14:31:26 2013

SmartDefragDriver.sys Mon Dec 23 02:05:52 2013 (just not a good idea to replace the OS defrag with a 3rd party util)

unable to read machine info out of the minidump for some reason.

----------
search your system for memory.dmp by default it should be in c:\windows
it is a large file but you should be able to just copy it up to your server and share it out.

Habbelfisk :

Habbelfisk · May 3, 2015

johnbl :

the new bugcheck was bughcek 0x117 VIDEO_TDR_TIMEOUT_DETECTED
basically the graphics adapter/hardware failed to respond and directx called a bugcheck because of it.

it is a minidump, and verifier is not on. this can not be debugged with a minidump.

suspect drivers list:
update or remove this USB apple device charger driver (memory corruption)
AppleCharger.sys Mon Jan 10 01:57:29 2011

BitDefender AntiVirus FS filter driver
bdfsfltr.sys Wed Mar 23 06:52:33 2011 (too old, remove)

update your razer drivers (memory corruption problems)
rzdaendpt.sys Tue Nov 06 23:49:58 2012
rzudd.sys Tue Nov 06 23:49:47 2012
rzvkeyboard.sys Tue Nov 06 23:49:55 2012

PowerISO Virtual Drive driver (update)
SCDEmu.SYS Sun Dec 09 00:46:41 2012

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver (I think this failed verifier, or was it updated?)
ScpVBus.sys Sun May 05 14:31:26 2013

SmartDefragDriver.sys Mon Dec 23 02:05:52 2013 (just not a good idea to replace the OS defrag with a 3rd party util)

unable to read machine info out of the minidump for some reason.

----------
search your system for memory.dmp by default it should be in c:\windows
it is a large file but you should be able to just copy it up to your server and share it out.

Habbelfisk :

I deleted Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver (scpvbus.sys) already, It was the one causing Blue Screens on boot when Verifier was on. Do you want me to keep running Verifier till I've cleaned out bad drivers? Or will that take 500 years or something like that?
I'll delete/update the other drivers you listed as well.

I know about the memory.dmp file and I know where it is located, I've been trying to share it for the entire span of this post but it won't go anywhere online. If I put it in dropbox it won't sync, when I tried sending it to Nexon it wouldn't upload or w/e.

Any ideas on how I can share it with you? I have 2 of those dumps saved on my desktop atm but I still can't seem to share them in any way...
I believe the file is protected and require some changes in order to be shared.

Thanks

johnbl · May 4, 2015

the file is in a directory that you don't have full rights to, you can move it or copy it to a new location.
mediafire and microsoft onedrive seem to work fine for most people.

normally, you would use verifier and work thru all the bad drivers.
it should be a finite list because if you have windows update installed the bad driver is likely to be a OEM driver not a microsoft driver. you can turn of verifier if you have to. it is more important to get a kernel memory dump or full memory dump so the debugger can look at some internal windows errors and common problems that are not recorded in a minidump file.

Habbelfisk :

johnbl :

I deleted Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver (scpvbus.sys) already, It was the one causing Blue Screens on boot when Verifier was on. Do you want me to keep running Verifier till I've cleaned out bad drivers? Or will that take 500 years or something like that?
I'll delete/update the other drivers you listed as well.

I know about the memory.dmp file and I know where it is located, I've been trying to share it for the entire span of this post but it won't go anywhere online. If I put it in dropbox it won't sync, when I tried sending it to Nexon it wouldn't upload or w/e.

Any ideas on how I can share it with you? I have 2 of those dumps saved on my desktop atm but I still can't seem to share them in any way...
I believe the file is protected and require some changes in order to be shared.

Thanks

Habbelfisk · May 4, 2015

There we go, changed privelegies options which didn't really make sense. Could then zip them together, however I've put it on dropbox.

https://www.dropbox.com/s/ieynxqqobpzh66n/MEMORY%20%282%29.rar?dl=0

I deleted/updated the drivers you had listed earlier, though I can't manage to delete
"BitDefender AntiVirus FS filter driver bdfsfltr.sys Wed Mar 23 06:52:33 2011" Because it is currently open in System, I've searched Task Manager for the bdsfltr.sys / Bitdefender in both services and processes but can't seem to terminate the process.

So should I turn on verifier and go on or will that not fix the issue? Sorry didn't quite get that part.
Or should I keep making these changes, reporting dumpfiles hoping for one to show what driver is the issue?

Will try running the game now.

johnbl · May 4, 2015

first bugcheck was 0x101
the memory dump was corrupted, it also indicated no page file .

second memory dump looks good. looks like a bug in ScpVBus.sys the driver did not fill out a required routine in the driver.
will look at it when I get back from lunch.

Habbelfisk · May 4, 2015

johnbl :

Alright, thanks.
*Updated* https://www.dropbox.com/sh/bi69xbd93ntowh8/AAChlfbebsFmfhmgGBPE45_da?dl=0

Did run the game and got a x101 just 30 seconds into the game.
Link for following dump is in the dropbox folder in the MEMORY.rar and is Memory (3).
Seems to be x101's now. These seem alot more trustworthy than the minidumps.

"On Mon 2015-05-04 21:15:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88002D65180)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002D65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT"

*According to WhoCrashed.*

Adding to this, since I deleted those drivers you listed earlier (except from bdsfltr.sys) they can't have been the issue. Or atleast they're not now since I crashed again. Did get a blue screen this crash, for the record.

Also if you can't access Dropbox links tell me, there's supposed to be 3 dumps in the .rar file atm, higher number is latest dump.

Greatful for the help, the support on Nexon and Microsoft can't beat this

BSoD running Maplestory

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Polypheme

Distinguished

Share this page