[Grymm]

When installing a game or  sometimes playing a game I get a BSOD, the prompt is as follows:

 

  Problem Event Name: BlueScreen

  OS Version: 6.1.7601.2.1.0.768.3

  Locale ID: 1033

 

Additional information about the problem:

BCCode: 1000008e

BCP1: C0000005

BCP2: 8F2839B3

BCP3: AF39E994

BCP4: 00000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

 

Files that help describe the problem:

C:\Windows\Minidump\091514-38001-01.dmp

C:\Users\Grymm\AppData\Local\Temp\WER-54662-0.sysdata.xml

 

 

I also ran WhoCrashed and came up with this:

 

On Tue 9/16/2014 12:48:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091514-38001-01.dmp
This was probably caused by the following module: afd.sys (afd+0x39B3)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F2839B3, 0xFFFFFFFFAF39E994, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 9/16/2014 12:48:57 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7BB86)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F2839B3, 0xFFFFFFFFAF39E994, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

 

 

 

What do I do???

[Advertisements]

Can you upload the dump files for analysis.

Go to

C:\Windows\minidump

Upload all those files by copying them to the desktop and compressing them in a single .zip folder.

Or even better, upload a Kernel memory dump.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

[Jared44]

Can you upload the dump files for analysis.

Go to

C:\Windows\minidump

Upload all those files by copying them to the desktop and compressing them in a single .zip folder.

Or even better, upload a Kernel memory dump.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

[Grymm]

Thanks for replying, Jared! I was starting to get worried no one was going to help... lol. The crash happened again last night while attempting to redownload Everquest. Here is the Kernel Memory Dump

 

https://onedrive.liv...ithint=file,zip

Edited by Grymm, 17 September 2014 - 12:36 PM.

[Jared44]

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 85c05b58, Physical Device Object of the stack
Arg3: 8292cae0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: 888a0960, The blocked IRP

This bugcheck indicates an IRP took too long to complete and therefore we crashed.

 

Lets look at the PDO on the stack.

0: kd> !devobj 85c05b58
Device object (85c05b58) is for:
 NTPNP_PCI0019 \Driver\pci DriverObject 85817030
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
Dacl 8b85a640 DevExt 85c05c10 DevObjExt 85c05fc0 DevNode 84f5c8b8 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) 863ea028 \Driver\NETw5s32
Device queue is not busy.

So the device object which the IRP was trying to be sent down was the network pci stack.

0: kd> !irp 888a0960
Irp is active with 4 stacks 2 is current (= 0x888a09f4)
 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
>[ 16, 2]   0  0 863ea028 00000000 00000000-00000000    
	      *** ERROR: Module load completed but symbols could not be loaded for NETw5s32.sys
 \Driver\NETw5s32
			Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 863c4b00 00000000 82b28d5d-86625828 Success Error Cancel pending
	       \Driver\vwifibus	nt!PopSystemIrpCompletion
			Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-86625828    

			Args: 00000000 00000000 00000000 00000000

So the IRP being blocked was caused by NETw5s32 taking too long.

0: kd> lmvm NETw5s32
start    end        module name
95411000 95a8d000   NETw5s32   (no symbols)           
    Loaded symbol image file: NETw5s32.sys
    Image path: \SystemRoot\system32\DRIVERS\NETw5s32.sys
    Image name: NETw5s32.sys
    Timestamp:        Wed Jan 13 16:36:36 2010 (4B4DF694)
    CheckSum:         0067CCFF
    ImageSize:        0067C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your network driver is very outdated, you need to update your Intel® WiFi Link 5100 AGN network driver.

[Grymm]

Fantastic! I updated the drivers and have had no issues! I didn't even think the drivers would be an issue because I had just picked up the laptop from a local repair shop, they said they updated everything... apparently not.

 

Jared, where can I learn to debug and fix these problems on my own? Thank you!

[Jared44]

Debugging can be difficult but also easy.
To learn how to debug (specifically kernel debugging such as blue screens) you need to understand how Windows works internally.

To debug basic error such as yours you can install the Windows Debugger but when complex debugging is involved it can be very difficult.

I'm glad your PC is working fine.