BSOD sometimes random, sometimes while playing league of legends

[nuwc]

Hi all

I've been getting random BSODs, even after a fresh install on a brand new hard drive (SSD). I have attached the minidump that was created around 4 days ago.

Could someone point out what the problem is?...Thank you very much!

 

[koolkat77]

Welcome to Seven Forums.

Update the drivers below to their latest.

cmudaxp.sys                 Tue Jun  9 17:32:36 2009

C-Media Audio Interface Driver (WDM) by C-Media [br] ASUS Xonar DG Audio Interface driver [br] HTO CLARO Audio Interface Driver
Driver Reference Table - cmudaxp.sys

LGPBTDD.sys                 Thu Jul  2 00:47:52 2009

Logitech GamePanel Software
Driver Reference Table - LGPBTDD.sys

nusb3xhc.sys                Fri Dec 10 10:50:35 2010

NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3xhc.sys

nusb3hub.sys                Fri Dec 10 10:50:35 2010

NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3hub.sys
------------------------
To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8e22, 2, 1, fffff880071d63fe}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: 0000000000008e22, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880071d63fe, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d06100
GetUlongFromAddress: unable to read from fffff80002d061c0
 0000000000008e22 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
bowser!BowserTdiReceiveDatagramHandler+ea
fffff880`071d63fe 668390028e000000 adc     word ptr [rax+8E02h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800a03a2d0 -- (.trap 0xfffff8800a03a2d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000020 rbx=0000000000000000 rcx=fffff8800a03a5c0
rdx=000000000000002c rsi=0000000000000000 rdi=0000000000000000
rip=fffff880071d63fe rsp=fffff8800a03a460 rbp=00000000c000021b
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002c4a880
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
bowser!BowserTdiReceiveDatagramHandler+0xea:
fffff880`071d63fe 668390028e000000 adc     word ptr [rax+8E02h],0 ds:00000000`00008e22=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ace129 to fffff80002aceb80

STACK_TEXT:  
fffff880`0a03a188 fffff800`02ace129 : 00000000`0000000a 00000000`00008e22 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a03a190 fffff800`02accda0 : fffff880`0a03a4b8 fffff880`0181b9b4 00000000`00000000 fffffa80`078ea4c0 : nt!KiBugCheckDispatch+0x69
fffff880`0a03a2d0 fffff880`071d63fe : 00000000`00000000 fffff800`02c74a28 00000000`00000002 fffff880`00000100 : nt!KiPageFault+0x260
fffff880`0a03a460 fffff880`02d3646a : fffffa80`084cf7b0 fffffa80`084cf010 00000000`c000021b 00000000`00000052 : bowser!BowserTdiReceiveDatagramHandler+0xea
fffff880`0a03a550 fffff880`02d312d2 : fffffa80`089b3080 00000000`00000000 00000000`00000000 fffff880`00dc9400 : netbt!DgramHndlrNotOs+0x3bb
fffff880`0a03a6b0 fffff880`00daf325 : fffffa80`089b3080 fffffa80`089b3080 fffff880`0a03a9e8 fffffa80`0881d8c0 : netbt!TdiRcvDatagramHandler+0xe4
fffff880`0a03a780 fffff880`018834c5 : fffffa80`0881d8c0 00000000`00000000 fffffa80`0881d8c0 fffffa80`0881d8c0 : tdx!TdxEventReceiveMessagesTransportAddress+0x315
fffff880`0a03a970 fffff880`0187dbe2 : fffffa80`00000000 fffffa80`0881d8c0 00000000`00000000 fffff880`05e99a22 : tcpip!UdpDeliverDatagrams+0x155
fffff880`0a03ab00 fffff880`01859d27 : fffffa80`07429880 fffffa80`077d4100 00000000`00000020 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x332
fffff880`0a03ac10 fffff880`0185983a : 00000000`00000000 fffff880`0196e9a0 fffff880`0a03add0 fffffa80`1a24cd3e : tcpip!IppDeliverListToProtocol+0xf7
fffff880`0a03acd0 fffff880`01858e39 : fffff880`0196e9a0 fffffa80`0796eba0 00000000`00000011 fffff880`0a03adc0 : tcpip!IppProcessDeliverList+0x5a
fffff880`0a03ad70 fffff880`01856adf : 00000000`ff00a8c0 fffff880`0196e9a0 fffff880`0196e9a0 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`0a03ae50 fffff880`018560b2 : fffffa80`0773f880 00000000`00000000 fffffa80`07d51b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`0a03b050 fffff880`018554da : fffffa80`07d51ba0 fffff880`0a03b180 fffffa80`07d51ba0 00000000`078d0000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`0a03b130 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !bowser
    fffff880071d6400-fffff880071d6401  2 bytes - bowser!BowserTdiReceiveDatagramHandler+ec
	[ bc 24:90 02 ]
2 errors : !bowser (fffff880071d6400-fffff880071d6401)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

 

[nuwc]

Thank you very much for responding so quickly! I will try these methods and will let you know how it goes.