Solved Had paused Dead space 2 when I got BSOD Bug Check Code 0x000000d1

[Thomath]

Hello
This is my first post here

I have just resently build this rig 1-2 months old
Had been absent from the game for roughly 2 hours, when I went
back to resume the game, my computer had restarted because of BSOD.

My pc is cooled by a H100 and the temps during the game was max 93°F,
I ran memtest86+-4.20.usb with pass and also IntelBurnTest v2.54 pass
This is what bluescreenview info is giving me.

Dump File : 102812-8065-01.dmp
Crash Time : 28-10-2012 21:13:17
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102812-8065-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 277.536

A bit oc info cpu 3770K 4.6 MHz, core voltage 1.19 V
Ram 2x8 XMP profile cas 9-9.9-24 voltage 1.5 V 1600MHz

Any help would be appreciatet

 

[Arc]

Welcome aboard.

Uninstall these programs...

• Start Menu\Programs\ASUS
• Start Menu\Programs\ASUS\AI Suite II
• Start Menu\Programs\Catalyst Control Center

Your crash dump says:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck D1[/COLOR], {0, 2, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner

As per Carrona.org, STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUALhttp://www.carrona.org/bsodindx.html#top
Usual causes: Device driver

To find out the faulting driver (as it is not found in the stack trace), we are to use Driver Verifier there.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

And, if you are OCing, get back to default settings.

 

[Thomath]

Hello again
Here is an update
System is back to default
I have uninstalled AI Suite II and Catalyst Control Center as you suggestet.
I followed the guide and ran driver verifier for more then 30 hours with only non
Microsoft drivers checket.
No BSOD at all, so is it fair to say that the problem was with one of the uninstalled
programs?
Didn't know that AISuite II and catalyst Control Center could cause a BSOD,
Do you know of any bug free versions of these programs or should I just live without

Thanks for all your help
Best regards

Thomas

 

[Thomath]

Hallo
Back here with som more info
After running driver verifer more then 30 hours, finding no BSOD i switched it of
I went back to my old OC settings, then of course I got one more of the same BSOD
as before when playing dead space 2.
An old saying in danish( god advice is expensive)
So I was thinking mayby I need to give the cpu vcore some more juice, I tried auto OC
at 4.6 to see what the vcore would be and it was 1.33v, manually OC i had set the vcore
to 1.19 so I raised it to 1.25v.
I have been running with my new OC settings and playing dead space 2 four days now with no BSOD

So whats your thought on this could it be the vcore or do you still think this is a driver problem?

 

[Arc]

It cannot be. If it has been a driver problem, it must have crashed within the time when verifier was enabled.

If it is not crashing now, use your present settings, but if there are further crashes, you may disable the OC, I guess.

 

[Thomath]

The cause of this BSOD was most definitely not giving the Vcore
enough power.
No more BSOD'S

Thanks for your time and help with this issue
All the best to crew