BSOD and broken display in normal mode, all started because of crash midgame LoL

ThePraisedOne · Jul 29, 2012

I was playing the game League of Legends and in the middle of the game the computer just shutdowns. When i started it up again the display wasn't working anymore in normal mode. I heard the laptop starting up and the start jingle but i didn't see anything. I tried starting in safe mode and there everything was working fine, when i started in normal mode again i got this BSOD and the problem still persists.

I wrote this from safe mode.

perfmon /report dint work so its just the Windows7_Vista_jcgriff2

-Windows 7
-64 bit
-it came pre installed on the system.
- I bought the laptop more than 1 year ago.
- Never reainstalled
- HP G72- B10SD

Does anyone see the attachment?

View attachment 1191

Corrine · Jul 29, 2012

Hi, ThePraisedOne. Welcome to Sysnative!

Attachments with vBulletin software can sometimes show up in a strange location, depending on the position of your cursor when adding the attachment. I edited your post to move it from the middle of your first paragraph to the bottom of the post.

Laxer · Jul 29, 2012

@Corrine, can you D/L it? I cannot...

The file does not look like it was uploaded completely.

Try instead of using the button in the editor scroll down a bit in the advanced reply page and click the "Manage Attachments" button

ThePraisedOne · Jul 29, 2012

Laxer said:
@Corrine, can you D/L it? I cannot...

The file does not look like it was uploaded completely.

Try instead of using the button in the editor scroll down a bit in the advanced reply page and click the "Manage Attachments" button

I just downloaded it myself, and it seems alright. All the files are there.

Laxer · Jul 29, 2012

It finally went through here as well, stuck at ~70% for a few minutes which is odd...

Thank you for double checking.

ThePraisedOne · Jul 29, 2012

I cant respond to this topic till tomorrow. Thanks for helping me

Corrine · Jul 29, 2012

Not to worry, ThePraisedOne, one of the analysts will have had an opportunity to review your logs by then.

writhziden · Jul 30, 2012

Device Concerns:

Code:

Security Processor Loader Driver    ROOT\LEGACY_SPLDR\0000    This device is not present, not working properly, or does not have all its drivers installed.

The above may be due to being in Safe Mode, or it may indicate a display card driver issue. See Recommendations: for steps to re-install the display card driver. You may need Error “The Windows Installer Service Could Not Be Accessed” when installing or updating programs on Windows 7 or Windows Vista:

Method 2: Start the Windows Installer Service

Analysis:

The following is for information purposes only.

Code:

