I have some weird BSOD while i close the game, and today i experienced like a Network lg which I havent seen before while I have had this mobo
whocrashed has this BSOD on the dump files
What could I do?
whocrashed has this BSOD on the dump files
On Thu 24/07/2014 21:29:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072414-14757-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C9B5FE, 0xFFFFF880064CFE00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/07/2014 21:29:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cdd.dll (cdd+0xDCE0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C9B5FE, 0xFFFFF880064CFE00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 20/07/2014 18:18:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072014-19656-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000186483, 0xFFFFF88005CEA030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 14/07/2014 15:19:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071414-17628-01.dmp
This was probably caused by the following module: cdd.dll (0xFFFFF960007CDC51)
Bugcheck code: 0x50 (0xFFFFF900C00BF7A0, 0x0, 0xFFFFF960007CDC51, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 12/07/2014 23:03:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071214-17394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C405FE, 0xFFFFF88008193E00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 11/07/2014 16:34:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071114-17752-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002C260D)
Bugcheck code: 0x50 (0xFFFFF900C2B41CF0, 0x0, 0xFFFFF960002C260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
crash dump file: C:\Windows\Minidump\072414-14757-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C9B5FE, 0xFFFFF880064CFE00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 24/07/2014 21:29:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cdd.dll (cdd+0xDCE0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C9B5FE, 0xFFFFF880064CFE00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 20/07/2014 18:18:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072014-19656-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000186483, 0xFFFFF88005CEA030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 14/07/2014 15:19:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071414-17628-01.dmp
This was probably caused by the following module: cdd.dll (0xFFFFF960007CDC51)
Bugcheck code: 0x50 (0xFFFFF900C00BF7A0, 0x0, 0xFFFFF960007CDC51, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 12/07/2014 23:03:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071214-17394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C405FE, 0xFFFFF88008193E00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 11/07/2014 16:34:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071114-17752-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002C260D)
Bugcheck code: 0x50 (0xFFFFF900C2B41CF0, 0x0, 0xFFFFF960002C260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
What could I do?