Windows crashed + dump file inside


  1. Posts : 11
    WIN 7
       #1

    Windows crashed + dump file inside


    Hi guys,

    i come to you after formating my computer and without success to solve my blue screens problem.

    when i watch a movie and specially while playing i get a blue screen
    i attached the dump file.

    thanks a lot!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    shiker said:
    Hi guys,

    i come to you after formating my computer and without success to solve my blue screens problem.

    when i watch a movie and specially while playing i get a blue screen
    i attached the dump file.

    thanks a lot!
    SPDT.SYS used by daemon tools/alcohol and KeyMagic. Both.

    Your computer was up for 2 plus days so it isnt happening frequently, and removing those two items may fix it.


    Ken J

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    [/quote]
    You can use MagicDisc as an alternative.

    Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\dump_110310-26083-01.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;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x82a19000 PsLoadedModuleList = 0x82b61810
    Debug session time: Tue Nov  2 18:46:53.808 2010 (GMT-4)
    System Uptime: 2 days 0:45:47.338
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    Loading unloaded module list
    ..........................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {82bf636f, 2, 8, 82bf636f}
    
    Unable to load image \SystemRoot\system32\DRIVERS\KeyMagic.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for KeyMagic.sys
    *** ERROR: Module load completed but symbols could not be loaded for KeyMagic.sys
    Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : KeyMagic.sys ( KeyMagic+2f1b )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 82bf636f, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000008, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 82bf636f, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82b81718
    Unable to read MiSystemVaType memory at 82b61160
     82bf636f 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!IoIsWdmVersionAvailable+0
    82bf636f 8bff            mov     edi,edi
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  vlc.exe
    
    TRAP_FRAME:  8078a9f8 -- (.trap 0xffffffff8078a9f8)
    ErrCode = 00000010
    eax=00000000 ebx=77f519c8 ecx=880ae102 edx=00000000 esi=89cac008 edi=880ae7f8
    eip=82bf636f esp=8078aa6c ebp=8078aa80 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!IoIsWdmVersionAvailable:
    82bf636f 8bff            mov     edi,edi
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82bf636f to 82a5f82b
    
    FAILED_INSTRUCTION_ADDRESS: 
    nt!IoIsWdmVersionAvailable+0
    82bf636f 8bff            mov     edi,edi
    
    STACK_TEXT:  
    8078a9f8 82bf636f badb0d00 00000000 880ae102 nt!KiTrap0E+0x2cf
    8078aa68 92315f1b 00000006 00000000 00000000 nt!IoIsWdmVersionAvailable
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8078aa80 83644217 77c6f6c0 77f4e290 8078aaa4 KeyMagic+0x2f1b
    8078aacc 83644325 88390938 880b1d68 83676a8c Wdf01000!FxRequestBase::CompleteSubmittedNoContext+0x63
    8078aae8 83628c36 880b8d50 880b1d68 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0x104
    8078ab04 83628cde 01390938 86a99e78 8078ab3c Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
    8078ab14 82aa28b6 880b1ef0 880b8d50 88390938 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
    8078ab3c 82a81b33 880b1ef0 880b8d50 86a99e78 nt!IopUnloadSafeCompletion+0x45
    8078ab80 92234272 00000000 8078aba8 922342b7 nt!IopfCompleteRequest+0x128
    8078ab8c 922342b7 880314b8 880b8d50 880b8d50 bthport!BthCompleteRequestEpilogue+0x38
    8078aba8 9225e388 880314b8 880b8d50 00000000 bthport!BthCompleteRequestEx+0x27
    8078abd4 9225abf9 87fa72e0 0178acbc 8819d858 bthport!L2Cap_CompleteReadIrpList+0x8c
    8078acc8 9223d12a 87fa72e0 0119a958 0019d858 bthport!L2CapInt_ProcessReadBip+0x2b3
    8078ad08 9223cc8b 88032930 881f1f78 0019a8f8 bthport!HCI_ProcessAclReadBip+0x45e
    8078ad38 92257ca4 88032930 00000000 00000012 bthport!HCI_ProcessAclRead+0x18d
    8078ad5c 92236122 88032930 8838b870 8838b870 bthport!HCI_ProcessMpBip+0x60
    8078ad70 8fdee80a 8838b870 82e2c7a0 87ff9d70 bthport!BTHPORT_RecvMpBip+0x38
    8078ad8c 8fdf3910 8803a008 85a00000 00000012 BTHUSB!BthUsb_ReadTransferComplete+0x9e
    8078ade4 8fdf3d13 88031400 8078ae00 869598af BTHUSB!UsbWrapWorkRoutine+0xce
    8078ae0c 82a81b33 88031400 869596f8 01000003 BTHUSB!UsbWrapInterruptReadComplete+0x11d
    8078ae54 8fc2c868 82a59354 89d8ed08 00000000 nt!IopfCompleteRequest+0x128
    8078ae84 8fc2d178 b855a9b0 869596f8 87ff9a80 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
    8078aeb0 8fc309af 8682e028 8682e0f0 8682ea98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
    8078aed8 8fc2ad18 8682e028 8682ea98 8682e002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
    8078aefc 836af894 8682eaa4 8682e002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
    8078af48 82a813b5 8682eaa4 8682ea98 00000000 sptd+0x11894
    8078afa4 82a81218 82b42d20 db9813e8 00000000 nt!KiExecuteAllDpcs+0xf9
    8078aff4 82a809dc a3460ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
    8078aff8 a3460ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
    82a809dc 00000000 0000001a 00d6850f bb830000 0xa3460ce4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    KeyMagic+2f1b
    92315f1b ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  KeyMagic+2f1b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: KeyMagic
    
    IMAGE_NAME:  KeyMagic.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49c160e8
    
    FAILURE_BUCKET_ID:  0xA_CODE_AV_BAD_IP_KeyMagic+2f1b
    
    BUCKET_ID:  0xA_CODE_AV_BAD_IP_KeyMagic+2f1b
    
    Followup: MachineOwner
    ---------
    Old drivers
    Code:
    lmimirr.sys        0x90fa5c80    0x00000c80    4/10/2007 18:32:11            0x461c106b    0x90fa5000                
    RaInfo.sys        0x99bc5800    0x00001800    1/4/2008 14:57:12            0x477e8188    0x99bc4000                
    nvmfdx32.sys        0x8fd9fe00    0x000fee00    7/8/2008 05:17:12            0x48733098    0x8fca1000                
    LMIRfsDriver.sys        0x99bd0000    0x0000a000    7/14/2008 12:26:22            0x487b7e2e    0x99bc6000                
    nvsmu.sys        0x9021b000    0x00009000    7/22/2008 13:21:06            0x48861702    0x90212000                
    KeyMagic.sys    KeyMagic.sys+2f1b    0x9231e000    0x0000b000    3/18/2009 17:00:24            0x49c160e8    0x92313000                
    spldr.sys        0x8b664000    0x00008000    5/11/2009 12:13:47            0x4a084ebb    0x8b65c000
      My Computer


  3. Posts : 11
    WIN 7
    Thread Starter
       #3

    thanks a lot for the quick response !
    i removed the deamon tools and sptd from my computer.
    is magiciso going to do the same as demon tools, i'm not goona have any trouble loading games thourgh it ?

    about the old drivers, i downloaded driver detective and he told me that only the
    atheros ar928x driver need to be updated and i update him.
    the rest of the "old drivers" are windows drivers, logmein and apple's shi** :)

    i'll check the games and report back thanks!

    thanks! :)
    Last edited by shiker; 05 Nov 2010 at 17:09.
      My Computer


  4. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #4

    Shiker, we don't recommend using a driver program. Go to the websites of the manufactures and get your drivers from there. Regardless of what Driver Detective said, those drivers Ken listed are out of date. Outdated drivers can and do cause conflicts and BSOD's.
      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 00:27.
Find Us