locked
Automatically Restart Lead to Blue Screen RRS feed

  • Question

  • About one month ago, my Laptop (Lenovo T440s i7, Win8.1 pro) restart automatically and repair the system error below (1. SYSTEM_SERVICE-EXCEPTION(DI.DLL) AND 2. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED(CI.DLL)), which happens about several days a time.

    After that, the restating happened more frequently (about several hours a time) to repair itself.

    However, it cannot repair itself when it tries to repair itself and restart again when the repair process is at (0%, which was able to be down before, say, when it happened hours a time or days a time).

    After contacting with the Lenovo Tech Team, I set the OS Optimized Defaults to [Disabled] and F9 Setup Defaults, and backing up all my files, then try to reinstall the Win8.1, the original Win8.1 OS could start successfully without the blue Screen.

    One thing should mention is that when I try to install the Win8.1 through a bootable USB before setting the OS Optimized Defaults to [Disabled] and F9 Setup Defaults, it shows the same error and failed to install the Win8.1.

    Are there someone could tell what is wrong with my PC, I am afraid the error and Blue Screen will happen again... as I am using MSVC2013 to develop some thread related application without using the CI.DLL. Thanks in advance!!

    After using two hours, again, it restarts automatically, but without the Blue Screen. I think it will be more and more serious... as what happened before.


    YU Xinbo

    • Edited by Bruce Yo Thursday, May 21, 2015 9:58 AM
    Thursday, May 21, 2015 8:38 AM

Answers

  • These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.


    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not


    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)



    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Bruce Wooding Thursday, June 4, 2015 8:17 PM
    Friday, May 22, 2015 1:46 PM

All replies

  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Thursday, May 21, 2015 10:13 AM
  • Hello Moderator, thanks for your reply. Below are the details of two DMP files:

    1. //////////////////////////////////////////////////////////////////////////////////////////

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\bruce_000\Desktop\052115-26859-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *

    ////////////////////////////////////////////////////////////////////////////////////////

    Error info. is as below:


    YU Xinbo


    • Edited by ZigZag3143x Thursday, May 21, 2015 11:03 AM Clarity
    Thursday, May 21, 2015 10:50 AM
  • Hello Moderator, thanks for your reply. Below are the details of two DMP files:

    1. //////////////////////////////////////////////////////////////////////////////////////////

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\bruce_000\Desktop\052115-26859-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
    Machine Name:
    Kernel base = 0xfffff800`f3a02000 PsLoadedModuleList = 0xfffff800`f3cdb850
    Debug session time: Thu May 21 17:59:52.905 2015 (UTC + 8:00)
    System Uptime: 0 days 0:14:41.643
    *********************************************************************

    Probably caused by : CI.dll ( CI+62490 )

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

    ////////////////////////////////////////////////////////////////////////////////////////

    Error info. is as below:


    YU Xinbo


    • Edited by ZigZag3143x Thursday, May 21, 2015 11:05 AM Clarity
    Thursday, May 21, 2015 10:53 AM
  • Hello Moderator, thanks for your reply. Below are the details of two DMP files:

    1. //////////////////////////////////////////////////////////////////////////////////////////

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\bruce_000\Desktop\052115-26859-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
    Machine Name:
    Kernel base = 0xfffff800`f3a02000 PsLoadedModuleList = 0xfffff800`f3cdb850
    Debug session time: Thu May 21 17:59:52.905 2015 (UTC + 8:00)
    System Uptime: 0 days 0:14:41.643
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
                               *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
    Machine Name:
    Kernel base = 0xfffff801`81e04000 PsLoadedModuleList = 0xfffff801`820dd850
    Debug session time: Thu May 21 18:03:05.935 2015 (UTC + 8:00)
    System Uptime: 0 days 0:02:17.673
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................................................
    Loading User Symbols
    Loading unloaded module list
    ......................
    *******************************************************************************
    *                                                                             *

    Probably caused by : CI.dll ( CI+62490 )

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

    ////////////////////////////////////////////////////////////////////////////////////////

    Error info. is as below:


    YU Xinbo


    • Edited by ZigZag3143x Thursday, May 21, 2015 11:04 AM Clarity
    Thursday, May 21, 2015 10:55 AM
  • BY

    NO!!  We need the actual DMP file not what you are giving us.  We need the  files themselves


    Wanikiya and Dyami--Team Zigzag

    Thursday, May 21, 2015 11:02 AM
  • I use google drive to upload the dmp files in the link below:

    https://drive.google.com/folderview?id=0B8IuiXzC-U96VVFYQkV4dnNIZnM&usp=sharing

    Thanks! It restart automatically even without doing anything to the PC.


    YU Xinbo

    Thursday, May 21, 2015 3:52 PM
  • These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.


    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not


    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)



    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Bruce Wooding Thursday, June 4, 2015 8:17 PM
    Friday, May 22, 2015 1:46 PM
  • Hello Moderator, the problem is solved by replacing the RAM.

    I took my PC to Lenovo Service Center at last. It turns out to be the RAM fail. Many thanks for your help! I really appreciate it! 


    YU Xinbo



    • Edited by Bruce Yo Wednesday, May 27, 2015 7:11 AM
    Wednesday, May 27, 2015 7:11 AM