Another BSOD post.

[Tzelik]

I recently switched to 7 (havent even fully activated it yet) and I am getting Blue screens when i try to play WoW.

I believe I have attached all the pertinent files as requested in the "How-To" post. I am not a computer genius, please help me here

-Tzel

 

[wish]

Hi Tzel
No wonder that you get bsod because your Linksys ethernet driver is very old.
Please update that driver if possible or delete it from your windows. (windows\system32\DRIVERS\lne100v4.sys)
lne100v4.sys Timestamp: Wed May 03 23:07:50 2000

You may also remove AVG and replace it with MSE because MSE well known running better on windows.

Update these old drivers :
- Logitech driver --> LHidFilt.Sys and LMouFilt.Sys
- Linksys driver --> lne100v4.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {170, 2, 0, 8b3ab38e}

Unable to load image \SystemRoot\system32\DRIVERS\lne100v4.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for lne100v4.sys
*** ERROR: Module load completed but symbols could not be loaded for lne100v4.sys
Probably caused by : lne100v4.sys ( lne100v4+194d )

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

3: 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: 00000170, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8b3ab38e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 8277d718
Unable to read MiSystemVaType memory at 8275d160
 00000170 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisMCompleteBufferPhysicalMapping+27
8b3ab38e ff7014          push    dword ptr [eax+14h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8d552b64 -- (.trap 0xffffffff8d552b64)
ErrCode = 00000000
eax=0000015c ebx=8b3ab367 ecx=84f76a08 edx=84e73ae8 esi=82a26400 edi=00000141
eip=8b3ab38e esp=8d552bd8 ebp=8d552be4 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
ndis!NdisMCompleteBufferPhysicalMapping+0x27:
8b3ab38e ff7014          push    dword ptr [eax+14h]  ds:0023:00000170=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8b3ab38e to 8265b7eb

STACK_TEXT:  
8d552b64 8b3ab38e badb0d00 84e73ae8 995616e7 nt!KiTrap0E+0x2cf
8d552be4 9956294d 84f4f0e0 0000015c 00000141 ndis!NdisMCompleteBufferPhysicalMapping+0x27
WARNING: Stack unwind information not available. Following frames may be wrong.
8d552c2c 8b3ad18d 84f674c0 84f74438 84f4f0e0 lne100v4+0x194d
8d552c58 8b37d54c 84f7444c 84f74438 00000000 ndis!ndisMDpc+0x173
8d552c78 8267d3b5 84f7444c 84f74438 00000000 ndis!ndis5InterruptDpc+0x99
8d552cd4 8267d218 8d536120 8d53b800 00000000 nt!KiExecuteAllDpcs+0xf9
8d552d20 8267d038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
8d552d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
lne100v4+194d
9956294d ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  lne100v4+194d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lne100v4

IMAGE_NAME:  lne100v4.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  391113b6

FAILURE_BUCKET_ID:  0xD1_lne100v4+194d

BUCKET_ID:  OLD_IMAGE_lne100v4.sys

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

 

[Tzelik]

well, Linksys apparently hasnt released windows 7 drivers. I spoke to their tech support and will now be trying a different brand. Thanks for the help.

-Tzel

 

[cybercore]

Excellent post, wish.

well, Linksys apparently hasnt released windows 7 drivers. I spoke to their tech support and will now be trying a different brand. Thanks for the help.

-Tzel

It's the problem then, lne100v4+194d, if no compatible drivers for it you got 2 options then:

1. Replace this device with a new one compatible with Windows 7

2. Switch to Windows XP