bsod when playing anything 0X000000d1

[korzor]

do you guys use teamviewer ?

 

[korzor]

britton im looking at my idle now it's 52 CPU

 

[Britton30]

Yes, that is too hot for idling, it's not damaging but at idle should be much less.

I don't use TeamViewer, but perhaps some BSOD Team members do.

 

[korzor]

ok britton so any tips or vids how to clean a PC CPU and fans i.m new to PC i use to play on the ps3 never got a error on it

 

[korzor]

so any bsod team have teamviewer

 

[Britton30]

You should take it outside, remove a side panel, usually two screws in the back. Use some canned air to blow out any dust you see. The fan may have to be taken off of the CPU cooler to clean it.

You may actaully need an aftermarket cooler if you are using the one that came with the CPU.

To better help us to help you would you please add your systems specs? Here's the correct way to do it. :SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.

Your System Specs here.

After doing this your specs will be available in each of your posts.
Click on My system Specs in the lower left of this post to see how it should look.
Full instructions are in the tutorial.

 

[korzor]

britton i done some of it ^ ^ what do you think

 

[Britton30]

That's very good but I'd like to know what is your CPU cooler and power supply (PSU).

 

[x BlueRobot]

BSOD Analysis:

[COLOR="Red"]BugCheck D1[/COLOR], {[COLOR="Orange"]28[/COLOR], 2, [COLOR="Blue"]0[/COLOR], [COLOR="SeaGreen"]fffff88004601f58[/COLOR]}

Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+dc )

Usual causes:  Device driver

Okay, the thread began to process through it's DPC queue which I believe can only occur at IRQL Level 2, as a result of being at IRQL Level 2, the scheduler is turned off, therefore only non-paged pool can be accessed, since accessing memory which isn't available would lead to a page fault, which would then result in the thread being placed in a wait state with a context switch to a different thread being used, whilst the thread waited for the Memory Manager to process the page fault and make the memory address available.

A device driver must have been reading a non-paged pool address for a certain kind of data or memory address, but this memory address wasn't available or the data wasn't present, so it issued a illegal page fault, which then lead to the bugcheck.

3: kd> [COLOR="SeaGreen"]k[/COLOR]
Child-SP          RetAddr           Call Site
fffff880`009b0a78 fffff800`02ed41a9 nt!KeBugCheckEx
fffff880`009b0a80 fffff800`02ed2e20 nt!KiBugCheckDispatch+0x69
fffff880`009b0bc0 fffff880`04601f58 [COLOR="Red"]nt!KiPageFault+0x260[/COLOR] <-- Illegal Page Fault
fffff880`009b0d58 fffffa80`08d5d6a0 usbohci!OHCI_PollIsoEndpoint+0xdc
fffff880`009b0da8 fffff880`04604744 [COLOR="Red"]0xfffffa80`08d5d6a0[/COLOR] <-- No symbols?
fffff880`009b0db0 fffff880`0460ce8b usbohci!OHCI_PollEndpoint+0x4c
fffff880`009b0de0 fffff880`046119d1 USBPORT!MPf_PollEndpoint+0x9b
fffff880`009b0e10 fffff880`0461d077 USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`009b0e70 fffff880`0460df89 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`009b0ed0 fffff800`02edf2fc USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`009b0f00 fffff800`02ed7d05 nt!KiRetireDpcList+0x1bc
fffff880`009b0fb0 fffff800`02ed7b1c [COLOR="Red"]nt!KyRetireDpcList+0x5[/COLOR] <-- Empty DPC Queue
fffff880`0b44abe0 00000000`00000000 nt!KiDispatchInterruptContinue

TRAP_FRAME:  fffff880009b0bc0 -- ([COLOR="SeaGreen"].trap 0xfffff880009b0bc0[/COLOR])
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008d646c0
[COLOR="Red"]rdx=0000000000000000[/COLOR] rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004601f58 rsp=fffff880009b0d58 rbp=0000000000000000
 r8=000000004f444648  r9=fffff8800a33d100 r10=00000000ffffffff
r11=fffffa800b2c3330 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
usbohci!OHCI_PollIsoEndpoint+0xdc:
fffff880`04601f58 8b4228          mov     eax,dword ptr [COLOR="Red"][rdx+28h][/COLOR] ds:00000000`00000028=????????

0000000000000028 Nonpaged pool

If I made any mistakes, then it would appreciated if someone could correct me.

---------------------------------------------------------------

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[Arc]

If I made any mistakes, then it would appreciated if someone could correct me.

Sorry my friend, but it is a minidump.

Mini Kernel Dump File: Only registers and stack trace are available

All the information you will not get from it, but you will get some, for sure.

You can frame an idea what is going on. See the XHCI drivers ....

Image name: nusb3xhc.sys
Timestamp:        Fri Apr 23 07:04:36 2010

The decision you have arrived at is right, DV is needed. But, As you can see so many USB related entries in the stack text, pay attention to them more, than the page fault info.

 

[korzor]

arc and blue robot got no clue what your saying

 

[Arc]

See this part .... and follow it.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[x BlueRobot]

If I made any mistakes, then it would appreciated if someone could correct me.

Sorry my friend, but it is a minidump.

Mini Kernel Dump File: Only registers and stack trace are available

All the information you will not get from it, but you will get some, for sure.

You can frame an idea what is going on. See the XHCI drivers ....

Image name: nusb3xhc.sys
Timestamp:        Fri Apr 23 07:04:36 2010

The decision you have arrived at is right, DV is needed. But, As you can see so many USB related entries in the stack text, pay attention to them more, than the page fault info.

Thanks