I need some smart people to help me out :P (Asus G60JX)

Mk i bought my Asus G60jx back in August 2010. It has been great for the most part. But recently i have been experiencing blue screens. And i just cannot figure out why. And the Asus support really isn't helping me too much at all. I've read through the Asus G60 and G51 sections on here, doesn't really help me much.

Here are some specs.
Asus G60JX
Intel i5 430m 2.27 GHZ w/ 2.53 Turbo boost
4GB DDR3 RAM
NVIDIA GTS 360m GDDR5 RAM
Windows 7 Home Premium 64 bit

The bluescreens are random, there is nothing consistent about what i'm doing when they happen and nothing consistent about how often they happen. I can be playing a game, browsing the internet, or just having it idle on the desktop. So i really don't know what to do. I monitor my temps constantly with HWMonitor and sometimes i use GPU-Z. Never have my temps been out of line for the G60JX's standard.

Here are the BSOD reports


==================================================
Dump File : 051111-51620-01.dmp
Crash Time : 5/11/2011 2:59:57 AM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00001097
Parameter 3 : 00000000`09060012
Parameter 4 : fffffa80`03cd0bb0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051111-51620-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================


==================================================
Dump File : 050911-48219-01.dmp
Crash Time : 5/9/2011 8:06:42 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`033fb617
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\050911-48219-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================

==================================================
Dump File : 042811-44132-01.dmp
Crash Time : 4/28/2011 1:57:52 AM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`03408617
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\042811-44132-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================

