Various BSOD

I'm getting some BSODs . Most of them while i play Pro evolution Soccer 2012 (online). They seem related to my new VGA card wich i bought few weeks ago, but i have to be sure ( shame on you nVidia, you used to make stable drivers).Since i got now 2 BSODs in the same day i decided to seel help and come here. 1 was when i shut down my computer & the other in PES2012. there are 2 or 3 more older dumps there, most of them while in PES2012 if i remember well.

I'm on:
- Windows 7 Home Premium x64 full retail version
- Most of my hardware is bought last year in june exept the HDD drives wich are older and the VGA card wich i just bought 2 weeks ago
- 2 weeks, when i bought my new VGA card : 560GTX

Its not really Nvidia's fault but a lot of users have reported certain issues with the GTX560Ti series cards.

Update your Nvidia Driver NVIDIA DRIVERS 285.62 WHQL
Test it with OCCT
https://www.sevenforums.com/tutorials...test-occt.html

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffff8521f2d5, 9, 0, fffff880130c33c8}

Unable 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+773c8 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffffff8521f2d5, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880130c33c8, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fa100
 ffffffff8521f2d5 

CURRENT_IRQL:  9

FAULTING_IP: 
nvlddmkm+773c8
fffff880`130c33c8 33d2            xor     edx,edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  pes2012.exe

TRAP_FRAME:  fffff880009b02f0 -- (.trap 0xfffff880009b02f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000017ede rbx=0000000000000000 rcx=fffffa80041b8200
rdx=0000000000017ede rsi=0000000000000000 rdi=0000000000000000
rip=fffff880130c33c8 rsp=fffff880009b0480 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff8801383d5b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0x773c8:
fffff880`130c33c8 33d2            xor     edx,edx
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032c71e9 to fffff800032c7c40

STACK_TEXT:  
fffff880`009b01a8 fffff800`032c71e9 : 00000000`0000000a ffffffff`8521f2d5 00000000`00000009 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b01b0 fffff800`032c5e60 : 3c81a000`00000000 bd44e700`c44d505b 00000000`00000041 fffff880`13c6f200 : nt!KiBugCheckDispatch+0x69
fffff880`009b02f0 fffff880`130c33c8 : fffffa80`07b124a0 fffff880`009b0868 fffffa80`04db0000 fffffa80`046d9450 : nt!KiPageFault+0x260
fffff880`009b0480 fffffa80`07b124a0 : fffff880`009b0868 fffffa80`04db0000 fffffa80`046d9450 00000000`00000000 : nvlddmkm+0x773c8
fffff880`009b0488 fffff880`009b0868 : fffffa80`04db0000 fffffa80`046d9450 00000000`00000000 fffff880`1312f624 : 0xfffffa80`07b124a0
fffff880`009b0490 fffffa80`04db0000 : fffffa80`046d9450 00000000`00000000 fffff880`1312f624 00000000`00000001 : 0xfffff880`009b0868
fffff880`009b0498 fffffa80`046d9450 : 00000000`00000000 fffff880`1312f624 00000000`00000001 fffffa80`00000000 : 0xfffffa80`04db0000
fffff880`009b04a0 00000000`00000000 : fffff880`1312f624 00000000`00000001 fffffa80`00000000 00000000`00000000 : 0xfffffa80`046d9450


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+773c8
fffff880`130c33c8 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+773c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d866a30

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+773c8

BUCKET_ID:  X64_0xD1_nvlddmkm+773c8

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffffff8521f2d5, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880130c33c8, address which referenced memory

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


READ_ADDRESS:  ffffffff8521f2d5 

CURRENT_IRQL:  9

FAULTING_IP: 
nvlddmkm+773c8
fffff880`130c33c8 33d2            xor     edx,edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  pes2012.exe

