Blue Screen of Death

Hello, I keep getting a blue screen of death, when the computer starts back up this message is shown...
I tried to upload the C:\Windows\Minidump\ files but I keep getting this error...


"Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8003D07E30
BCP3: FFFFF80000BA2748
BCP4: FFFFFA8003E69810
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\081312-13135-01.dmp
C:\Users\Einrich\AppData\Local\Temp\WER-34039-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
"

 

Hi and Welcome to Majorgeeks.

Copy the dump(s) to your Desktop then zip it, right-click it and 'Send to > Compressed folder', attach the resulting zip to a reply.

Your error code indicates 'A device object has been blocking an IRP for too long a time', so hopefully, we can track down the cause from the dump.

 

This is the first computer I have owned in about 8 years, lol
I only had it 3 weeks and im getting this damn blue screen crap..
what is an IRP??

 

What's an IRP? I/O Request Packet, here's a Microsoft take on it. I'd liken it to 'lag', one part of an operation halts because it's waiting for information that's late arriving, we need to find what's stopping up or blocking that IRP.

It usually occurs when the computer is switching between different power states, like from standby/sleep/hibernation through wake to on, or from normal low power mode to full power or 'turbo'

I checked the problem with the latest dump, the initial "Unable to load image \SystemRoot\system32\DRIVERS\pneteth.sys" flagged up proved to be the offender when checking the blocked IRP, noted in Arg4 (here it's fffffa8003e69810). The 'caret' symbol (>) points out the offender when we run the check on the blocked IRP:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8003d07e30, fffff80000ba2748, [COLOR="Blue"]fffffa8003e69810[/COLOR]}

[B]Unable to load image \SystemRoot\system32\DRIVERS\pneteth.sys[/B], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="Red"]pneteth.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]pneteth.sys[/COLOR]
Probably caused by : ntkrnlmp

Followup: MachineOwner
---------

0: kd> [B]!irp[/B] [COLOR="Blue"]fffffa8003e69810[/COLOR]
Irp is active with 3 stacks 2 is current (= 0xfffffa8003e69928)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
[COLOR="Red"][B]>[/B][/COLOR][ 16, 2]   0 e1 fffffa800543b050 00000000 00000000-00000000    [COLOR="Red"]pending
	       \Driver\pneteth[/COLOR]
			Args: 00015400 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005e805b0    

			Args: 00000000 00000000 00000000 00000000

So it looks like we need to update the pneteth.sys driver, the Driver Reference Table shows what it is, a PdaNet USB wireless tether (http://www.junefabrics.com/). Update or uninstall it.

Once done, check in the Properties sheets of each networking and USB device that they are not allowed to be turned off to save power - that could play a big part in this.

On a general note, USB wireless drivers on Windows 7x64 are a big pain, many are simply Vista -era drivers that will cause crashes.



Here's a list of the 3rd party drivers, the oldest of which, pre-2011, really should be updated once you track down more recent versions:

EtronHub3.sys Thu Jun 30 07:03:02 2011 (4E0C1196) http://sysnative.com/drivers/driver.php?id=EtronHub3.sys

EtronXHCI.sys Thu Jun 30 07:03:00 2011 (4E0C1194) http://sysnative.com/drivers/driver.php?id=EtronXHCI.sys

HECIx64.sys Wed Oct 20 00:33:43 2010 (4CBE2AD7) http://sysnative.com/drivers/driver.php?id=HECIx64.sys

ITECIRfilter.sys Tue Mar 22 07:24:41 2011 (4D884EB9) http://sysnative.com/drivers/driver.php?id=ITECIRfilter.sys

MBfilt64.sys Fri Jul 31 04:40:32 2009 (4A7267B0) http://sysnative.com/drivers/driver.php?id=MBfilt64.sys

RTKVHD64.sys Tue Sep 20 12:51:42 2011 (4E787E4E) http://sysnative.com/drivers/driver.php?id=RTKVHD64.sys

Rt64win7.sys Fri Jun 10 07:33:15 2011 (4DF1BAAB) http://sysnative.com/drivers/driver.php?id=Rt64win7.sys

RtsPStor.sys Wed Jan 12 07:32:49 2011 (4D2D5921) http://sysnative.com/drivers/driver.php?id=RtsPStor.sys

amdxata.sys Fri Mar 19 16:18:18 2010 (4BA3A3CA) http://sysnative.com/drivers/driver.php?id=amdxata.sys

clwvd.sys Thu Apr 14 04:47:49 2011 (4DA66E65) http://sysnative.com/drivers/driver.php?id=clwvd.sys

igdkmd64.sys Wed Jul 27 00:22:40 2011 (4E2F4C40) http://sysnative.com/drivers/driver.php?id=igdkmd64.sys

itecir.sys Tue Jul 13 10:50:47 2010 (4C3C36F7) http://sysnative.com/drivers/driver.php?id=itecir.sys

netr28x.sys Tue Apr 19 04:31:37 2011 (4DAD0219) http://sysnative.com/drivers/driver.php?id=netr28x.sys

pneteth.sys Fri Nov 25 05:25:50 2011 (4ECF26DE) http://sysnative.com/drivers/driver.php?id=pneteth.sys

rtsuvc.sys Wed Jun 29 08:14:52 2011 (4E0AD0EC) http://sysnative.com/drivers/driver.php?id=rtsuvc.sys

ssadbus.sys Wed Dec 08 14:12:37 2010 (4CFF9255) http://sysnative.com/drivers/driver.php?id=ssadbus.sys

ssadcm.sys Thu May 12 14:09:45 2011 (4DCBDC19)http://sysnative.com/drivers/driver.php?id=ssadcm.sys

ssadmdfl.sys Thu May 12 14:08:26 2011 (4DCBDBCA)http://sysnative.com/drivers/driver.php?id=ssadmdfl.sys

ssadmdm.sys Thu May 12 14:08:36 2011 (4DCBDBD4) http://sysnative.com/drivers/driver.php?id=ssadmdm.sys

ssadwh.sys Wed Dec 08 14:12:14 2010 (4CFF923E) http://sysnative.com/drivers/driver.php?id=ssadwh.sys

 

Sorry I am having trouble, How do I unistall a driver? and how do i check properties sheet regarding USB shut down times?