==================================================
Dump File : 042311-58188-01.dmp
Crash Time : 4/23/2011 3:03:25 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`033b0617
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\042311-58188-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================



I'm not 100% sure but i think i started having the issues once i "upgraded" to BIOS 208. After the most recent BSOD i rolled back to 207. So now i just have to wait and see if i end up having any issues. It's just so hard to tell since they can be 2 weeks apart, or 2 days, but i guess if i no longer BSOD then problem solved.

I've updated my drivers from the Asus website. After this issue started happening, no luck. (However I'm pretty sure they are all way outdated....) Aside from my NVIDIA driver which i just get from the NVIDIA website.

I guess i'm just looking for opinions as to what the heck is going on. I don't know much about blue screens at all.

What do these blue screens mean? Can the BIOS cause driver issues? Could rolling back to 207 solve my issue?..

Do you guys need any more information?

Please help! I've done a bunch of research on the topic and just cannot find an answer!

 

Run memtest86+ through a few passes.

It could be a bad graphics driver but it'd be best to rule out bad RAM before you get into driver whack-a-mole.

 

There is a nice, long, exhaustive thread in the owners forum about this (though, I think it might be here too...) under the g51j/jx.

There is a beta bios that fixes the problem.

 

I don't think this is the same as 0x124, none of the stop codes above match that.

This is almost definitely either bad RAM or a driver issue, unless the GPU has itself gone bad.

The creative drivers and stock razer drivers were known to cause BSODs but I don't recall the stop codes.

 

Soooo.... How do i got about running memtest86

 

Put it on a USB stick or burn a CD: Memtest86+ - Advanced Memory Diagnostic Tool

 

I did memtest. No errors at all.

Looks like we are going to be playing "driver whack-a-mole"

How do we got about finding bad drivers?....

Also, could rolling back to BIOS 207 have solved my problem?...It's really quite hard to tell since the BSOD's are so random.

 

How long did you let memtest86 run? For the most part an overnight run is the best to be 100% of no errors.

Also, if you like, there is a in-windows ram test program. Which has worked pretty solid for me, since I started using it.

MemTest for Windows Download Page

 

For drivers I would start with trying to fully remove and reinstall the nvidia driver package.

Also, make sure your temps aren't out of control. If your CPU or GPU temps are really high it could cause weird problems like this.

 

I ALWAYS monitor my temps just incase something spikes up for some reason. It's not temps.

My CPU idles in the mid to high 30's and GPU idles in low 40's

During high end Gaming (Games like Starcraft2) my CPU maxes at 66 but it usually averages lower. and my GPU maxes at 85 and also averages lower. From what i've read, the temps i've listed are by no means out of line for an G60JX, or any of the ASUS brand space heaters.

The blue screens happen at random times. I can just be browsing the internet and ...BAM...blue screen. Or i can be gaming, i don't recall ever crashing while in a game, but idk if that matters at all...There is no apparent patterns from what i've noticed...And they are so spaced out, sometimes weeks apart.

By fully remove the package...can i just reinstall it? Or do i have to take another step to completely remove all files and then go and reinstall? I'm not quite sure how to safely do that. Do i just go into device manager and just remove the driver completely?...Or would that cause me to not have a screen when i boot up...?

I've tried reinstalling the NVIDIA drivers a few different times, most of the time by upgrading to new drivers. Most recently i just plain reinstalled it. However i've never deleted everything.

Sorry for being such a noob :/. Still not sure about the answer though

 

I'd like to see the minidump files that go with those BSODs. Seeing the call stack would be nice. All those errors are related...

 

Want me to upload them? There a way to do that on this site?

This help with any troubleshooting? Pulled this out of the !analyze section from WinDbg


5/11/11

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff8000320c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

POOL_ADDRESS: fffffa8003cd0bb0

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800033b6be9 to fffff8000328c640

STACK_TEXT:
fffff880`09dcd7a8 fffff800`033b6be9 : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`09060012 : nt+0x80640
fffff880`09dcd7b0 00000000`000000c2 : 00000000`00000007 00000000`00001097 00000000`09060012 fffffa80`03cd0bb0 : nt+0x1aabe9
fffff880`09dcd7b8 00000000`00000007 : 00000000`00001097 00000000`09060012 fffffa80`03cd0bb0 fffffa80`0a996c68 : 0xc2
fffff880`09dcd7c0 00000000`00001097 : 00000000`09060012 fffffa80`03cd0bb0 fffffa80`0a996c68 00000000`00000000 : 0x7
fffff880`09dcd7c8 00000000`09060012 : fffffa80`03cd0bb0 fffffa80`0a996c68 00000000`00000000 fffff800`034136c8 : 0x1097
fffff880`09dcd7d0 fffffa80`03cd0bb0 : fffffa80`0a996c68 00000000`00000000 fffff800`034136c8 00000000`00000002 : 0x9060012
fffff880`09dcd7d8 fffffa80`0a996c68 : 00000000`00000000 fffff800`034136c8 00000000`00000002 fffffa80`039d1710 : 0xfffffa80`03cd0bb0
fffff880`09dcd7e0 00000000`00000000 : fffff800`034136c8 00000000`00000002 fffffa80`039d1710 fffffa80`039d1710 : 0xfffffa80`0a996c68


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+80640
fffff800`0328c640 48894c2408 mov qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+80640

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


5/9/11

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80003250000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 0

FAULTING_IP:
nt+1ab617
fffff800`033fb617 48895808 mov qword ptr [rax+8],rbx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

LAST_CONTROL_TRANSFER: from fffff800032cfbe9 to fffff800032d0640

STACK_TEXT:
fffff880`096ff3f8 fffff800`032cfbe9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt+0x80640
fffff880`096ff400 00000000`0000000a : 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`033fb617 : nt+0x7fbe9
fffff880`096ff408 00000000`00000008 : 00000000`00000002 00000000`00000001 fffff800`033fb617 fffffa80`10f71030 : 0xa
fffff880`096ff410 00000000`00000002 : 00000000`00000001 fffff800`033fb617 fffffa80`10f71030 00000000`00000000 : 0x8
fffff880`096ff418 00000000`00000001 : fffff800`033fb617 fffffa80`10f71030 00000000`00000000 00000000`00000000 : 0x2
fffff880`096ff420 fffff800`033fb617 : fffffa80`10f71030 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`096ff428 fffffa80`10f71030 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x1ab617
fffff880`096ff430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`10f71030


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+1ab617
fffff800`033fb617 48895808 mov qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: nt+1ab617

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


4/28/11

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff8000325d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 0

FAULTING_IP:
nt+1ab617
fffff800`03408617 48895808 mov qword ptr [rax+8],rbx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

LAST_CONTROL_TRANSFER: from fffff800032dcbe9 to fffff800032dd640

