Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen of death


  • Please log in to reply
1 reply to this topic

#1 Srobak2001

Srobak2001

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:04:58 AM

Posted 07 December 2008 - 06:25 PM

I have been experiencing the bsod for some time now. I actually just about got this message posted and when I went to click submit the BSOD once again entered my life. When I first started getting it I decided I would just format my HD and reinstall windows, this did not solve my problem. I continue to get it after my computer has been running for a little bit. I ran windows debugger and below is the analysis I got. Any suggestions would be great.


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini120708-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun Dec 7 17:19:42.437 2008 (GMT-6)
System Uptime: 0 days 0:29:09.000
Loading Kernel Symbols
...............................................................
..........................................
Loading User Symbols
Loading unloaded module list
.................
Unable to load image LSIPNDS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for LSIPNDS.sys
*** ERROR: Module load completed but symbols could not be loaded for LSIPNDS.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {ffff, 2, 0, f85e7734}

Probably caused by : LSIPNDS.sys ( LSIPNDS+8734 )

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: 0000ffff, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f85e7734, address which referenced memory

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


READ_ADDRESS: 0000ffff

CURRENT_IRQL: 2

FAULTING_IP:
LSIPNDS+8734
f85e7734 8b10 mov edx,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from f85ea787 to f85e7734

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f9001e10 f85ea787 828a6000 00000000 00000000 LSIPNDS+0x8734
f9001e34 f85e2fe7 82a31fc8 8288551a 00000007 LSIPNDS+0xb787
f9001f8c f85e3566 828a6000 f9001fac 82a71490 LSIPNDS+0x3fe7
f9001fb8 f8a64e99 00000008 82a19c10 82a19e74 LSIPNDS+0x4566
f9001fd0 804dbbd4 828a60ec 828a60d8 00000000 NDIS!ndisMDpcX+0x21
f9001ff4 804db89e ee6796c4 00000000 00000000 nt!KiRetireDpcList+0x46
f9001ff8 ee6796c4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
804db89e 00000000 00000009 bb835675 00000128 0xee6796c4


STACK_COMMAND: kb

FOLLOWUP_IP:
LSIPNDS+8734
f85e7734 8b10 mov edx,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: LSIPNDS+8734

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: LSIPNDS

IMAGE_NAME: LSIPNDS.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3ef91459

FAILURE_BUCKET_ID: 0xD1_LSIPNDS+8734

BUCKET_ID: 0xD1_LSIPNDS+8734

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

BC AdBot (Login to Remove)

 


#2 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:58 PM

Posted 07 December 2008 - 06:34 PM

Probably caused by : LSIPNDS.sys ( LSIPNDS+8734 )

I believe that the LSIPNDS.sys file is related to your wireless card. You might want to try updating the driver for it.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users