Overclock.net banner

Some ramdon crashes after closing a game

310 views 11 replies 3 participants last post by  PontiacGTX 
#1 ·
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
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.

What could I do?
 
#6 ·
Quote:
Originally Posted by PontiacGTX View Post

@eXXon
Ran memtest and the 240 interations it ran,passed

What else can be the 0x3b?maybe a damaged imc?
Actually, it usually means low vcore according to this:

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

Source
 
#10 ·
Quote:
On Mon 04/08/2014 17:27:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080414-15241-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000C6483, 0xFFFFF88005955030, 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 Fri 01/08/2014 14:41:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080114-14695-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116483, 0xFFFFF8800671B030, 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
After closing BF3 and BF4...(alt+F4)
i guess that my IMC is damaged
 
#11 ·
Or, or, other possibility:
While you did quote my advice above; you did not apply it. Your RAM may claim it can run at that speed but it doesn't change the fact that it is above spec. You can't claim something else is damaged (the IMC) when you are running it on "Auto", relying on some mobo microcode to determine your timings rather than setting them to the appropriate stock values.

First drop your RAM speed (the multiplier) all you can. If that works, you'll be happy enough (overclocked RAM doesn't help much) and we also know that is the problem.

It is possible you may still be able to use the quoted RAM speed though if you read the timing (may be under advanced settings in your mobo) that have to be used with said 2133Mhz and manually set them.

Good luck.

EDIT:
My fault for forgetting the context of this thread before replied:
Actually, that particular code can be caused by the graphics driver (I won't go into the details unless you care). Given that the problem seems directly linked to a driver transition (you are hard closing a game) this seems most likely. Do a clean install of your graphics driver, the standard sweep etc. Try old versions, etc. You know the drill.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top