BSOD Playing games, driver maybe? error 0x116

Pharanoia · 09 Aug 2015

Hello

I've been having a lot of troubles since i upgraded my hardware, games crashing, BSOD and pc reboots (at least this one was solved), i tried almost everything since updating bios to lates (beta) putting it the old ones, clean install, tried almost 7 different drivers, almost everything i looked on the internet but without being able to solve it

. Hope you guys could help.

Plus, no overheating shown by MSI Afterburner

Thanks in advance.

ICIT2LOL · 09 Aug 2015

Hello and welcome Pharanoia mat where did you get this oS form as I have a nasty feeling it is pirated or a very old media the version I have marked in red should read 7601 - that is it has service pack 1 (SP1) included which version 7600 does not.

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\John\AppData\Local\Temp\Temp1_GHOST-09_08_2015__20947,61.zip\080915-12308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e50
Debug session time: Sun Aug  9 17:00:30.735 2015 (UTC + 10:00)
System Uptime: 0 days 0:39:22.234
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list

Pharanoia · 09 Aug 2015

I'll update win 7 tomorrow and make a few test to report back

ICIT2LOL · 09 Aug 2015

Ok if you go to Start and type in the box "msinfo32" (no quotation marks) it should bring up your system info as in my pic see what it says there. I do stand to be corrected though if you have some form of multi machine setup but it does look odd.

Laith · 09 Aug 2015

Hiya and welcome to SevenForums!

Thought you might need a little help, ICIT2LOL,

Code:

BugCheck A, {fffff88005569930, 2, 0, fffff800030a78d5}

Probably caused by : memory_corruption ( nt!MiDeletePteRun+4e5 )

Code:

BugCheck 116, {fffffa8009d7c010, fffff88006a55cac, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+ccac )

Code:

BugCheck 50, {fffffa800a276028, 0, fffff800030e5694, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+194 )

Code:

BugCheck 3B, {c0000005, fffff96000174283, fffff88008278020, 0}

Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )

Code:

BugCheck 19, {22, 2000000, 0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllocations+715 )

Code:

BugCheck 7F, {8, 80050033, 406f8, fffff800030ca301}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Code:

BugCheck 50, {ffffffffffffffc8, 0, fffff880113da22e, 0}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+c2 )

Code:

BugCheck F7, {6696049, f8800129301e, ffff077ffed6cfe1, 0}

Probably caused by : hardware ( Ntfs!_report_gsfailure+26 )

Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: Display Driver Uninstaller: How to use

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

SFC /SCANNOW Command - System File Checker

Run MemTest86+, It must be MemTest86+. RAM - Test with Memtest86+

Check for viruses using Malwarebytes Malwarebytes Anti-Malware Free

Run SeaTools(DO NOT RUN FOR SSDS) SeaTools for DOS and Windows - How to Use

ICIT2LOL · 09 Aug 2015

Thanks Laith I was going to suggest the sfc and chkdsk but the build number threw me because it looks like it has not got SP1

The memtest if we are going to run it I have a little ditty to explain it - sticks and slots

Suppose we shall have to hear back before we can do anything really.
John

Laith · 09 Aug 2015

No problem :)
Yup, he should update to SP1 ASAP, as it's important.
That's handy, good thing that we have such a hardware expert around here

Yup, we'll just wait and see.

Pharanoia · 09 Aug 2015

Laith said:

No problem :)
Yup, he should update to SP1 ASAP, as it's important.
That's handy, good thing that we have such a hardware expert around here

Yup, we'll just wait and see.

So i just intall SP1 or all updates?

Laith · 09 Aug 2015

All updates including SP1.

Pharanoia · 09 Aug 2015

Laith said:

Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: Display Driver Uninstaller: How to use

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

SFC /SCANNOW Command - System File Checker

Run MemTest86+, It must be MemTest86+. RAM - Test with Memtest86+

Check for viruses using Malwarebytes Malwarebytes Anti-Malware Free

Run SeaTools(DO NOT RUN FOR SSDS) SeaTools for DOS and Windows - How to Use

Well, i've runned all test and it seems i was the almost 220 viruses detected by Malwarebytes, all other test succeed, installed updates... Now, do i start testing the pc or run DM Log Collector again?