**************************Sat Jul 28 16:05:46.753 2012 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\ThePraisedOne\072912-70465-01.dmp]
Windows 7 Kernel Version[B]7600 MP (4 procs) Free x64[/B] MP (4 procs) Free x64
System Uptime:[B]0 days 0:01:07.532[/B]
BugCheck Code: [B]BugCheck 116, {fffffa8006d544e0, fffff88002f00c58, 0, 2}[/B]
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]atikmpag.sys ( atikmpag+6c58 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_atikmpag.sys[/B]
CPUID:        "Intel(R) Core(TM) i3 CPU       M 350  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed:[B]2261[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 28 16:00:24.500 2012 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\ThePraisedOne\072912-73585-01.dmp]
Windows 7 Kernel Version[B]7600 MP (4 procs) Free x64[/B] MP (4 procs) Free x64
System Uptime:[B]0 days 0:01:09.279[/B]
BugCheck Code: [B]BugCheck 116, {fffffa8006b324e0, fffff88002efbc58, 0, 2}[/B]
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]atikmpag.sys ( atikmpag+6c58 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x116_IMAGE_atikmpag.sys[/B]
CPUID:        "Intel(R) Core(TM) i3 CPU       M 350  @ 2.27GHz"
MaxSpeed:     2270
CurrentSpeed:[B]2261[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
****************************************************
Loading Dump File [C:\Users\Mike\Downloads\ThePraisedOne\072912-62244-01.dmp]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:

The following is for information purposes only. Any drivers in red should be updated.

Code:

**************************Sat Jul 28 16:05:46.753 2012 (GMT-6)**************************
GEARAspiWDM.sys         Mon May 18 06:17:04 2009 (4A1151C0)
intelppm.sys            Mon Jul 13 17:19:25 2009 (4A5BC0FD)
HECIx64.sys             Thu Sep 17 13:54:16 2009 (4AB293E8)
RTKVHD64.sys            Fri Mar 12 14:47:03 2010 (4B9AB657)
amdxata.sys             Fri Mar 19 10:18:18 2010 (4BA3A3CA)
iaStor.sys              Tue Apr 13 10:44:16 2010 (4BC49F60)
AtiHdmi.sys             Thu May  6 03:20:39 2010 (4BE289E7)
bcmwl664.sys            Fri May  7 17:59:43 2010 (4BE4A96F)
SynTP.sys               Thu May 27 15:41:36 2010 (4BFEE710)
igdpmd64.sys            Wed Jun  2 10:43:16 2010 (4C068A24)
atikmpag.sys            Mon Jun 21 19:24:10 2010 (4C2010BA)
atikmdag.sys            Mon Jun 21 19:49:15 2010 (4C20169B)
clwvd.sys               Tue Jul 27 19:13:47 2010 (4C4F844B)
BazisVirtualCDBus.sys   Thu Oct 28 08:10:59 2010 (4CC98473)
cnnctfy2.sys            Fri Jun 24 09:29:01 2011 (4E04AD3D)
MpFilter.sys            Fri Mar  9 04:05:26 2012 (4F59E3F6)

Recommendations:

BugCheck 0x116

These crashes are DirectX/graphics card related. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

If you are overclocking any hardware, please stop.
Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. If you hae errors, proceed to

To determine which files could not be repaired by the System File Checker tool, follow these steps:

Click to expand...

in SFC /SCANNOW Command - System File Checker and upload the sfcdetails.txt file.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

Download the drivers you want for your display card(s)
Click Start Menu
Click Control Panel
Click Uninstall a program
For NVIDIA:
- Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
- Restart your computer
- Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
- If any remain of the above, uninstall one at a time
- If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
For AMD:
- Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
- If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Expand Display adapters
  6. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  Alternatively:
  1. Login as an adminstrative user
  2. Click Start Menu
  3. Click Control Panel
  4. Click Hardware and Sound
  5. Click Device Manager (the last link under Devices and Printers)
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For 0x116 Video TDR Error crashes: A 0x116 TDR crash means the system sent a signal to the display card to refresh the video, and the display card did not respond. This may be due to a driver error or a hardware error with respect to the display card.

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.
Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
  FurMark Steps:
  1. First, download and install the latest version of FurMark.
  2. Run FurMark as an administrator
  3. Find your display resolution by right clicking the Desktop and clicking Screen resolution and enter it into FurMark's options:
  4. Change FurMark's settings as in the image. You want to run it for 20 minutes or until it reaches the alarm temperature you set up. 90 is a good number for AMD display cards, 80 or 85 is probably best for NVIDIA cards. The best method to set the temperature alarm is the maximum temperature of your card minus 10 C. Again, if you do not know the maximum temperature, and you cannot find it through a Google search, ask us to find it for you.
  5. Run the Benchmark with user's settings and stop it once the temperature reaches a constant temperature, once the card reaches the alarm temperature, or once the video shows artifacts or strange colors.
- Run Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
Run the boot version of Memtest86+. Let it run for at least 7-10 passes (preferably more) or until errors show up.

If you see even one error, stop the test and do the following:
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

Click to expand...
1. Shut down and turn off your computer.
2. Unplug all power sources to the system: unplug the power from the outlet/surge protector or PSU (then remove the battery if it is a laptop).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing (or remove the RAM panel if it is a laptop).
5. Remove all but one memory module making sure you are grounded while doing so.
  Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
6. Replace the casing (or replace the RAM panel if it is a laptop) and put the remaining memory module(s) in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).
Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.
Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. You may want to run both Memtest86+ and the Windows Memory Diagnostics Tool overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

BSOD and broken display in normal mode, all started because of crash midgame LoL

ThePraisedOne

New member

Corrine

Administrator,
Microsoft MVP,
Security Analyst

Laxer

Co-Founder
Senior Administrator

ThePraisedOne

New member

Laxer

Co-Founder
Senior Administrator

ThePraisedOne

New member

Corrine

Administrator,
Microsoft MVP,
Security Analyst

writhziden

Administrator, .NET/UWP Developer

BSOD and broken display in normal mode, all started because of crash midgame LoL

New member

Administrator, Microsoft MVP, Security Analyst

Co-FounderSenior Administrator

New member

Co-FounderSenior Administrator

New member

Administrator, Microsoft MVP, Security Analyst

Administrator, .NET/UWP Developer

Administrator,
Microsoft MVP,
Security Analyst

Co-Founder
Senior Administrator

Co-Founder
Senior Administrator

Administrator,
Microsoft MVP,
Security Analyst