windows 7 crash again. Bluescreen


  1. Posts : 2
    windows 7. 64bit
       #1

    windows 7 crash again. Bluescreen


    here is dump file check it ty.
      My Computer


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

    robero said:
    here is dump file check it ty.

    Easy

    Sptd.sys. Used by daemon tools and alcohol120

    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


    SPTD may also be causing this memory corruption. Run a memtory test to be sure.

    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\120210-19952-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: C:\symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea0e50
    Debug session time: Thu Dec  2 07:12:07.364 2010 (GMT-5)
    System Uptime: 0 days 0:00:08.049
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc000001d, fffff88003f18176, fffff880009a93a8, fffff880009a8c10}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    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: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff88003f18176, The address that the exception occurred at
    Arg3: fffff880009a93a8, Exception Record Address
    Arg4: fffff880009a8c10, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    
    FAULTING_IP: 
    tdx!TdxInitializeNaClientModule+76
    fffff880`03f18176 c5              ???
    
    EXCEPTION_RECORD:  fffff880009a93a8 -- (.exr 0xfffff880009a93a8)
    ExceptionAddress: fffff88003f18176 (tdx!TdxInitializeNaClientModule+0x0000000000000076)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    CONTEXT:  fffff880009a8c10 -- (.cxr 0xfffff880009a8c10)
    rax=0000000000000000 rbx=00000000000007ff rcx=fffff88003f1c5d0
    rdx=0000000000000000 rsi=0000000000000000 rdi=fffff880009a96b0
    rip=fffff88003f18176 rsp=fffff880009a95e0 rbp=0000000000000000
     r8=0000000000010478  r9=0000000000000020 r10=fffff80002c63000
    r11=0000000000000683 r12=fffff88003f1c110 r13=ffffffff80000060
    r14=fffffa8004944990 r15=000000000000001c
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    tdx!TdxInitializeNaClientModule+0x76:
    fffff880`03f18176 c5              ???
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    BUGCHECK_STR:  0x7E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    
    LAST_CONTROL_TRANSFER:  from fffff88003f1858a to fffff88003f18176
    
    FAILED_INSTRUCTION_ADDRESS: 
    tdx!TdxInitializeNaClientModule+76
    fffff880`03f18176 c5              ???
    
    STACK_TEXT:  
    fffff880`009a95e0 fffff880`03f1858a : 00000000`000007ff 00000000`00000000 00000000`00000000 fffff800`030a9994 : tdx!TdxInitializeNaClientModule+0x76
    fffff880`009a9610 fffff880`03f1921d : 00000000`00000000 fffffa80`04d03000 fffff880`009a9838 fffffa80`039d4b60 : tdx!TdxInitializeModule+0x1ea
    fffff880`009a96b0 fffff800`030bb917 : fffffa80`04cfb270 fffffa80`04d03000 00000000`00000000 00000000`000007ff : tdx!DriverEntry+0xdd
    fffff880`009a96e0 fffff800`03200ad6 : fffffa80`04c47618 fffffa80`04c47618 fffffa80`04c475d0 fffff8a0`00000016 : nt!IopLoadDriver+0xa07
    fffff880`009a99b0 fffff800`03201c92 : fffff800`00000000 fffff8a0`003fd4e0 ffffffff`80000064 fffff8a0`00154fe0 : nt!IopInitializeSystemDrivers+0x1d6
    fffff880`009a9a40 fffff800`03204cec : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`008131b0 : nt!IoInitSystem+0x9b2
    fffff880`009a9b40 fffff800`031558c9 : 00000000`00000000 fffffa80`039d4b60 00000000`00000080 fffffa80`039d4040 : nt!Phase1InitializationDiscard+0x129c
    fffff880`009a9d10 fffff800`02f77c06 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`02cb1c19 : nt!Phase1Initialization+0x9
    fffff880`009a9d40 fffff800`02cb1c26 : fffff800`02e4de80 fffffa80`039d4b60 fffff800`02e5bc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a79e0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !tdx
    2 errors : !tdx (fffff88003f18176-fffff88003f18c36)
    fffff88003f18170  5c  44  00  00  33  d2 *c5  05  88  44  00  00  01  00  00  00 \D..3....D......
    ...
    fffff88003f18c30  31  80  79  29  05  72 *29  0f  ba  61  2c  09  73  24  48  8b 1.y).r)..a,.s$H.
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  STRIDE
    
    STACK_COMMAND:  .cxr 0xfffff880009a8c10 ; kb
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    Followup: memory_corruption
    ---------
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.


    Ken J
      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 08:58.
Find Us