Windows 7 WIN7 BSOD: ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5708972E5E6000 )

MJL

New Member
Anyone have a fix for this tragedy?
 

Attachments

  • 090616-13119-01.dmp
    1.2 MB · Views: 512
  • MiniDump WIL60030331.txt
    43.5 KB · Views: 454
Looks like it's a problem with your wireless card.
0: kd> !analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa801d8f9a10, fffff80003c073d8, fffffa8029cd2c60}

c0000005 Exception in ext.analyze debugger extension.
PC: 00007ffc`baefd06a VA: 00000000`00000040 R/W: 0 Parameter: 00000000`00000000
0: kd> !devobj fffffa801d8f9a10
Device object (fffffa801d8f9a10) is for:
Cannot read info offset from nt!ObpInfoMaskToOffset
\Driver\pci DriverObject fffffa801d29d680
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
DevExt fffffa801d8f9b60 DevObjExt fffffa801d8f9f88 DevNode fffffa801d8f5930
ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) fffffa801d8fa890 \Driver\ACPI
Device queue is not busy.
0: kd> !devnode fffffa801d8f5930
DevNode 0xfffffa801d8f5930 for PDO 0xfffffa801d8f9a10
Parent 0xfffffa801d8d2d90 Sibling 0000000000 Child 0xfffffa80295005a0
InstancePath is "PCI\VEN_8086&DEV_24F3&SUBSYS_08508086&REV_3A\B808CFFFFF33271200"
ServiceName is "NETwNs64"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[15] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[14] = DeviceNodeEnumeratePending (0x30c)
StateHistory[13] = DeviceNodeStarted (0x308)
StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
StateHistory[10] = DeviceNodeStarted (0x308)
StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
StateHistory[07] = DeviceNodeStarted (0x308)
StateHistory[06] = DeviceNodeStartPostWork (0x307)
StateHistory[05] = DeviceNodeStartCompletion (0x306)
StateHistory[04] = DeviceNodeStartPending (0x305)
StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
StateHistory[02] = DeviceNodeDriversAdded (0x303)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
Flags (0x4c000030) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
DNF_NO_UPPER_CLASS_FILTERS
CapabilityFlags (0x00002040) UniqueID, WakeFromD3
 
Nice call Neem's.. Tell me, what's your debugger running like?

This, 'NETwNs64' relates to the Intel WiFi driver. If your using a laptop you can find a driver update on the laptops support page. Do not use a driver auto updater as these simply cause more issues than cure.
 
Hmm.... My debugger shouldn't have bother going online as I have most of the symbols downloaded as packs plus i always make a back up of my symcache folder. Currently my symcache holds around 22GB of symbols but yet it's still as slow as molasses.

This threads dump file I gave up on especially after i saw you'd answered .
I'll have a chat with some of the guy's over at sysnative and see if they know anything about it.
 
Have you tried turning on noisy loading to see what the debugger is doing? !sym noisy
 
Yes have you? the results were rather vague to non existant to be honest..
 
Hehe yeah i do something similar but it's getting beyond a joke now. The 8.1 version worked fine as does w10v from time to time.
 
Back
Top