Blue Screen Of Death


  1. Posts : 33
    Windows 7
       #1

    Blue Screen Of Death


    Is Windows 7 . . . - x86 (32-bit) or x64 ? 32-bit
    - the original installed OS on the system?
    Windows XP Media Edition 2002
    - an OEM or full retail version? Full Retail
    - OEM = came pre-installed on system - Full Retail = you purchased it from retailer
    - What is the age of system (hardware)? 3-5 months - What is the age of OS installation (have you re-installed the OS?) 2-5 days.

    Zip with the file + health check report: Attachment 170006
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    BSODs caused by an obsolete USB Dongle driver, probably an old Belkin device
    Please update its driver if possible or else remove that device, its is very old and is not Windows 7 certified
    http://en-us-support.belkin.com/app/...twork-adapters
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {4, 258, 855ae798, 82d60b24}
    
    Unable to load image \SystemRoot\system32\DRIVERS\rt73.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for rt73.sys
    *** ERROR: Module load completed but symbols could not be loaded for rt73.sys
    Probably caused by : memory_corruption
    
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp
        subsystem.
    Arg2: 00000258, Timeout in seconds.
    Arg3: 855ae798, The thread currently holding on to the Pnp lock.
    Arg4: 82d60b24
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  4
    
    FAULTING_THREAD:  855ae798
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LOCK_ADDRESS:  82d9ff80 -- (!locks 82d9ff80)
    
    Resource @ nt!PiEngineLock (0x82d9ff80)    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  : 0x82d9ff80
        Thread Count  : 0
        Thread address: 0x00000000
        Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from 82ca8c75 to 82ca1aa6
    
    STACK_TEXT:  
    8db1f3d8 82ca8c75 855ae798 00000000 807c4120 nt!KiSwapContext+0x26
    8db1f410 82ca7573 855ae858 855ae798 8db1f4f8 nt!KiSwapThread+0x266
    8db1f438 82ca140f 855ae798 855ae858 00000000 nt!KiCommitThreadWait+0x1df
    8db1f4b4 8bc3ec68 8db1f4f8 00000000 00000000 nt!KeWaitForSingleObject+0x393
    8db1f4d8 9e6d783c 8db1f4f8 00000000 85692000 ndis!NdisWaitEvent+0x55
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8db1f510 9e6d7760 8571f000 8db1f520 00080050 rt73+0x1383c
    8db1f588 9e6d6e83 8571f000 00000000 00000040 rt73+0x13760
    8db1f5b4 9e6d596f 8571f000 00000800 9e6f5980 rt73+0x12e83
    8db1f5fc 9e6d66ec 8571f000 00000000 00000000 rt73+0x1196f
    8db1f61c 8bcb1246 8db1f67c 8db1f6e0 8bc76a98 rt73+0x126ec
    8db1f8f4 8bcb0aea 8567eda8 856920e0 880749a8 ndis!ndisMInitializeAdapter+0x649
    8db1f92c 8bcb0963 8567eda8 85692028 8567d628 ndis!ndisInitializeAdapter+0x10a
    8db1f954 8bcad247 85692028 8756f560 8756f584 ndis!ndisPnPStartDevice+0x130
    8db1f998 82c764bc 85692028 8756f460 8db1fa20 ndis!ndisPnPDispatch+0x62f
    8db1f9b0 82de2d7c 00000000 8562a030 85634568 nt!IofCallDriver+0x63
    8db1f9cc 82c4e479 8db1f9fc 82c4db67 85634568 nt!PnpAsynchronousCall+0x92
    8db1fa30 82de8bf8 82c4db67 85634568 8568ae78 nt!PnpStartDevice+0xe1
    8db1fa8c 82de8ac1 85634568 00000023 00000000 nt!PnpStartDeviceNode+0x12c
    8db1faa8 82de18bd 00000000 00000000 88025308 nt!PipProcessStartPhase1+0x62
    8db1fca4 82ddb636 86bd47d8 88025308 8db1fcd0 nt!PipProcessDevNodeTree+0x188
    8db1fcd8 82c4df7f 82d9dea0 855ae798 82d745bc nt!PiProcessReenumeration+0x74
    8db1fd00 82ca808b 00000000 00000000 855ae798 nt!PnpDeviceActionWorker+0x224
    8db1fd50 82e48a55 00000001 a397d49c 00000000 nt!ExpWorkerThread+0x10d
    8db1fd90 82cfa239 82ca7f7e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .thread 0xffffffff855ae798 ; kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        82ca1c9f - nt!SwapContext_PatchXSave+2
        [ 01:21 ]
        82ca1eed - nt!EnlightenedSwapContext_PatchXSave+2 (+0x24e)
        [ 01:21 ]
    2 errors : !nt (82ca1c9f-82ca1eed)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT_LARGE
    
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    Followup: memory_corruption
    ---------
      My Computer


  3. Posts : 33
    Windows 7
    Thread Starter
       #3

    Ok will do.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:47.
Find Us