Periodic Blue Screens

joebro865

Reputable
Feb 13, 2015
50
0
4,640
I am having trouble with BSOD's they happen about once a week, but I recently installed a new graphics card and I think they might be happening more frequently ever since HL2 refuses to work and I am ecxperiencing other problems.
Usually when I game, sometimes heavy browsing.
I have some who-crash reports but other than that I am completely in the dark about to fix it. I might be dealing with two kinds of blue screens
I couldn't save the more recent BSOD's so this information might be old
----------------------------
PC:
----------------------------
MOBO ASUS M5A97 R2.0
CPU: AMD FX-4350 Black edition
GPU: Nvidia Was 750 now 960
Ram: Balistix Sport 2-4GB DDR3-1600 CL9 @1.5
SSD Samsung 840 EVO
500GB HDD

------------------------------------------------
Whocrash's (from more to less recent)
------------------------------------------------

n Sat 5/23/2015 6:45:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052315-10608-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0xFFFFF10005ECC500, 0x2, 0x1, 0xFFFFF80002EDBE62)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 5/23/2015 6:45:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC5AB7)
Bugcheck code: 0xA (0xFFFFF10005ECC500, 0x2, 0x1, 0xFFFFF80002EDBE62)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.