Sign in with
Sign up | Sign in
Your question
Solved

PC crashing with BSOD

Tags:
  • Blue Screen
  • Windows 7
Last response: in Windows 7
Share
June 9, 2013 9:00:47 PM

I was wondering if you guys could help. My brothers PC has been blue screening for some time now.

I have 2 dump logs, hopefully you can help. Ask if you need more.
I put them in spoilers to make space easier.
Spoiler

==================================================
Dump File : 060913-13384-01.dmp
Crash Time : 6/9/2013 10:27:38 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`18455010
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02d4aca6
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060913-13384-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,152
==================================================

Spoiler

==================================================
Dump File : 060913-12121-01.dmp
Crash Time : 6/9/2013 9:21:52 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffff880`069c6ba0
Parameter 3 : fffff880`069c6ba0
Parameter 4 : 00fff880`069c6ba0
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+b6bb4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060913-12121-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,152
==================================================

More about : crashing bsod

June 9, 2013 9:25:53 PM

I would guess a driver is wigging out. Update all drivers.
m
0
l
June 9, 2013 9:58:01 PM

All drivers are up to date. It's happened even when the drivers were just obtained from the manufactures websites.
m
0
l
Related resources

Best solution

June 9, 2013 11:10:44 PM

Oh...
Next thing I would try is stress testing the hardware. Prime95 or IntelBurnTest for CPU, MemTest86+ for RAM, Furmark for GPU if you have a discreet GPU. Probably start with MemTest86+.
Share
June 10, 2013 12:04:27 PM

Looks like it was one of the memory sticks. Idk what happened to it but one stick gets errors and the other doesn't. And I did test the sticks in both slots as in switched them. So just RMA the bad stick?
m
0
l
June 10, 2013 12:32:39 PM

Yep. I'm glad you found the issue.
m
0
l
!