TechSpot

Windows Vista laptop repeatedly crashes at startup

By hamricka
Jul 12, 2010
  1. I have a Sony Vaio VGN-NS240E and since the day I bought it, it goes to a blue screen at startup until it eventually is able to boot up. The sony vaio customer service is completely unhelpful. My warranty is up, too.

    I have an Intel Core 2 Duo CPU T6400 @ 2.00 GHz with 3.00 GB RAM on a 32-bit.
    BTW I am running on windows vista home premium... and I have service pack 2 installed.

    So I used the windows debugger program to analyze a minidump file and these are the results. But I have no clue what they mean. Can anyone help me?

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


    Loading Dump File [C:\Windows\Minidump\Mini071210-03.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
    Machine Name:
    Kernel base = 0x81e1c000 PsLoadedModuleList = 0x81f33c70
    Debug session time: Mon Jul 12 17:46:47.725 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:16.319
    Loading Kernel Symbols
    ...................................................
    Loading User Symbols
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, 82ee276d, 8ab5b5dc, 8ab5b2d8}

    Probably caused by : ndis.sys ( ndis!NdisReadConfiguration+c8 )

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

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 82ee276d, The address that the exception occurred at
    Arg3: 8ab5b5dc, Exception Record Address
    Arg4: 8ab5b2d8, 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.

    FAULTING_IP:
    ndis!NdisReadConfiguration+c8
    82ee276d 8b4608 mov eax,dword ptr [esi+8]

    EXCEPTION_RECORD: 8ab5b5dc -- (.exr 0xffffffff8ab5b5dc)
    ExceptionAddress: 82ee276d (ndis!NdisReadConfiguration+0x000000c8)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: 30a8854a
    Attempt to read from address 30a8854a

    CONTEXT: 8ab5b2d8 -- (.cxr 0xffffffff8ab5b2d8)
    eax=00000000 ebx=8204a841 ecx=82e4187c edx=82e41990 esi=30a88542 edi=00000003
    eip=82ee276d esp=8ab5b6a4 ebp=8ab5b718 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
    ndis!NdisReadConfiguration+0xc8:
    82ee276d 8b4608 mov eax,dword ptr [esi+8] ds:0023:30a8854a=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_PARAMETER1: 00000000

    EXCEPTION_PARAMETER2: 30a8854a

    READ_ADDRESS: GetPointerFromAddress: unable to read from 81f53868
    Unable to read MiSystemVaType memory at 81f33420
    30a8854a

    FOLLOWUP_IP:
    ndis!NdisReadConfiguration+c8
    82ee276d 8b4608 mov eax,dword ptr [esi+8]

    BUGCHECK_STR: 0x7E

    LOCK_ADDRESS: 81f50600 -- (!locks 81f50600)

    Resource @ nt!PiEngineLock (0x81f50600) Available

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
    Lock address : 0x81f50600
    Thread Count : 0
    Thread address: 0x00000000
    Thread wait : 0x0

    LAST_CONTROL_TRANSFER: from 82ecdae8 to 82ee276d

    STACK_TEXT:
    8ab5b718 82ecdae8 8ab5b75c 8ab5b750 30a88542 ndis!NdisReadConfiguration+0xc8
    8ab5b754 82eea525 c0000001 81f09005 00000000 ndis!ndisReadOffloadRegistry+0x33e
    8ab5b7f8 82ee9c62 854196c8 86e9b438 86e9bf0c ndis!ndisInitializeConfiguration+0x599
    8ab5b8cc 82ee95cc 85419818 8ab5b908 8542e578 ndis!ndisAddDevice+0x587
    8ab5b9d0 81e2825b 85419818 8542e578 8542f8b0 ndis!ndisPnPAddDevice+0x572
    8ab5b9ec 81f7f654 85419818 82ee905a 00000004 nt!PpvUtilCallAddDevice+0x19
    8ab5ba14 81f7e66c 85419818 82ee905a 00000002 nt!PnpCallAddDevice+0x7e
    8ab5baf0 81f7da27 02000000 00000000 81f4e550 nt!PipCallDriverAddDevice+0x477
    8ab5bcec 81e28764 846abea8 867cae70 8ab5bd38 nt!PipProcessDevNodeTree+0x15c
    8ab5bd44 81ec1e22 00000000 00000000 846a5828 nt!PnpDeviceActionWorker+0x229
    8ab5bd7c 81ff1c42 00000000 eb2ad7ab 00000000 nt!ExpWorkerThread+0xfd
    8ab5bdc0 81e5af4e 81ec1d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: ndis!NdisReadConfiguration+c8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ndis

    IMAGE_NAME: ndis.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 49e02080

    STACK_COMMAND: .cxr 0xffffffff8ab5b2d8 ; kb

    FAILURE_BUCKET_ID: 0x7E_ndis!NdisReadConfiguration+c8

    BUCKET_ID: 0x7E_ndis!NdisReadConfiguration+c8

    Followup: MachineOwner
    ---------
     
  2. fastco

    fastco TS Rookie Posts: 1,511

    Read this please.. We need more than one minidump to determine the cause or the crashes. Most likely faulty memory if it happens when the computer boots and has been occurring since you got the computer. You can download Memtest here in the download section and let it run overnight. If it finds errors then remove one module at a time and run Memtest until you find out which one is bad.
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.