TRAP_FRAME:  fffff880009b02f0 -- (.trap 0xfffff880009b02f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000017ede rbx=0000000000000000 rcx=fffffa80041b8200
rdx=0000000000017ede rsi=0000000000000000 rdi=0000000000000000
rip=fffff880130c33c8 rsp=fffff880009b0480 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff8801383d5b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0x773c8:
fffff880`130c33c8 33d2            xor     edx,edx
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032c71e9 to fffff800032c7c40

STACK_TEXT:  
fffff880`009b01a8 fffff800`032c71e9 : 00000000`0000000a ffffffff`8521f2d5 00000000`00000009 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b01b0 fffff800`032c5e60 : 3c81a000`00000000 bd44e700`c44d505b 00000000`00000041 fffff880`13c6f200 : nt!KiBugCheckDispatch+0x69
fffff880`009b02f0 fffff880`130c33c8 : fffffa80`07b124a0 fffff880`009b0868 fffffa80`04db0000 fffffa80`046d9450 : nt!KiPageFault+0x260
fffff880`009b0480 fffffa80`07b124a0 : fffff880`009b0868 fffffa80`04db0000 fffffa80`046d9450 00000000`00000000 : nvlddmkm+0x773c8
fffff880`009b0488 fffff880`009b0868 : fffffa80`04db0000 fffffa80`046d9450 00000000`00000000 fffff880`1312f624 : 0xfffffa80`07b124a0
fffff880`009b0490 fffffa80`04db0000 : fffffa80`046d9450 00000000`00000000 fffff880`1312f624 00000000`00000001 : 0xfffff880`009b0868
fffff880`009b0498 fffffa80`046d9450 : 00000000`00000000 fffff880`1312f624 00000000`00000001 fffffa80`00000000 : 0xfffffa80`04db0000
fffff880`009b04a0 00000000`00000000 : fffff880`1312f624 00000000`00000001 fffffa80`00000000 00000000`00000000 : 0xfffffa80`046d9450


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+773c8
fffff880`130c33c8 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+773c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d866a30

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+773c8

BUCKET_ID:  X64_0xD1_nvlddmkm+773c8

can't understand how OCCT works or it doesn't work for me. i hit ON at GPU test window, another window pops up but it's all black and shows some statitic about FPS, error but after it dissapear and GPU doesn't seem stressed at all

apoklyps3 said:

can't understand how OCCT works or it doesn't work for me. i hit ON at GPU test window, another window pops up but it's all black and shows some statitic about FPS, error but after it dissapear and GPU doesn't seem stressed at all

Your should have the latest DirectX9 components before using OCCT
Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details

of course i have it. how else would i be able to play battlefield and pes2012?? just to be sure i reinstalled it. it's the same, the window that pops up is all black and it stays stable at 13.8 FPS, don't know what's counting though, nothing on the window & GPU use is next to 0

apoklyps3 said:

of course i have it. how else would i be able to play battlefield and pes2012?? just to be sure i reinstalled it. it's the same, the window that pops up is all black and it stays stable at 13.8 FPS, don't know what's counting though, nothing on the window & GPU use is next to 0

This should not be occurring unless a theres a problem with your graphics card

after almost a week without BSOD it happened again while i was browsing the web and chatting on MSN. here's the new dump generated by windows. what's this one about?

This one blames the Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver
Update it Realtek

Code:

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  wlcomm.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba2458 -- (.exr 0xfffff80000ba2458)
ExceptionAddress: fffff880015467c1 (ndis!ndisParseReceivedNBL+0x0000000000000081)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba2500 -- (.trap 0xfffff80000ba2500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005132d30
rdx=bffff88002e74000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015467c1 rsp=fffff80000ba2690 rbp=0000000000000000
 r8=0000000000000600  r9=fffff80000ba2760 r10=0000000000000000
r11=fffff80000ba2758 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ndis!ndisParseReceivedNBL+0x81:
fffff880`015467c1 0fb64a0c        movzx   ecx,byte ptr [rdx+0Ch] ds:4ce0:bffff880`02e7400c=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032c95fe to fffff800032d1c10

STACK_TEXT:  
fffff800`00ba1538 fffff800`032c95fe : 00000000`00000000 fffffa80`064d8080 fffff800`00ba1cb0 fffff800`032fd830 : nt!KeBugCheck
fffff800`00ba1540 fffff800`032fd4fd : fffff800`034db71c fffff800`03418c30 fffff800`03255000 fffff800`00ba2458 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1570 fffff800`032fc2d5 : fffff800`0341c028 fffff800`00ba15e8 fffff800`00ba2458 fffff800`03255000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba15a0 fffff800`0330d361 : fffff800`00ba2458 fffff800`00ba1cb0 fffff800`00000000 00000000`000005c8 : nt!RtlDispatchException+0x415
fffff800`00ba1c80 fffff800`032d12c2 : fffff800`00ba2458 fffff800`00ba2700 fffff800`00ba2500 00000000`000005c8 : nt!KiDispatchException+0x135
fffff800`00ba2320 fffff800`032cfbca : ffff0080`013c15f3 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00ba2500 fffff880`015467c1 : 00000000`00000002 fffffa80`0588b400 fffffa80`045fa640 fffff880`0615dc93 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2690 fffff880`01546592 : fffffa80`05130000 fffff800`00ba27e0 fffffa80`05132800 00000000`00000000 : ndis!ndisParseReceivedNBL+0x81
fffff800`00ba26e0 fffff880`015469c5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisSortNetBufferLists+0xc2
fffff800`00ba2760 fffff880`014bfcc1 : fffffa80`04f471a0 00000000`00000002 00000000`00000002 00000000`00000001 : ndis!ndisMDispatchReceiveNetBufferLists+0xc5
fffff800`00ba2be0 fffff880`042e6f66 : fffffa80`050cb000 00000000`00000001 00000000`00000001 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff800`00ba2c30 fffffa80`050cb000 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : Rt64win7+0x15f66
fffff800`00ba2c38 00000000`00000001 : 00000000`00000001 00000000`00000000 00000000`00000001 fffffa80`04372af0 : 0xfffffa80`050cb000
fffff800`00ba2c40 00000000`00000001 : 00000000`00000000 00000000`00000001 fffffa80`04372af0 fffffa80`00000002 : 0x1
fffff800`00ba2c48 00000000`00000000 : 00000000`00000001 fffffa80`04372af0 fffffa80`00000002 fffffa80`00000001 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+15f66
fffff880`042e6f66 ??              ???

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  Rt64win7+15f66

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b8fb8dc

FAILURE_BUCKET_ID:  X64_0x1E_Rt64win7+15f66

BUCKET_ID:  X64_0x1E_Rt64win7+15f66

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

thanks man. wlcomm.exe is related to Windows live messenger. now come to think about it all bsods happen while using the internet somehow: PES2012 online gaming , WL messenger... i will try to play alot of offline Battlefield 3 to see if i get any BSOD, to rule out the VGA.