BSOD(?) playing Minecraft

[FloppyDingo]

Recently I've had some issues with my computer randomly rebooting while playing Minecraft, or so I thought it was a reboot. It seems windows created a minidump file which would point at it having been a BSOD I believe.

It seems random, but when I play I'll be on for anywhere between 10 minutes to half an hour before the computer suddenly seems to reboot.

Things I have tried so far:

Updated my video card driver.
Updated Java (both 32 and 64 bit java)
Ran RegClean Pro and fixed some registry problems.
Monitored CPU and GPU heat while playing to ensure it was not an overheating issue.
Googled the problem several times with different wording, checking out various threads on similar issues. (to no avail)

So now I put myself in your hands!

 

[koolkat77]

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800c4604e0, fffff88009e236c4, ffffffffc000009a, 4}

Unable to load image 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+9316c4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c4604e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88009e236c4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+9316c4
fffff880`09e236c4 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0399da48 fffff880`08145054 : 00000000`00000116 fffffa80`0c4604e0 fffff880`09e236c4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0399da50 fffff880`08118867 : fffff880`09e236c4 fffffa80`0a727000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0399da90 fffff880`08144e63 : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0c4604e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0399db40 fffff880`0803803d : fffffa80`097a6110 00000000`00000080 00000000`00000000 fffffa80`0a71b390 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0399dbc0 fffff800`03513bae : 00000000`fffffc32 fffffa80`0a742a00 fffffa80`066f9040 fffffa80`0a742a00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0399dc00 fffff800`032668c6 : fffff800`033f0e80 fffffa80`0a742a00 fffff800`033fecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0399dc40 00000000`00000000 : fffff880`0399e000 fffff880`03998000 fffff880`0399d4d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9316c4
fffff880`09e236c4 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+9316c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`094f2000 fffff880`09f9a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Feb 10 05:13:08 2013 (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Free up the start-up, nothing except the antivirus is usually needed.
http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Follow this -

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

• 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
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall Daemon Tools.
DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the rb:
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your hard disk for file system errors and bad sectors on it:
http://www.sevenforums.com/tutorials/433-disk-check.html

Upload a screenshot using:
CrystalDiskInfo
:tip: For how to upload a screenshot or file, read here

Test your Hard Drive by running:
Hard Drive Diagnostic Procedure

Test and Diagnose RAM Issues with Memtest86+:
RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:

]CPUID - HWMonitor

 

[VistaKing]

Id personally remove RegClean Pro

 

[FloppyDingo]

Thanks a lot for the replies. Here's what I've done so far:

I've cleaned up my start up programs (which really helped with the initial log in of windows, it was going slow).

I've updated my SSD firmware.
I updated my BIOS (turns out I had never done this and there was quite a bit of updating to do!)
I updated my chipset drivers.
I updated my SATA drivers.

I uninstalled the latest NVIDIA drivers and ran DriverSweeper to clean up old driver files, and installed ONLY the shown driver files for 314.22 WHQL.

I uninstalled Daemon Tools.

I ran System File Checker - it showed nothing out of the ordinary.
I ran Check Disk - it showed nothing out of the ordinary.

The screenshots of my hard drives from Crystal Disk Info are attached to this post.

I could -not- run the Hard Drive Diagnostic Procedure - I do not have a CD/DVD rom drive on this tower. I borrowed a friends (newegg was supposed to bundle one with one of my purchases but they ran out, so I just never bought one).

I attempted to make my USB stick into a Memtest86+ stick, and it said it succeeded but I couldn't for the life of me figure out how to make my BIOS launch from the stick.

I'll try running the game now and come back to you if it restarts again.

 

[koolkat77]

Thanks for the clear feedback.
Hope it works for you!

 

[FloppyDingo]

Sadly it doesn't seem to have solved the issue yet. I uploaded a new cache of info as well as the new minidump.

 

[koolkat77]

Have a look at this thread
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[FloppyDingo]

Have a look at this thread
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

I'm not sure what I'm supposed to be reading there but I've tried a few more things:

I've tried reinstalling both Java and Minecraft entirely. I've tried using an older version of Java (Java 7 update 21 rather than 25).

Other games DO NOT crash, so by that standard you would think it's something specifically regarding minecraft correct? Because if it was an issue with the Video Card itself, or my RAM other games would trigger it right?

 

[FloppyDingo]

Searching the official microsoft forums I came to notice that one of the most common things in my Event Viewer referred to Microsoft Security Essentials having an issue. Someone on the forums suggested that some people there had some issues with it causing BSOD's, so I've for the moment removed it and replaced it with Avast! to see if that improves the situation.

 

[FloppyDingo]

I'm noticing every time I crash the same error is in my event viewer:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

 

[FloppyDingo]

I'm noticing every time I crash the same error is in my event viewer:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

I'm also noticing this is no longer a blue screen issue. When the computer restarts it does not leave a minidump.

 

[Arc]

I'm noticing every time I crash the same error is in my event viewer:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

This has nothing to do with a stop 0x116 BSOD, which is a display/graphics failure.

Have you followed the suggested steps?

And, if you have issue with a particulat game only, better you consult the game developer. May be some custom settings or patch is needed there.

 

[FloppyDingo]

I'm noticing every time I crash the same error is in my event viewer:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

This has nothing to do with a stop 0x116 BSOD, which is a display/graphics failure.

Have you followed the suggested steps?

And, if you have issue with a particulat game only, better you consult the game developer. May be some custom settings or patch is needed there.

I've followed them to the best of my ability yes.

This morning I dusted out my computer and reseated everything, gpu, ram. While doing so I switched the ram sticks around (put the 2nd stick in the first slot, first where the second was) and noticed something odd:

When I turned on my computer after that, it would power on for a moment, then turn off, then turn back on - but it wouldn't show a screen. The screen was saying the HDMI was giving no output.

When I switch the sticks of ram -back- the computer turns on just fine. Bad stick of ram?

 

[Arc]

May be. If there is a doubt, test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

 

[FloppyDingo]

Memtest came up clean.

 

[Arc]

You have 4x4 GBs of memory .... which should take a few hours to run 8 passes at least.

May be the memory sticks was not properly placed .... or it is a defect from motherboards part.

 

[FloppyDingo]

Ran the ram test all day today, 0 errors.

 

[d00p98uy]

well, the regclean PRO itself should be removed, replace it with the portable CCleaner if you must have a registry scanner, that way you don't need to install anything and can run the best registry scanner in the world(IMHO), make sure to backup your registry first!

 

[Arc]

Ran the ram test all day today, 0 errors.

Good information. Anyway, use the settings of RAM which is working good.
Let us know for any further BSOD.

redfang337, a registry cleaner can cause many a troubles, but merely a BSOD. As it is a BSOD issue, we concentrate to the issue first and maintenance later.