BSOD on t400/t500/x301/x200 on Vista 32

By locker2 ยท 9 replies
Jul 15, 2009
  1. Hi, first time post so thanks ahead of time :)

    Getting random BSOD on shutdown on 4 models of lenovo laptops. Trying to stabalize these images and each of them throw up a error related to what appears to be the Ethernet driver. BSOD is on shutdown, and happens only sporadically, maybe once every 7 or 8 shutdowns which is terrible in terms of troubleshooting.

    I'm having issues trying to include the dmp file details, says I must remove links from my message but i don't have any links in it?
  2. B00kWyrm

    B00kWyrm TechSpot Paladin Posts: 1,436   +37

    Try zipping up to five of your most recent minidumps.
    Then using the paperclip icon at the top of the reply tools (next to the emoticon button).
    This should allow you to make the attachment.
  3. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

    Is the ethernet card/drivers the only thing these have in common?
  4. locker2

    locker2 TS Rookie Topic Starter

    Here's the dump...any help would be so appreciated..

    Kernel Summary Dump File: Only kernel address space is available
    Symbol search path is: C:\Windows\Symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Machine Name:
    Kernel base = 0x82217000 PsLoadedModuleList = 0x8232ec70
    Debug session time: Wed Jul 15 04:30:14.734 2009 (GMT-7)
    System Uptime: 0 days 0:03:45.329
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *
    Use !analyze -v to get detailed debugging information.
    BugCheck 7E, {c0000005, 8903799d, b3ed9b88, b3ed9884}
    Probably caused by : e1y6032.sys ( e1y6032+16e27 )
    Followup: MachineOwner
    0: kd> !analyze -v
    * *
    * Bugcheck Analysis *
    * *
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8903799d, The address that the exception occurred at
    Arg3: b3ed9b88, Exception Record Address
    Arg4: b3ed9884, Context Record Address
    Debugging Details:

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    8903799d f6410e02 test byte ptr [ecx+0Eh],2
    EXCEPTION_RECORD: b3ed9b88 -- (.exr 0xffffffffb3ed9b88)
    ExceptionAddress: 8903799d (ndis!NdisCancelTimerObject+0x00000036)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: 7b40e90f
    Attempt to read from address 7b40e90f
    CONTEXT: b3ed9884 -- (.cxr 0xffffffffb3ed9884)
    eax=00650000 ebx=825dd106 ecx=7b40e901 edx=00000000 esi=865e8770 edi=89037967
    eip=8903799d esp=b3ed9c50 ebp=b3ed9c54 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    8903799d f6410e02 test byte ptr [ecx+0Eh],2 ds:0023:7b40e90f=??
    Resetting default scope
    PROCESS_NAME: System
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    READ_ADDRESS: 7b40e90f
    8936de27 5f pop edi
    LAST_CONTROL_TRANSFER: from 8936de27 to 8903799d
    b3ed9c54 8936de27 005e8770 00000000 8626f000 ndis!NdisCancelTimerObject+0x36
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b3ed9c68 893680af 8626f000 b3915c60 89040000 e1y6032+0x16e27
    b3ed9c90 89361815 8626f000 861b80e8 b3ed9cb8 e1y6032+0x110af
    b3ed9ca0 890f2758 000004d2 00000000 00000000 e1y6032+0xa815
    b3ed9cb8 890f4ad0 001b80e8 89040000 8903ea38 ndis!ndisMShutdownMiniport+0xa8
    b3ed9cf8 890f4fc2 b3915c60 b3915d18 00000006 ndis!ndisSetPower+0x541
    b3ed9d20 8221c7c2 b3915d18 847a3588 00000000 ndis!ndisPowerDispatch+0x1a3
    b3ed9d7c 823ecc42 8799f090 c3d3d88b 00000000 nt!PopIrpWorker+0x40f
    b3ed9dc0 82255efe 8221c3af 8799f090 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    SYMBOL_NAME: e1y6032+16e27
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: e1y6032
    IMAGE_NAME: e1y6032.sys
    STACK_COMMAND: .cxr 0xffffffffb3ed9884 ; kb
    FAILURE_BUCKET_ID: 0x7E_e1y6032+16e27
    BUCKET_ID: 0x7E_e1y6032+
  5. Route44

    Route44 TechSpot Ambassador Posts: 11,984   +72

  6. B00kWyrm

    B00kWyrm TechSpot Paladin Posts: 1,436   +37

    As a quick followup on Route44... Lenovo offers two versions of the driver...
    e1y6032.sys (180422) Windows Vista 32-bit
    e1y60x64.sys (180422) Windows Vista 64-bit
    Be sure to use the right one for your system.
  7. locker2

    locker2 TS Rookie Topic Starter

    Right, thanks guys for the reply. We've verified we're using the correct version of the driver for Vista 32 bit, and uninstalled and reinstalled the driver with no success. the aggrivating part is it's so sporadic. it occurs at shutdown, but only I would say about once every 10 shutdowns, not every time.

    any other thoughts?
  8. B00kWyrm

    B00kWyrm TechSpot Paladin Posts: 1,436   +37

    Have you changed NIC cards?
    If so, is it possible that there are remnants of the old drivers still on your system?
  9. locker2

    locker2 TS Rookie Topic Starter

    Book..these were all factory built lenovos. We did not change any hardware, all we did was apply windows updates, when to lenovo to update anything via system updater. I will look however to see if there are any old drivers by chance, thanks.
  10. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

    I noticed the driver version on the website is
    Release Date: 2009/06/10

    So this driver was just released a month ago?! Are your computers all that new?! Did these problems start to occur after the new driver was applied?

    This might be the only driver version for T400 (i can't tell from web site release notes) but you might try on each computer, go to Dev Manager, find the network adapter
    >> Rt click Properties, click Driver tab
    >> Click the Roll Back Driver button

    If you can't rollback you might try uninstalling that one month old version and looking for the prior version (if one exists) and see if the older version runs better
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...