STACK_TEXT:
fffff880`0759c8b8 fffff800`032dcbe9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt+0x80640
fffff880`0759c8c0 00000000`0000000a : 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`03408617 : nt+0x7fbe9
fffff880`0759c8c8 00000000`00000008 : 00000000`00000002 00000000`00000001 fffff800`03408617 fffff880`0759c8e0 : 0xa
fffff880`0759c8d0 00000000`00000002 : 00000000`00000001 fffff800`03408617 fffff880`0759c8e0 00000000`00000000 : 0x8
fffff880`0759c8d8 00000000`00000001 : fffff800`03408617 fffff880`0759c8e0 00000000`00000000 00000000`00000000 : 0x2
fffff880`0759c8e0 fffff800`03408617 : fffff880`0759c8e0 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0759c8e8 fffff880`0759c8e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x1ab617
fffff880`0759c8f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0759c8e0


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+1ab617
fffff800`03408617 48895808 mov qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: nt+1ab617

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

4/23/11

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80003205000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 0

FAULTING_IP:
nt+1ab617
fffff800`033b0617 48895808 mov qword ptr [rax+8],rbx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

LAST_CONTROL_TRANSFER: from fffff80003284be9 to fffff80003285640

STACK_TEXT:
fffff880`08855fa8 fffff800`03284be9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt+0x80640
fffff880`08855fb0 00000000`0000000a : 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`033b0617 : nt+0x7fbe9
fffff880`08855fb8 00000000`00000008 : 00000000`00000002 00000000`00000001 fffff800`033b0617 fffff880`08856150 : 0xa
fffff880`08855fc0 00000000`00000002 : 00000000`00000001 fffff800`033b0617 fffff880`08856150 a31d1866`54d97663 : 0x8
fffff880`08855fc8 00000000`00000001 : fffff800`033b0617 fffff880`08856150 a31d1866`54d97663 1a00250c`efd1d61c : 0x2
fffff880`08855fd0 fffff800`033b0617 : fffff880`08856150 a31d1866`54d97663 1a00250c`efd1d61c 0fde1f59`fcbb717d : 0x1
fffff880`08855fd8 fffff880`08856150 : a31d1866`54d97663 1a00250c`efd1d61c 0fde1f59`fcbb717d 5cf312a5`b0e25b4a : nt+0x1ab617
fffff880`08855fe0 a31d1866`54d97663 : 1a00250c`efd1d61c 0fde1f59`fcbb717d 5cf312a5`b0e25b4a 00000000`00000000 : 0xfffff880`08856150
fffff880`08855fe8 1a00250c`efd1d61c : 0fde1f59`fcbb717d 5cf312a5`b0e25b4a 00000000`00000000 00000000`00000000 : 0xa31d1866`54d97663
fffff880`08855ff0 0fde1f59`fcbb717d : 5cf312a5`b0e25b4a 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1a00250c`efd1d61c
fffff880`08855ff8 5cf312a5`b0e25b4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfde1f59`fcbb717d
fffff880`08856000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5cf312a5`b0e25b4a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+1ab617
fffff800`033b0617 48895808 mov qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: nt+1ab617

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

 

Yeah i'm pretty sure you guys are my only help...I've been emailing them it takes about 2 days for them to shell out a whopping, unhelpful One sentence response.

Asus support is as dumb as a box of rocks.. Anyway is there anything else i can provide to help you guys out with figuring this out? I appreciate your time!

 

Another blue screen.... This one happened while my laptop was in standby/sleep mode. I figured it out when I turned my computer back on and it said it recovered from a crash

Does anyone know what the hell is going on? I'm guessing a driver is causing the issue. How do i find the bad one?

==================================================
Dump File : 051711-43103-01.dmp
Crash Time : 5/17/2011 1:27:50 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x1000009f
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000258
Parameter 3 : fffffa80`03564040
Parameter 4 : fffff800`00b9c510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+824da
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051711-43103-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 471,952
==================================================

I'll take that as a no :/

 

Maybe get BlueScreenView to view the minidumps so we can see the stack trace in human-readable format...

 

I thought i was posting the bluescreeviews? That's the program i've been using.

What else should i do with the program? I've just been saving them as text documents and posting them here.

 

All I see is a bunch of hexadecimal numbers, unless I missed something. bluescreenview shows the filenames of the driver modules involved

 

Mk i must not be doing it right then?

How do i get the information you need out of bluescreenview?

I open up the program
File>save selected items

Then i name the file, open it up in notepad, and post it here.

Where am i going wrong?

 

I'm currently interested in these filenames...



...(the ones with the pinkish background). Don't care how you post them

 

On each pink line with a stack on it i right clicked it and clicked properties. Took a screenshot of it and posted it underneath the other bluescreen info. There was only 1 pink line per blue screen


5/17/11

==================================================
Dump File : 051711-43103-01.dmp
Crash Time : 5/17/2011 1:27:50 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x1000009f
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`00000258
Parameter 3 : fffffa80`03564040
Parameter 4 : fffff800`00b9c510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+824da
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051711-43103-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 471,952
==================================================


