Blue screen of death help

Jovie Biig

Reputable
Jun 28, 2014
9
0
4,510
Help me guys i have a Blue screen of death while exiting the dota 2 application.the blue screen is Kernel mode exeption cant handle
specs
i3 3240
4 gb ram
2 gb radeon hd 6450
pls help me
tnx
 

Andrew Buck

Honorable


Not sure why, but these have popped up a lot lately. Try running a virus scan and open CMD and do sfc /scannow.
 

Jovie Biig

Reputable
Jun 28, 2014
9
0
4,510
crash dump file: C:\Windows\Minidump\062914-27565-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9942BD01, 0xFFFFFFFF9A06BB98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 a kernel-mode program generated an exception which the error handler did not catch.
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 6/29/2014 5:49:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF9942BD01, 0xFFFFFFFF9A06BB98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED



On Sun 6/29/2014 3:23:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062814-26722-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBBD01)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8217BD01, 0xFFFFFFFF99C4FB98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 a kernel-mode program generated an exception which the error handler did not catch.
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 Thu 6/26/2014 5:01:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062514-31949-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB768)
Bugcheck code: 0x50 (0xFFFFFFFFFDCA05DC, 0x0, 0xFFFFFFFF98B7B768, 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.
this what i got
 

Crazy_Ivan55

Distinguished
Apr 15, 2011
95
0
18,660
I used to have errors and after many hours of research I figured out that it could be my RAM. So I did memtest which is something you burn onto a CD and run it through the bios and came up with many memory errors. So in my case it was faulty memory and new RAM fixed it. I don't recommend you do this first because it was a last ditch thing for me but I just wanted to say it so you are informed that it could potentially be faulty RAM.

The error i was getting was page fault in nonpaged area for the most part.
 

Jovie Biig

Reputable
Jun 28, 2014
9
0
4,510
this is the dump file
070414-25818-01.dmp
7/4/2014 2:38:59 PM
KERNEL_MODE_EXCEPTION_NOT_HANDLED
0x1000008e
0xc0000005
0x98bdbd01
0x99a97b98
0x00000000
win32k.sys
win32k.sys+bbd01
Multi-User Win32 Driver
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7600.16385 (win7_rtm.090713-1255)
32-bit
win32k.sys+bbd01
win32k.sys+bd47f
win32k.sys+6cc47
win32k.sys+bf520
 

Jovie Biig

Reputable
Jun 28, 2014
9
0
4,510
070414-22573-01.dmp
7/4/2014 1:25:00 PM
PAGE_FAULT_IN_NONPAGED_AREA
0x10000050
0xffb885dc
0x00000000
0x9884b768
0x9884b768
cdd.dll
cdd.dll+1753
Canonical Display Driver
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7600.16385 (win7_rtm.090713-1255)
32-bit
cdd.dll+b768
cdd.dll+1753
win32k.sys+cd304
win32k.sys+ce718