Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Frequent BSOD while playing League of Legends [ntoskrnl.exe]

19 May 2014   #11
ThatBenderGuy

Windows 7 Professional 64-bit
 
 

Here are some dumps from the past few days


My System SpecsSystem Spec
.
19 May 2014   #12
Thedoctor44

 

Can you switch to Kernel Memory Dumps.

Follow these instructions on how to change your dump files to Kernel Memory Dumps.

Dump Files - Configure Windows to Create on BSOD

Once your dump file creation has changed, reboot the computer and wait for another BSOD.
When a new BSOD has occurred go to this directory:
C:/Windows/memory.dmp

Copy that dump file to the desktop, then upload it to a program like OneDrive, once uploaded post the link in your next reply and I'll take a look.
My System SpecsSystem Spec
19 May 2014   #13
ThatBenderGuy

Windows 7 Professional 64-bit
 
 

Okay here is the link to the memory.dmp file that was created after I recieved a BSOD after switching to kernal memory dump

https://onedrive.live.com/redir?resi...D4F258D1%21107
My System SpecsSystem Spec
.

20 May 2014   #14
Thedoctor44

 

Your realtek network driver is out of date.

Code:
fffff880`0426f000 fffff880`04322000   Rt64win7   (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Jun 12 15:00:29 2012 (4FD74B7D)
    CheckSum:         000B8CFC
    ImageSize:        000B3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
I need your msinfo32 file.

Click on this button.



Once downloaded run the file as administrator then upload the folder created on your desktop.
My System SpecsSystem Spec
20 May 2014   #15
ThatBenderGuy

Windows 7 Professional 64-bit
 
 

Here's the folder that was given to me from the application, i'm looking up the updated drivers right now for realtek network driver
My System SpecsSystem Spec
20 May 2014   #16
Thedoctor44

 

Download the driver here:

Realtek

Make sure you choose the right version for your OS.

Just to make sure, create a restore point by following these instructions.
My System SpecsSystem Spec
20 May 2014   #17
ThatBenderGuy

Windows 7 Professional 64-bit
 
 

Alright I installed the driver after creating a restore point. Why was it you needed that msinfo32 file?
My System SpecsSystem Spec
20 May 2014   #18
ThatBenderGuy

Windows 7 Professional 64-bit
 
 

Ok so I got another BSOD but I decided to look at memory.dmp with WindDbg and it's telling me that chrome.exe was probably the cause. That's odd that it would be my browser causing BSODs

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8009ffbbd0, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: c100000000000002, Reserved
	The reference count of an object is illegal for the current state of the object.
	Each time a driver uses a pointer to an object the driver calls a kernel routine
	to increment the reference count of the object. When the driver is done with the
	pointer the driver calls another kernel routine to decrement the reference count.
	Drivers must match calls to the increment and decrement routines. This bugcheck
	can occur because an object's reference count goes to zero while there are still
	open handles to the object, in which case the fourth parameter indicates the number
	of opened handles. It may also occur when the object’s reference count drops below zero
	whether or not there are open handles to the object, and in that case the fourth parameter
	contains the actual value of the pointer references count.

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


DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000302fe14 to fffff80003089bc0

STACK_TEXT:  
fffff880`089efa08 fffff800`0302fe14 : 00000000`00000018 00000000`00000000 fffffa80`09ffbbd0 00000000`00000002 : nt!KeBugCheckEx
fffff880`089efa10 fffff800`0333ea7d : fffff880`089efb60 00000000`00000000 00000000`00000000 00000000`73947b00 : nt! ?? ::FNODOBFM::`string'+0x48de1
fffff880`089efa70 fffff800`03088e53 : fffffa80`0a29a060 00000000`00000000 00000000`00000000 fffffa80`0a244101 : nt!NtReleaseSemaphore+0xcd
fffff880`089efae0 00000000`73912e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`035bee58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73912e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+48de1
fffff800`0302fe14 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+48de1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48de1

BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48de1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x18_corrupt_ref_count_nt!_??_::fnodobfm::_string_+48de1

FAILURE_ID_HASH:  {d3af5bf2-5e99-93a2-1458-fbf7f0106024}

Followup: MachineOwner
---------
here is the link to the dump on my oneDrive

https://onedrive.live.com/redir?resi...D4F258D1%21109
My System SpecsSystem Spec
21 May 2014   #19
Thedoctor44

 

You didn't roll back your display driver as requested earlier.
Roll back to 314.22 as directed previously.

Code:
fffff880`0f0ca000 fffff880`0fd22000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Mar 04 11:07:52 2014 (5315B408)
    CheckSum:         00C20523
    ImageSize:        00C58000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
The latest driver is looping a lot,

Code:
fffff880`089edd68  fffff880`0f2b6152 nvlddmkm+0x1ec152
fffff880`089edd70  00000000`00000000
fffff880`089edd78  fffff880`089ede20
fffff880`089edd80  fffffa80`0972e000
fffff880`089edd88  fffff880`0f2b5da5 nvlddmkm+0x1ebda5
fffff880`089edd90  00000000`00000000
fffff880`089edd98  00000000`006100bc
fffff880`089edda0  00000000`00000000
fffff880`089edda8  fffff880`0f2b5da5 nvlddmkm+0x1ebda5
fffff880`089eddb0  00000000`00000000
fffff880`089eddb8  fffff880`089ede60
fffff880`089eddc0  fffffa80`0972e000
fffff880`089eddc8  fffff880`0f2b6152 nvlddmkm+0x1ec152
fffff880`089eddd0  00000000`00000000
fffff880`089eddd8  fffff880`0f2b5da5 nvlddmkm+0x1ebda5
fffff880`089edde0  00000000`006100bc
fffff880`089edde8  fffff880`0f295b14 nvlddmkm+0x1cbb14
fffff880`089eddf0  00000000`006100bc
fffff880`089eddf8  fffff880`0f2dcfd0 nvlddmkm+0x212fd0
fffff880`089ede00  00000000`00000000
fffff880`089ede08  fffff880`0f2b5da5 nvlddmkm+0x1ebda5
fffff880`089ede10  fffffa80`0972e000
fffff880`089ede18  fffff880`0f2b6152 nvlddmkm+0x1ec152
My System SpecsSystem Spec
21 May 2014   #20
ThatBenderGuy

Windows 7 Professional 64-bit
 
 

I apologize, I thought I rolled back my GPU driver but I must have accidentally updated it.

Well after I rolled it back I got another BSOD

https://onedrive.live.com/redir?resi...D4F258D1%21110

it looks like it might have something to do with audiodg.exe.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880048a2798, fffff8800a7c4e90, 0}

Probably caused by : ksthunk.sys ( ksthunk!CKernelFilterDevice::DispatchIrp+90 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880048a2798, Address of the instruction which caused the bugcheck
Arg3: fffff8800a7c4e90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
ksthunk!CKernelFilterDevice::DispatchIrp+90
fffff880`048a2798 ff5038          call    qword ptr [rax+38h]

CONTEXT:  fffff8800a7c4e90 -- (.cxr 0xfffff8800a7c4e90)
rax=92fff880048a4770 rbx=0000000000000001 rcx=fffffa800aff9180
rdx=fffffa800d505bd0 rsi=fffffa800aff9180 rdi=fffffa800d505bd0
rip=fffff880048a2798 rsp=fffff8800a7c5870 rbp=fffffa800d505fb8
 r8=0000000000000000  r9=fffff8800a7c58e0 r10=0000000000000028
r11=0000000000000006 r12=0000000000000003 r13=0000000000000001
r14=0000000000000000 r15=fffffa800b928b70
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
ksthunk!CKernelFilterDevice::DispatchIrp+0x90:
fffff880`048a2798 ff5038          call    qword ptr [rax+38h] ds:002b:92fff880`048a47a8=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033aee67 to fffff880048a2798

STACK_TEXT:  
fffff880`0a7c5870 fffff800`033aee67 : fffffa80`0a3f94d0 fffff880`0a7c5b60 fffffa80`00000000 fffffa80`0a3f94d0 : ksthunk!CKernelFilterDevice::DispatchIrp+0x90
fffff880`0a7c58d0 fffff800`033af6c6 : 00000000`0331f6a0 00000000`00000995 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0a7c5a00 fffff800`03090e53 : fffffa80`0dd14b50 00000000`0331f688 fffff880`0a7c5a88 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0a7c5a70 00000000`76ee132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0331f658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ee132a


FOLLOWUP_IP: 
ksthunk!CKernelFilterDevice::DispatchIrp+90
fffff880`048a2798 ff5038          call    qword ptr [rax+38h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ksthunk!CKernelFilterDevice::DispatchIrp+90

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ksthunk

IMAGE_NAME:  ksthunk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bca93

STACK_COMMAND:  .cxr 0xfffff8800a7c4e90 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_ksthunk!CKernelFilterDevice::DispatchIrp+90

BUCKET_ID:  X64_0x3B_ksthunk!CKernelFilterDevice::DispatchIrp+90

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

0: kd> lmvm ksthunk
start             end                 module name
fffff880`048a2000 fffff880`048a7200   ksthunk    (pdb symbols)          c:\symbols\ksthunk.pdb\A58068C2E5CB41E6B685D3866CA394141\ksthunk.pdb
    Loaded symbol image file: ksthunk.sys
    Image path: \SystemRoot\system32\drivers\ksthunk.sys
    Image name: ksthunk.sys
    Timestamp:        Mon Jul 13 17:00:19 2009 (4A5BCA93)
    CheckSum:         0000AF92
    ImageSize:        00005200
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
I'm updating my audio driver right now. I'll let you know if BSOD again



-----------------------------------------------------
EDIT
-----------------------------------------------------

Ok got another one this time it's for dxgmms1.sys

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff880043ac10e, fffff88004034558, fffff88004033db0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880043ac10e, The address that the exception occurred at
Arg3: fffff88004034558, Exception Record Address
Arg4: fffff88004033db0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86
fffff880`043ac10e 8b4810          mov     ecx,dword ptr [rax+10h]

EXCEPTION_RECORD:  fffff88004034558 -- (.exr 0xfffff88004034558)
ExceptionAddress: fffff880043ac10e (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x0000000000000086)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88004033db0 -- (.cxr 0xfffff88004033db0)
rax=c2fffa800b6c3990 rbx=fffff8a011f38010 rcx=fffff8a011f38010
rdx=0000000000000000 rsi=fffffa800d6cc2b0 rdi=fffffa800c7d2000
rip=fffff880043ac10e rsp=fffff88004034790 rbp=0000000000000000
 r8=fffffa800d6cc300  r9=0000000000000001 r10=0000000000000000
r11=fffffa800c7d33e8 r12=0000000000000038 r13=0000000000000000
r14=fffffa800a117140 r15=00000000000000d5
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x86:
fffff880`043ac10e 8b4810          mov     ecx,dword ptr [rax+10h] ds:002b:c2fffa80`0b6c39a0=????????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86
fffff880`043ac10e 8b4810          mov     ecx,dword ptr [rax+10h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880043a99d3 to fffff880043ac10e

STACK_TEXT:  
fffff880`04034790 fffff880`043a99d3 : 00000000`00000000 fffffa80`0a3231c0 00000000`000000d5 fffffa80`0daec548 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x86
fffff880`040347d0 fffff880`043c37d9 : 00000000`00000000 fffff8a0`05b04cc0 fffffa80`00000000 fffffa80`0a117140 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`040349a0 fffff880`043c3514 : fffff880`02fdbf40 fffff880`043c2f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04034b90 fffff880`043c3012 : 00000000`00000000 fffffa80`0dce8d50 00000000`00000080 fffffa80`0ae1b410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04034bc0 fffff800`0331b73a : 00000000`040b1e34 fffffa80`0b6c3b50 fffffa80`0970c990 fffffa80`0b6c3b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04034c00 fffff800`030708e6 : fffff880`02fd7180 fffffa80`0b6c3b50 fffff880`02fe1fc0 00000000`00000004 : nt!PspSystemThreadStartup+0x5a
fffff880`04034c40 00000000`00000000 : fffff880`04035000 fffff880`0402f000 fffff880`04034540 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

STACK_COMMAND:  .cxr 0xfffff88004033db0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86

Followup: MachineOwner
---------
The memory dump uploaded to my onedrive is still the previous one. Let me know if you want the memory dump from this BSOD
My System SpecsSystem Spec
Reply

 Frequent BSOD while playing League of Legends [ntoskrnl.exe]




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD while playing League of Legends?
During the last month I've had several bluescreens, I get them when I opened programs like Skype, Metal Gear Rising and now Rust. Would appreciate some help.
BSOD Help and Support
BSOD while playing League of Legends Only
Hi, I get a few BSOD each time I play League of Legends. This only happens when I play, if I don't do anything on my computer there are no BSOD.
BSOD Help and Support
BSOD playing League of Legends 0x0000001e dxgmms1.sys and ntoskrnl.exe
Hi i keep getting frequent blue screens whilst playing league of legends. I have downloaded blue screen viewer and tried to identify the issue as much as possible however i don't know how to fix it. I have attached all of the minidump files found within the folder.
BSOD Help and Support
BSOD and frequent crashes when playing League of legends game
Whenever i play this game i get frequent BSOD/Crashes with the prompt that the application has stopped working. I had problems with BSOD before but resolved them by changing the RAM sticks to the correct positions. I only recently started playing this game and i only get the crashes when...
BSOD Help and Support
BSOD while playing league of legends.
BSOD only while playing league of legends. attached are the minidumps specs: OS Name Microsoft Windows 7 Home Premium Version 6.1.7601 Service Pack 1 Build 7601 System Type x64-based PC Processor Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, 2001 Mhz, 4 Core(s), 8 Logical...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:12.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App