New
#1
Hi, firstly I'm new to pc and don't have much knowledge about it, I apologize for that.
I have no idea what is going to my desktop, it keep on blue screen when I play a long time on battlefield 4, sometimes close browser while on battlefield 4. I have already change a new stick of ram, I install anti malware to check, and avast anti virus. This problem has been going on for about 2 months, almost everyday I am facing this blue screen. Sometime it even happen 3 times per day. I'm really have no idea what to do anymore. Help me please.Dmp file in the attachment. This is the latest blue screen code I've got from blue screen viewer.
032514-12651-01.dmp
3/25/2014 2:53:31 AM
SYSTEM_SERVICE_EXCEPTION
0x0000003b
00000000`c0000005
fffff800`02e9601e
fffff880`07811de0
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+71f00
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7600.16385 (win7_rtm.090713-1255)
x64
ntoskrnl.exe+71f00
Code:Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 3/24/2014 6:53:31 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\032514-12651-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E9601E, 0xFFFFF88007811DE0, 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 Mon 3/24/2014 6:53:31 PM 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, 0xFFFFF80002E9601E, 0xFFFFF88007811DE0, 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 Mon 3/24/2014 8:43:19 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\032414-15038-01.dmp This was probably caused by the following module: win32k.sys (0xFFFFF9600030C69D) Bugcheck code: 0x50 (0xFFFFF900C2A12030, 0x0, 0xFFFFF9600030C69D, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 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 3/22/2014 12:52:43 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\032214-11029-01.dmp This was probably caused by the following module: cdd.dll (0xFFFFF9600077DCD0) Bugcheck code: 0x50 (0xFFFFF900C00DA4B8, 0x0, 0xFFFFF9600077DCD0, 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 Fri 3/21/2014 1:38:40 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\032114-10186-01.dmp This was probably caused by the following module: cdd.dll (cdd+0x6CF9) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960007C6CF9, 0xFFFFF880091670D0, 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 Fri 3/21/2014 11:38:20 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\032114-11216-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CA201E, 0xFFFFF8800BD66DE0, 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 3/20/2014 6:53:38 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\032114-15475-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xC4283) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000194283, 0xFFFFF8800867E020, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 7 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Last edited by Brink; 24 Mar 2014 at 15:14. Reason: merged
Quote