BSOD Help!!!

Page 1 of 2 12 LastLast

  1. Posts : 14
    Windows 7 Ultimate 32bit
       #1

    BSOD Help!!!


    My Computer Config is
    OS : Windows 7 Ultimate
    RAM : DDR2 2 GB
    Processor : Intel Core2Duo @ 2.20 Ghz
    Graphic Card : Nvidia 9500 GT 1 GB
    Power Supply : 450W-P4

    Is the above config Ok to run...


    Error Report
    Source
    Windows

    Summary
    Shut down unexpectedly

    Date
    ‎9/‎28/‎2011 3:45 PM

    Status
    Not reported

    Problem signature
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Files that help describe the problem (some files may no longer be available)
    092811-23197-01.dmp
    sysdata.xml

    Extra information about the problem
    BCCode: 51
    BCP1: 00000001
    BCP2: 8961A4E0
    BCP3: 00ABF000
    BCP4: 00000374
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1
    Last edited by deep2sunny; 01 Oct 2011 at 05:14. Reason: Attachement
      My Computer


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

    Update the Nvidia driver, yours is outdated
    Its DirectX component was involved in the crashes
    NVIDIA DRIVERS 280.26 WHQL
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (appears to be on
        stack that was unwound)
    Arg2: 875184f0, IOSB address
    Arg3: 8a3e9c28, IRP address
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_c
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  c
    
    IOSB_ADDRESS: ffffffff875184f0
    
    IRP_ADDRESS:  003e9c28
    
    DEVICE_OBJECT: 8f1c7500
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1
    
    LOCK_ADDRESS:  82984f60 -- (!locks 82984f60)
    
    Resource @ nt!PiEngineLock (0x82984f60)    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  : 0x82984f60
        Thread Count  : 0
        Thread address: 0x00000000
        Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from 82b4e9f1 to 828fbd10
    
    STACK_TEXT:  
    87518688 82b4e9f1 000000c9 0000000c 875184f0 nt!KeBugCheckEx+0x1e
    875186a8 828c115d a3a7280d 849b54c0 8a3e9c68 nt!IovpCompleteRequest+0x3c
    875186ec 828c6fa9 003e9c68 87518718 87518724 nt!IopCompleteRequest+0x4a
    8751873c 8288dafd 00000000 00000000 00000000 nt!KiDeliverApc+0x111
    87518780 8288c403 849b5580 849b54c0 8751887c nt!KiSwapThread+0x24e
    875187a8 828862cf 849b54c0 849b5580 00000000 nt!KiCommitThreadWait+0x1df
    87518824 82b599b3 8751887c 00000000 00000000 nt!KeWaitForSingleObject+0x393
    87518854 8e964ad8 8751887c 00000000 00000000 nt!VerifierKeWaitForSingleObject+0xfe
    87518894 8e964455 89f39b60 8e921494 00000020 dxgkrnl!DpiQueryBusInterface+0x93
    87518960 8283378f 8a3e9af0 89f39b60 89f36378 dxgkrnl!DpiAddDevice+0x594
    8751897c 829ce7b3 89f39b60 8e963ec1 00000004 nt!PpvUtilCallAddDevice+0x45
    875189c4 829c72ea 8a3e9af0 8e963ec1 00000002 nt!PnpCallAddDevice+0xb9
    87518a98 829c6876 89f36378 87518cc8 00000000 nt!PipCallDriverAddDevice+0x565
    87518c94 829aaa2a 849c5620 8c8fd210 87518cc8 nt!PipProcessDevNodeTree+0x15d
    87518cd4 82832f99 8c8fd210 82982e80 849b54c0 nt!PiProcessStartSystemDevices+0x6d
    87518d00 8288cf2b 00000000 00000000 849b54c0 nt!PnpDeviceActionWorker+0x241
    87518d50 82a2d66d 00000001 a3a72371 00000000 nt!ExpWorkerThread+0x10d
    87518d90 828df0d9 8288ce1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgkrnl!DpiQueryBusInterface+93
    8e964ad8 8bd8            mov     ebx,eax
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  dxgkrnl!DpiQueryBusInterface+93
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc297
    
    FAILURE_BUCKET_ID:  0xc9_c_VRF_dxgkrnl!DpiQueryBusInterface+93
    
    BUCKET_ID:  0xc9_c_VRF_dxgkrnl!DpiQueryBusInterface+93
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #3

    You guys are awsome i didn't install the drivers of Nvidia or rather updated them but how did u come to know about this
      My Computer


  4. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #4

    One more blue screen


    I've updated my graphic card drivers but yet again one more blue screen in the morning. Check the mini dump file
      My Computer


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

    Dumps point to your RAM, your RAM stick may be defective
    Test it with Memtest www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

    Any errors detected in the test(red lines) would confirm the RAM problem
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 91a836f1, The address that the exception occurred at
    Arg3: 8b4477e0, Exception Record Address
    Arg4: 8b4473c0, 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: 
    dxgkrnl!DxgkCddEnable+fce
    91a836f1 8b09            mov     ecx,dword ptr [ecx]
    
    EXCEPTION_RECORD:  8b4477e0 -- (.exr 0xffffffff8b4477e0)
    ExceptionAddress: 91a836f1 (dxgkrnl!DxgkCddEnable+0x00000fce)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 00001000
    Attempt to read from address 00001000
    
    CONTEXT:  8b4473c0 -- (.cxr 0xffffffff8b4473c0)
    eax=861d8b00 ebx=8a0c8008 ecx=00001000 edx=8dc7b048 esi=8dc7707e edi=ffb895d8
    eip=91a836f1 esp=8b4478a8 ebp=8b447a78 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    dxgkrnl!DxgkCddEnable+0xfce:
    91a836f1 8b09            mov     ecx,dword ptr [ecx]  ds:0023:00001000=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  csrss.exe
    
    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:  00001000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82bba718
    Unable to read MiSystemVaType memory at 82b9a160
     00001000 
    
    FOLLOWUP_IP: 
    dxgkrnl!DxgkCddEnable+fce
    91a836f1 8b09            mov     ecx,dword ptr [ecx]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from 97752611 to 91a836f1
    
    STACK_TEXT:  
    8b447a78 97752611 40000000 00000000 8b447d28 dxgkrnl!DxgkCddEnable+0xfce
    8b447ac0 00000000 00000000 00000040 0000000c cdd!CreateAndEnableDevice+0x171
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgkrnl!DxgkCddEnable+fce
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc297
    
    STACK_COMMAND:  .cxr 0xffffffff8b4473c0 ; kb
    
    FAILURE_BUCKET_ID:  0x7E_dxgkrnl!DxgkCddEnable+fce
    
    BUCKET_ID:  0x7E_dxgkrnl!DxgkCddEnable+fce
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #6

    how much time will it take to complete the test
      My Computer


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

    deep2sunny said:
    how much time will it take to complete the test
    6-7 Passes usually take around 4+ Hours, so it would be better to leave the test running overnight :)
      My Computer


  8. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #8

    Plz check this dump file also


    One more BSOD. How do u decode BSOD codes
      My Computer


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

    deep2sunny said:
    One more BSOD. How do u decode BSOD codes
    This dumps points to ccHPx86.sys, used by a Symantec/Norton product
    You seem to be using an old Norton product, please uninstall it and use the latest version
    Dumps are analyzed using the Windows Debugging Tools
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 1, aa1128e4, 0}
    
    *** WARNING: Unable to verify timestamp for ccHPx86.sys
    *** ERROR: Module load completed but symbols could not be loaded for ccHPx86.sys
    *** WARNING: Unable to verify timestamp for SYMEFA.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEFA.SYS
    Probably caused by : ccHPx86.sys ( ccHPx86+191cd )
    
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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: 00000001, The address that the exception occurred at
    Arg3: aa1128e4, Trap Frame
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    +12a
    00000001 ??              ???
    
    TRAP_FRAME:  aa1128e4 -- (.trap 0xffffffffaa1128e4)
    ErrCode = 00000010
    eax=86f6c13c ebx=00000000 ecx=86f6c170 edx=00000000 esi=86f6c170 edi=9035f906
    eip=00000001 esp=aa112958 ebp=aa1129b4 iopl=0         nv up ei ng nz ac po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010292
    00000001 ??              ???
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  ccsvchst.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 87f09500 to 00000001
    
    STACK_TEXT:  
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    aa112954 87f09500 00000008 86f6c13c 9033483d 0x1
    aa1129b4 903301cd 00000000 85858a40 aa1129f4 0x87f09500
    aa1129fc 90319219 85858a40 00000080 aa112a38 ccHPx86+0x191cd
    aa112a60 90319721 99308208 993081e0 00000000 ccHPx86+0x2219
    aa112a94 88a96acd 99308208 00000000 00000001 ccHPx86+0x2721
    aa112ad0 88a9b535 00000000 99308138 993081dc SYMEFA+0x1bacd
    aa112af4 88a9acc0 99308138 88a83020 99308138 SYMEFA+0x20535
    aa112b30 88a97cd2 84a217b0 84a21740 00226004 SYMEFA+0x1fcc0
    aa112bdc 88a85a15 84a21740 84c3eac0 85568868 SYMEFA+0x1ccd2
    aa112bfc 82a874bc 85568868 84a21740 84a21740 SYMEFA+0xaa15
    aa112c14 82c88eee 84c3eac0 84a21740 84a217b0 nt!IofCallDriver+0x63
    aa112c34 82ca5cd1 85568868 84c3eac0 00000000 nt!IopSynchronousServiceTail+0x1f8
    aa112cd0 82ca84ac 85568868 84a21740 00000000 nt!IopXxxControlFile+0x6aa
    aa112d04 82a8e42a 00003034 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
    aa112d04 776a64f4 00003034 00000000 00000000 nt!KiFastCallEntry+0x12a
    0089e464 00000000 00000000 00000000 00000000 0x776a64f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ccHPx86+191cd
    903301cd ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  ccHPx86+191cd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ccHPx86
    
    IMAGE_NAME:  ccHPx86.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b6c8632
    
    FAILURE_BUCKET_ID:  0x8E_ccHPx86+191cd
    
    BUCKET_ID:  0x8E_ccHPx86+191cd
    
    Followup: MachineOwner
    ---------
      My Computer


  10. Posts : 14
    Windows 7 Ultimate 32bit
    Thread Starter
       #10

    no i'm using Norton 360 30 days trial version updated to latest virus definitions. How can Windows 7 be so delicate? How can it go weak at such small issues?
      My Computer


 
Page 1 of 2 12 LastLast

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 15:44.
Find Us