BSOD playing Mechwarrior Online, STOP: 0x000000c4

tobi3000 · 27 Dec 2013

Hello everybody...

Like the thread title says, I regulary get a BSOD when playing Mechwarrior Online, an online-game with modern 3d-graphics. This happens not always and on some maps it seems to happen more frequent than on others. Sometimes I have the BSOD, but more often the game just freezes and I have to turn off the computer. I'm playing on my Laptop.

Thank you very much!!

Arc · 28 Dec 2013

Never noticed this behavior with this driver version

So at the beginning I am thinking that the driver installation is not correct. Do it as follows:

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Also, Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

Double click to open it.
Click this button only:
If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus and the touchpad driver SynTPEnh.
Apply > OK
Accept then restart.

Also, scan the system for possible virus infection with the following programs. It is needed, as a driver is behaving like a BUG. It is all possible for a rootkit to disguise as a driver.

Let us know the results. Your feedback will be HIGHLY important to determine our way of future course of actions, in a broader sense.
_______________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffff80003c0ccc0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+18b286 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80003c0ccc0
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80005336398 -- (.exr 0xfffff80005336398)
ExceptionAddress: fffff88009250286 (nvlddmkm+0x000000000018b286)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80005336440 -- (.trap 0xfffff80005336440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000100042
rdx=fffffa800bf2c000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88009250286 rsp=fffff800053365d0 rbp=fffff800053365d0
 r8=fffffa800bf2c368  r9=0000000000400108 r10=fffffa800bf2c000
r11=0000000000400108 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0x18b286:
fffff880`09250286 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ada4fa to fffff80003a83bc0

STACK_TEXT:  
fffff800`05335498 fffff800`03ada4fa : 00000000`000000c4 00000000`00000091 00000000`00000002 fffff800`03c0ccc0 : nt!KeBugCheckEx
fffff800`053354a0 fffff800`03aad153 : 5422203d`20444945 00202020`36372d50 5f37372d`00000003 20444945`4c424154 : nt! ?? ::FNODOBFM::`string'+0x4884
fffff800`053354e0 fffff800`03abe4c1 : fffff800`05336398 fffff800`053360f0 fffff800`05336440 fffffa80`0bf2c000 : nt!RtlDispatchException+0x33
fffff800`05335bc0 fffff800`03a83242 : fffff800`05336398 fffffa80`0a2d52d0 fffff800`05336440 fffffa80`0bf7d1a0 : nt!KiDispatchException+0x135
fffff800`05336260 fffff800`03a81b4a : 03bb8e00`001093c0 00000000`fffff800 03bb8e00`001093d0 00000000`fffff800 : nt!KiExceptionDispatch+0xc2
fffff800`05336440 fffff880`09250286 : fffff800`05336610 fffff880`0945f6a6 fffffa80`0a2d52d0 fffffa80`0bf7d1a0 : nt!KiGeneralProtectionFault+0x10a
fffff800`053365d0 fffff800`05336610 : fffff880`0945f6a6 fffffa80`0a2d52d0 fffffa80`0bf7d1a0 fffffa80`0bf2c000 : nvlddmkm+0x18b286
fffff800`053365d8 fffff880`0945f6a6 : fffffa80`0a2d52d0 fffffa80`0bf7d1a0 fffffa80`0bf2c000 fffff880`00000000 : 0xfffff800`05336610
fffff800`053365e0 fffffa80`0a2d52d0 : fffffa80`0bf7d1a0 fffffa80`0bf2c000 fffff880`00000000 fffffa80`0bf2c000 : nvlddmkm+0x39a6a6
fffff800`053365e8 fffffa80`0bf7d1a0 : fffffa80`0bf2c000 fffff880`00000000 fffffa80`0bf2c000 00000000`00400108 : 0xfffffa80`0a2d52d0
fffff800`053365f0 fffffa80`0bf2c000 : fffff880`00000000 fffffa80`0bf2c000 00000000`00400108 fffff800`05336670 : 0xfffffa80`0bf7d1a0
fffff800`053365f8 fffff880`00000000 : fffffa80`0bf2c000 00000000`00400108 fffff800`05336670 fffff880`092d35fe : 0xfffffa80`0bf2c000
fffff800`05336600 fffffa80`0bf2c000 : 00000000`00400108 fffff800`05336670 fffff880`092d35fe fffffa80`0c25f9e0 : 0xfffff880`00000000
fffff800`05336608 00000000`00400108 : fffff800`05336670 fffff880`092d35fe fffffa80`0c25f9e0 00000000`00000000 : 0xfffffa80`0bf2c000
fffff800`05336610 fffff800`05336670 : fffff880`092d35fe fffffa80`0c25f9e0 00000000`00000000 fffff800`053366f8 : 0x400108
fffff800`05336618 fffff880`092d35fe : fffffa80`0c25f9e0 00000000`00000000 fffff800`053366f8 00000000`00000020 : 0xfffff800`05336670
fffff800`05336620 fffffa80`0c25f9e0 : 00000000`00000000 fffff800`053366f8 00000000`00000020 fffff800`00000000 : nvlddmkm+0x20e5fe
fffff800`05336628 00000000`00000000 : fffff800`053366f8 00000000`00000020 fffff800`00000000 fffff880`0927e26b : 0xfffffa80`0c25f9e0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+18b286
fffff880`09250286 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  nvlddmkm+18b286

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c

FAILURE_BUCKET_ID:  X64_0xc4_91_nvlddmkm+18b286

BUCKET_ID:  X64_0xc4_91_nvlddmkm+18b286

Followup: MachineOwner
---------

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`090c5000 fffff880`09b70000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

tobi3000 · 07 Jan 2014

Thank you for your help and the detailed instructions. And sorry for the late reply... it took me some time to do everything and expecially to test, if the error appears again.

Unfortunately it does. It's still the same. When I play the game, it mostly just freezes. Only sometimes I get the BSOD. The same as before. And I can clearly observe that it happens on some "maps" of the game more frequently than on others. There is one map, where it happens every second time. There are some other maps, where it - as I remember - never happend.

So I followed all your instructions. But when I reinstalled the graphics driver I could not reinstall the PhysX System Software. I tried several times but without success.

I also uninstalled Deamon Tools and used that SPTD-Installer.

Then I scanned for virus infections, but didn't find anything.

Also I cleaned the AutoStartup of everything but the Anti-Virus and Touchpad... Now I have also Skype and Dropbox starting automatically again.

After all this brought no success I tried to use a Notebook Cooler, because I thought that the system might just run too hot. Unfortunately it also makes no difference.

So do you still have any idea, what I could do? I'd really like to get rid of this error. If there's no other solution I'd try to reinstall the whole system when I find the time.

Arc · 07 Jan 2014

To frame the further idea, we need to see the further files. So post it following the Blue Screen of Death (BSOD) Posting Instructions. :)

tobi3000 · 07 Jan 2014

ok... here is the file

Arc · 07 Jan 2014

As per the uploaded zip, the last BSOD was on 01/01.

Attachment 300689

What is the situation after that?

tobi3000 · 07 Jan 2014

That's right... that last BSOD was already after I followed your instructions. Since then the game froze many many times, but I didn't have BSOD no more. As I wrote the BSODs only appear rarely.

But (at least from my noob point of view) I think both may have the same origin. Because BSOD and freezing of the game happen in the same situations. In both cases the sound turns into ugly noise that repeats all the time.

Arc · 07 Jan 2014

In that case, can you contract the game developer in their site/forum? They have custom settings and patches etc that can make the game run smoothly in your system.

tobi3000 · 07 Jan 2014

Ok, I will try this next. Thank you for your support so far.