5/11/11

==================================================
Dump File : 051111-51620-01.dmp
Crash Time : 5/11/2011 2:59:57 AM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00001097
Parameter 3 : 00000000`09060012
Parameter 4 : fffffa80`03cd0bb0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051111-51620-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================


5/9/11

==================================================
Dump File : 050911-48219-01.dmp
Crash Time : 5/9/2011 8:06:42 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`033fb617
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\050911-48219-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================



4/28/11

==================================================
Dump File : 042811-44132-01.dmp
Crash Time : 4/28/2011 1:57:52 AM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`03408617
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\042811-44132-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================



4/23/11
==================================================
Dump File : 042311-58188-01.dmp
Crash Time : 4/23/2011 3:03:25 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`033b0617
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\042311-58188-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,584
==================================================

 

Oops didn't read the first line...

hmmm...

Everything in ntoskrnl only (no driver modules on the stack)...I'm leaning towards allurgroceries' reply...bad RAM, bad CPU, bad GPU....some hardware failure.

Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL

 

So not a driver problem then? :/

I did memtest before didnt find any errors.

So whenever these bluescreens happen it's just a piece hardware deciding not to work at that moment?...Any way to find out what it is?

Uggggh

How do i go about using driver verifier as a troubleshooting tool? I've looked at it before, no unsigned drivers, but there are 2 drivers made for older versions of windows. Special pool option? What's that?

If it helps at all those two drivers made for older versions of windows are

pxhlpa64.sys
wpsdrvnt.sys

 

I can't rule out a driver problem, but the BSODs aren't happening as a direct result of driver code executing, which makes narrowing down the offending hardware (or its associated driver) difficult.

This has probably already been recommended and/or you've maybe tried it all before, but I would just strip down everything. Remove or disable all hardware that you can while still letting the machine function...network adapters, touchpads, sound devices, etc. For the remaining devices use the stock drivers for your operating system if they are available. Make sure Windows update isn't set to automatically install updates....you want to catch any drivers pushed by Microsoft before they install. If you already are not letting Windows Update install updates automatically, then you can look through the optional updates....not all pushed drivers are bad...there may be updated drivers for the OS that are good.

No fun when the crashes can't be replicated easily...

 

I guess ill try running memtest after removing a stick of RAM.

I did some reading somewhere that someone didn't get any errors while both sticks were in...but got hundreds when trying just 1.

OI.....

 

Is wpsdrvnt.sys related to some 3rd party security software? Forgot to mention those can be number one culprits. Remove any 3rd-party anti-virus, firewall, etc. software and use Microsoft Security Essentials and the built in firewall instead!!! (if the machine then works you can always move to a 3rd-party security solution.

Not sure what pxhlpa64.sys is...do you know? Sonic/Roxio related?

On the bright side, your avatar is spot-on!

 

The third party security software i'm going to assume is the Symantec that my college requires me to install to use the internet on campus. I guess once i leave campus this week i can uninstall it for the summer and see if the BSOD's go away. I also have malwarebytes.

Pxhlpa... no idea. I do have roxio burn on my computer. Could it be that? It came with the computer.

Mk i got rid of wpsdrvnt.sys. I went to ResNet and they updated their system about a month ago so i no longer need symantec. They allow us to have Microsoft security essentials so i have that on here now. I did driver verifier again and the wpsdrvnt.sys is nowhere to be found. I guess i will have to sit and wait and see if it happens again. If it does, then i'll get rid of my roxio software. And if it happens again....


HARDWARE!!!! ugh...
'

EDIT: just went and uninstalled Roxio...May as well just eliminate both of them. Instead of waiting weeks in between each BSOD if i get them again.

 

So far so good. Its been nearly 7 days since my last blue screen since i removed the drivers made for older versions of windows. wpsdrvnt.sys and pxhlpa64.sys.

wpsdrvnt.sys driver was removed by uninstalling the symantec program i had. And pxhlpa64.sys driver was removed by uninstalling the roxio program that came with the computer.


I'm not getting my hopes up quite yet. But so far everything is good. Just updating those that helped me and updating for anyone that may be googling this type of issue.

Use your driver verifier! Look for out of date drivers, and unsigned drivers. Research what programs are related to them and uninstall them if possible!


...i hope i don't get another BSOD

 

Another update.

Its been 2 weeks since my last blue screen. The longest period of time since the bluescreens started.

I haven't had a blue screen since i removed the programs associated with the wpsdrvnt.sys and pxhlpa64.sys drivers. Unfortunately i cannot tell you guys which was the offending driver (if that was the problem) since i removed them at the same time.

I'll give it one more week before i mark it as solved. But so far its looking good! Fingers crossed!

For those searching for a solution on google or something....
Just typed in "verifier" into the run bar. A program named "verifier" came up (which is the driver verifier). Did a search for "unsigned drivers". Found nothing. Did a search for "drivers made for older versions of windows" And the wpsdrvnt.sys driver and the pxhlpa64.sys driver both popped up. Then INSTEAD of pushing finish. I went and researched which programs were associated with those drivers and then uninstalled them.

Hope this helps. I always hated trying to find information on the internet and then meeting un-updated threads

Thanks to all that have helped

 

Ugh..I was just about to come and say this is solved.

I had a bluescreen on May 17th. And i haven't had one until June 25th...

I've had 2 within 24 hours...I really think it might be hardware related now...Or some sort of bad driver.. Idk... Take a look.. Man this is depressing. I and i just got out of warranty

I was really starting to think that the issue was solved. And who knows it might have been, this might just be a new issue....Screw blue screens.

Each one is a picture. 1st one is the first one that happened....I wish i knew what was going on...Ugh.

Anyone have any ideas?

Imageshack - bluescreen2.png
Imageshack - bluescreen1.png

I'm thinking i should just completely reinstall windows 7, But i was never provided with any CD's so i don't have a clue how

 

you should flash the original BIOS and try a fresh windows install. there's a link somewhere in these forums to get an original copy. install all of the original drivers. if the BSOD's still persist after the fresh install then it is most probably a hardware failure.

 

Im thinking i should try using the recovery partition within my computer?

Any clue on how to go about that? Pressing F9 at start up it says in my manual.

Well, i backed up my entire computer. Was a 25GB backup file.

Then i used the recovery partition within the HDD via F9 in during the BIOS splash screen.

The system seems to be fully reset to when i first turned it on, had to reconfigure windows and everything.

Removed some bloatware
I created another backup now, (this one was only 59MB! haha!)
And i created a system restore point.

Now i am reinstalling all the windows updates, will be updating my video driver. etc.

I hope this works

 

I've seen a few sites talking about video drivers causing it. If you don't feel like playing driver whack-a-mole, a fresh install is probably best. I'd suggest not getting any junk software that you -might- use, only what you -will- use. If you're still having this problem after a clean install, its probably hardware related. Alternately, as I said earlier, it might be video problems, try some older video drivers and see if it helps.

 

I updated to the newest NVIDIA driver (275.33) and did a clean install on it (after my windows clean install)

If i have problems again, i will downgrade my video driver. And if it happens yet again after that, I throw up the white flag and say its hardware related.

But so far so good since the clean install of windows 7. But then again that isn't saying much considering the blue screens usually are pretty spaced out (aside from the 2 i had in 24 hours right before the clean install)