Re: Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Sartan Dragonbane (null_at_null.mistrust.ca)
Date: 02/19/04 

Date: Thu, 19 Feb 2004 02:41:18 GMT

I had a problem with my power-saving mode on my new motherboard that made me
want to rip my hair out, it was fixed when I disabled it and reinstalled
windows.

"Roger Redford" <condor_222@yahoo.com> wrote in message
news:4be257cb.0402181804.7721e328@posting.google.com...
> Hello,
>
> I keep getting the Blue Screen of Death (BS0D) lately.
>
> I have two machines. Dell 4550 runs XP Pro.
> Dell 4600 the other runs XP.
> Each has an onboard Intel ethernet connection.
> Each Connected with a crossover cable directly to each other.
> Each has a firewire IEEE1394 card in it.
>
> I know that this has something to do with the network.
> Why? Originally, there was no networking. Only since I
> connected the two, and installed Windows networking,
> have I been getting problems.
>
> I have downloaded the latest drivers from Intel and
> installed them. I then turned on both machines, with
> no applications running on them, and went to the store.
> When I came back, I had the BSOD.
> Interestingly, the BSOD only occurs on XP Pro.
>
> Also different about XP Pro:
> - all the network connections are bridged.
> - there is MAC bridge Miniport in XP Pro, but nothing
> similar in XP.
> - Task manager shows a network bridge at 400 mbps,
> when the card is only supposed to handle 100 Mbps.
> The 1394 is can handle 400.
>
> I never did get the two XP machines to talk to each
> other at the Windows level. But they work at
> when I use Intel's test tool.
>
>
> Grizzly details follow. Any ideas?
>
> Thanks a lot!
>
> ---------------
>
>
> I believe the last event in the event log before the BSOD is:
>
> The system detected that network adapter MAC Bridge Miniport
> - Packet Scheduler Miniport was connected to the network,
> and has initiated normal operation over the network adapter.
>
>
> And after rebooting from the crash:
>
> The computer has rebooted from a bugcheck.
> The bugcheck was:
> 0x000000d1 (0x00000000, 0x00000002, 0x00000000, 0x00000000).
> A dump was saved in: C:\WINDOWS\MEMORY.DMP.
>
>
> I've got some debug info from Memory.dmp:
>
> Microsoft (R) Windows Debugger Version 6.2.0013.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini021804-02.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: *** Invalid ***
>
****************************************************************************
> * Symbol loading may be unreliable without a symbol search path.
> *
> * Use .symfix to have the debugger choose a symbol path.
> *
> * After setting your symbol path, use .reload to refresh symbol
> locations. *
>
****************************************************************************
> Executable search path is:
> *********************************************************************
> * Symbols can not be loaded because symbol path is not initialized. *
> * *
> * The Symbol Path can be set by: *
> * using the _NT_SYMBOL_PATH environment variable. *
> * using the -y <symbol_path> argument when starting the debugger. *
> * using .sympath and .sympath+ *
> *********************************************************************
> *** ERROR: Symbol file could not be found. Defaulted to export
> symbols for ntoskrnl.exe -
> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
> Product: WinNt
> Built by: 2600.xpsp2.030422-1633
> Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
> Debug session time: Wed Feb 18 19:31:02 2004
> System Uptime: 0 days 0:46:26.953
> *********************************************************************
> * Symbols can not be loaded because symbol path is not initialized. *
> * *
> * The Symbol Path can be set by: *
> * using the _NT_SYMBOL_PATH environment variable. *
> * using the -y <symbol_path> argument when starting the debugger. *
> * using .sympath and .sympath+ *
> *********************************************************************
> *** ERROR: Symbol file could not be found. Defaulted to export
> symbols for ntoskrnl.exe -
> Loading Kernel Symbols
>
............................................................................
..............................................................
> Loading unloaded module list
> ............
> Loading User Symbols
>
****************************************************************************
***
> *
> *
> * Bugcheck Analysis
> *
> *
> *
>
****************************************************************************
***
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck D1, {0, 2, 0, 0}
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> Unable to load image \SystemRoot\System32\DRIVERS\e100b325.sys, Win32
> error 2
> *** WARNING: Unable to verify timestamp for e100b325.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> e100b325.sys
> Unable to load image NDIS.sys, Win32 error 2
> *** WARNING: Unable to verify timestamp for NDIS.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> NDIS.sys
> Unable to load image \??\C:\WINDOWS\System32\vsdatant.sys, Win32 error
> 2
> *** WARNING: Unable to verify timestamp for vsdatant.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> vsdatant.sys
> Unable to load image \SystemRoot\System32\DRIVERS\bridge.sys, Win32
> error 2
> *** WARNING: Unable to verify timestamp for bridge.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> bridge.sys
> Probably caused by : Unknown_Image ( e100b325+18817 )
>
> Followup: MachineOwner
> ---------
>
> kd> !analyze -v
>
****************************************************************************
***
> *
> *
> * Bugcheck Analysis
> *
> *
> *
>
****************************************************************************
***
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
> An attempt was made to access a pageable (or completely invalid)
> address at an
> interrupt request level (IRQL) that is too high. This is usually
> caused by drivers using improper addresses.
> If kernel debugger is available get stack backtrace.
> Arguments:
> Arg1: 00000000, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: 00000000, address which referenced memory
>
> Debugging Details:
> ------------------
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
>
> READ_ADDRESS: unable to get nt!MmPoolCodeEnd
> unable to get nt!MmSpecialPoolEnd
> unable to get nt!MmPagedPoolEnd
> unable to get nt!MmNonPagedPoolEnd
> unable to get nt!MmNonPagedPoolStart
> unable to get nt!MmSpecialPoolStart
> unable to get nt!MmPagedPoolStart
> unable to get nt!MiSessionPoolStart
> unable to get nt!MiSessionPoolEnd
> unable to get nt!MmNonPagedPoolExpansionStart
> unable to get nt!MmPoolCodeStart
> 00000000
>
> CURRENT_IRQL: 2
>
> FAULTING_IP:
> +0
> 00000000 ?? ???
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT
>
> BUGCHECK_STR: 0xD1
>
> LAST_CONTROL_TRANSFER: from 80530335 to 804f4103
>
> STACK_TEXT:
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 80539070 80530335 0000000a 00000000 00000002 nt!KeBugCheckEx+0x19
> 8053908c 00000000 82c181fc f6747817 82c181f8 nt!Kei386EoiHelper+0x257d
>
>
> FAILED_INSTRUCTION_ADDRESS:
> +0
> 00000000 ?? ???
>
> FOLLOWUP_IP:
> e100b325+18817
> f6747817 ?? ???
>
> FOLLOWUP_NAME: MachineOwner
>
> SYMBOL_NAME: e100b325+18817
>
> MODULE_NAME: Unknown_Module
>
> IMAGE_NAME: Unknown_Image
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 0
>
> STACK_COMMAND: kb
>
> BUCKET_ID: WRONG_SYMBOLS
>
> Followup: MachineOwner
> ---------

Relevant Pages

  • Re: Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... > I have two machines. ... > Each has an onboard Intel ethernet connection. ... > I know that this has something to do with the network. ... > * Symbol loading may be unreliable without a symbol search path. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... > I have two machines. ... > Each has an onboard Intel ethernet connection. ... > I know that this has something to do with the network. ... > * Symbol loading may be unreliable without a symbol search path. ...
    (microsoft.public.win2000.networking)
  • Re: Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL, Blue screen of Death
    ... > I have two machines. ... > Each has an onboard Intel ethernet connection. ... > I know that this has something to do with the network. ... > * Symbol loading may be unreliable without a symbol search path. ...
    (microsoft.public.windowsxp.help_and_support)
  • PPP Lan Bridge
    ... machines running FreeBSD 5.3 with 56K modems & PPP. ... line-of-sight wireless connection. ... network to transmit data. ... Timeclock connected to dial-up client via CrossOver ...
    (freebsd-net)
  • RE: wirless connection security issues
    ... wrt54gl only has a single port for the incoming network. ... I would set up the router to use the Class C private IP range ... for your machines. ... Subject: wirless connection security issues ...
    (Security-Basics)