New
#1
BSOD Playing League of Legends: Error 0x0000007f
Couple of BSOD's lately, last two were whilst playing League of Legends.
Not sure if it might be because of the game or not.
Attachment 303103
Couple of BSOD's lately, last two were whilst playing League of Legends.
Not sure if it might be because of the game or not.
Attachment 303103
Here you go.
Attachment 303399
WinDBG pinpoints a video display problem. Try this updated driver:Code:bb540298 93b7ba70Unable 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 nvlddmkm+0x752a70
Drivers | GeForce
Was just browsing the web when I got this BSOD.
Attachment 304960
Hi Brutmax.
The stray crash dump itself is not providing sufficient information.
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.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
__________________________________________________________________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {80000004, 0, 9c1fe3a9, 0} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!XDCOBJ::bDeleteDC+6d ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: 80000004, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 9c1fe3a9, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from 839b784c Unable to read MiSystemVaType memory at 83996e20 80000004 FAULTING_IP: win32k!XDCOBJ::bDeleteDC+6d 9c1fe3a9 8b7f04 mov edi,dword ptr [edi+4] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: calc.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre TRAP_FRAME: 90993c1c -- (.trap 0xffffffff90993c1c) ErrCode = 00000000 eax=fe533008 ebx=80000000 ecx=89dffc38 edx=8ec84f00 esi=90993cfc edi=80000000 eip=9c1fe3a9 esp=90993c90 ebp=90993ca0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 win32k!XDCOBJ::bDeleteDC+0x6d: 9c1fe3a9 8b7f04 mov edi,dword ptr [edi+4] ds:0023:80000004=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 8388eaa8 to 838db879 STACK_TEXT: 90993c04 8388eaa8 00000000 80000004 00000000 nt!MmAccessFault+0x104 90993c04 9c1fe3a9 00000000 80000004 00000000 nt!KiTrap0E+0xdc 90993ca0 9c1fe724 00000000 0caae90b 00000000 win32k!XDCOBJ::bDeleteDC+0x6d 90993cdc 9c1fe533 90993cfc ffaff008 00000000 win32k!bDeleteDCInternalWorker+0x1b6 90993d08 9c1e1f9e a40110d6 00000000 00000000 win32k!bDeleteDCInternal+0x30 90993d28 8388b8c6 a40110d6 0018e864 770370f4 win32k!NtGdiDeleteObjectApp+0xa0 90993d28 770370f4 a40110d6 0018e864 770370f4 nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 0018e864 00000000 00000000 00000000 00000000 0x770370f4 STACK_COMMAND: kb FOLLOWUP_IP: win32k!XDCOBJ::bDeleteDC+6d 9c1fe3a9 8b7f04 mov edi,dword ptr [edi+4] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: win32k!XDCOBJ::bDeleteDC+6d FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5294737c IMAGE_VERSION: 6.1.7601.18327 FAILURE_BUCKET_ID: 0x50_win32k!XDCOBJ::bDeleteDC+6d BUCKET_ID: 0x50_win32k!XDCOBJ::bDeleteDC+6d ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x50_win32k!xdcobj::bdeletedc+6d FAILURE_ID_HASH: {2d9eed55-413e-f8e0-ee4c-28da011e688b} Followup: MachineOwner ---------