BSOD on Windows Developer

Elmer

Extraordinary Member
#1
Just thought I'd crash Win 8 to have a look at the drivers.

Mostly Aug 2011 but the interesting thing is that secdrv.sys is still dated 2006
 


Attachments

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#2
Really is about time that driver got updated.
 


zigzag3143

Honorable Member
Microsoft MVP
#3
If it aint broke dont fix it!!!!!
 


nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#4
If it aint broke dont fix it!!!!!
We seem to have a different philosophy 'If it aint broken try and try again to break it' ;)
 


zigzag3143

Honorable Member
Microsoft MVP
#5
We seem to have a different philosophy 'If it aint broken try and try again to break it' ;)
I will second that. If it isnt broken you arent trying hard enough {grin}
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#6
You folks want a real dump file for the Consumer Preview to play with..:friendly_wink:

Since I know what is causing it, I thought it might be fun to test your Debugger.

Anyway, here it is.. I don't want to give away too much info, but the other data sources are not needed.
 


Attachments

Elmer

Extraordinary Member
#7
OK Saltgrass.

The jraid driver isn't the latest (or best) released. There was one mid '10 that caused a few problems. Which one I cannot say for certain.

And the Marvell stuff needs updating.

Now spill the beans and divulge what really happened :p
 


Trouble

Noob Whisperer
#8
Yes Clark, clue us in.
Your dump file drove my debugger nuts, complaining about the symbols being incorrect. But Kev and I compared notes and noted a couple old driver AHCI /Raid Marvell drivers and the JMicron jraid.sys.
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#9
The cause is the basic Network adapter I have been having problems with (e1i63x64.sys).

I am still messing with it, because it seems the situation changes daily as to whether it will blue screen or not. My WinDbg listed it as the problem file, didn't even have to guess. Currently I am in a new install of the OS, but will get you a readout you can compare to what you are getting, after I reimage back to the prior install.

Of course, it might look different on this machine since it was created here....
 


Trouble

Noob Whisperer
#10
Interesting, as when I saw that particular driver e1i63x64.sys 12/7/2011 it looked like it would have been the most recent one available from http://downloadcenter.intel.com/Default.aspx for which ever Gigabit Intel NIC you had installed and wouldn't have been on my radar as a problem component.
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#11
OK, here is the analysis from my machine, on my machine. Again, I have been having problems with the Network adapter disabling itself after sleep. Rebooting was the only way to get it back, and that resulted in Blue Screens.

I was looking at the install files (.inf) for the Windows 8 version of the adapter (Intel 82579V) and the Windows 7 version. I noticed there is no section in the Windows 8 version for Power Management, but is in the Windows 7 one. Maybe Windows 8 handles that differently, I do not know. The Windows 7 version installs 5 drivers on the drivers details section, the Windows 8 only installs the one.

Anyway, here is the result of the Windbg analysis. I am using symbols I downloaded for the Microsoft site for this version of Windbg, which is for the Windows 8 Consumer Preview. I am not using the Microsoft public symbol server at this time. Since I just set this debugger up, I may still have some more work to do.

PHP:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800790f060, Physical Device Object of the stack
Arg3: fffff880015e0780, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80082e4af0, The blocked IRP

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa8009bed050

DRIVER_OBJECT: fffffa800a0db440

IMAGE_NAME:  e1i63x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ee024b7

MODULE_NAME: e1i63x64

FAULTING_MODULE: fffff88017909000 e1i63x64

IRP_ADDRESS:  fffffa80082e4af0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`015e0748 fffff802`f69d4204 : 00000000`0000009f 00000000`00000003 fffffa80`0790f060 fffff880`015e0780 : nt!KeBugCheckEx
fffff880`015e0750 fffff802`f69d423a : fffffa80`08a31f00 fffffa80`09c56920 fffff880`015b9f00 fffff802`f68c5778 : nt!PopIrpWatchdogBugcheck+0x90
fffff880`015e07b0 fffff802`f68c7612 : fffffa80`08a31f38 fffff880`015e08a9 00000000`00000001 00000000`00000000 : nt!PopIrpWatchdog+0x32
fffff880`015e0800 fffff802`f68c7322 : 00000000`00000000 fffff802`f69011df fffff880`015b7180 00000000`00000000 : nt!KiProcessExpiredTimerList+0x232
fffff880`015e0910 fffff802`f68c702b : fffffa80`072530c0 00000000`002109ad fffff880`015e09d0 fffff880`015e0af0 : nt!KiExpireTimerTable+0x1a2
fffff880`015e09a0 fffff802`f68c690c : 00000000`002109ad fffff802`f6900be1 00000000`00000000 fffff880`015b7180 : nt!KiTimerExpiration+0x9b
fffff880`015e0a60 fffff802`f6a1355a : fffff880`015b7180 fffff880`015b7180 fffff880`015c2f00 fffffa80`09c5e800 : nt!KiRetireDpcList+0x47c
fffff880`015e0c60 00000000`00000000 : fffff880`015e1000 fffff880`015db000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_e1i63x64.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_e1i63x64.sys

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


Elmer

Extraordinary Member
#12
I'm with Randy.

I've got that used to looking at e1i62x64.sys that I just assumed that e1i63x64.sys would be the latest available.

Moral must be don't assume. Anything!
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#13
They are also being a little tricky about identifying a file. Small changes, like e1i instead of e1c or e1ic may be used to identify a Windows 8 installed version versus an Intel direct supplied version. But mine came from ASUS and worked fine in Windows 7, no reason a power management setting should be causing blue screens. Unless, possibly the bug fix (see below), was not included in the Windows 8 version.

In my latest install :numbness: I have disabled the onboard adapter and now using a Belkin wireless USB adapter. The drivers are the ones that come with it, since Windows 8 did not recognize the device. All seems to be going well with the default settings.

If the system stays stable, I will install the direct Intel driver, to see if it will run in Windows 8. The download page does mention a bug fix for the previous release. (16.8 to 16.8.1)

I cannot, at this time, recommend you install the WinDbg for the Windows 8 Consumer preview. I saw some problems that might be related and will be checking that out.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.