Windows 7 startup error with ci.dll / ntoskrnl.exe

Windows 7 cannot start up and system recovery options cannot repair automatically. It looks like ci.dll and ntoskrnl.exe is causing the issue. I have run System File Checker (sfc.exe) on all Windows startup files and everything checks out okay.

Here is the log data from Windows\minidump :

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size
123112-136610-01.dmp 12/31/2012 8:27:03 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000006 fffff800`0346f7ef fffff880`054da7e8 fffff880`054da040 CI.dll CI.dll+16bbf Code Integrity Module Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385  x64 ntoskrnl.exe+5f7ef         F:\Windows\MiniDump\123112-136610-01.dmp 4 15 7601 281,744
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path
ntoskrnl.exe ntoskrnl.exe+5f97e fffff800`03410000 fffff800`039f8000 0x005e8000 0x4fa390f3 5/4/2012 3:18:59 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17835 (win7sp1_gdr.120503-2030) Microsoft Corporation F:\Windows\system32\ntoskrnl.exe


Any ideas on how to get this back up without having to re-install Windows 7?

Thanks!

Hi,

ntoskrnl.exe is a Windows component which means something else drove it into Fault.

Check these KB articles :

"Stop 0x0000007E" or "Stop 0x00000050" Stop error message in Windows 7 or Windows Server
2008 R2
http://support.microsoft.com/kb/979538 

"Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" error when the GPU
is under heavy load conditions in Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/983615

---------------------------------------------------------------------------------------------

Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.
http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7 

See this thread for information on using BlueScreenView, MyEventViewer, and other methods
to troubleshoot BlueScreens - top 3 replies (+1 other).

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

We can analyze the minidumps if you make them available from the SkyDrive or other
file sharing sites (such as MediaFire). If you have problems uploading the minidumps
copy them to the Desktop or the Documents folder and upload them from there.

Zip or upload the contents of C:\Windows\minidump

Use SkyDrive to upload collected files.
http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 

---------------------------------------------------------------------------------------------

References to Vista also apply to Windows 7.

BCCode: 7E      0x0000007E  which is also 0x1000007E

This error is usually a driver issue and display adapter (video) driver is the most suspect
though it could be others. Antivirus/antispyware/security programs, hardware (heat) and
major software issues can also cause the error. When you get to the driver section of the
troubleshooter use my generic methods in the next message and then return to the
troubleshooter if needed.

Have you added hardware recently or updated drivers? Be sure to look in Control Panel -
Windows Updates to see if any drivers were updated there. Other lessor possibilities
include antivirus/anti-spyware/security programs.

When you get to the driver and memory sections of the troubleshooter refer to the next
message to update drivers and test memory and then refer back to the troubleshooter
if needed.

=======================================================

BCCode: 7E      0x0000007E  which is also 0x1000007E

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000007E. This bug check indicates that a system thread generated an exception that the error handler did not catch.

Important Info If You Have Received a STOP Code

If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.


If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.


These actions might prevent an error like this from happening again:

  1. Download and install updates and device drivers for your computer from Windows Update.
  2. Scan your computer for computer viruses.
  3. Check your hard disk for errors.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Parameters


The following parameters appear on the blue screen.

Cause

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include the following:

  • 0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.

  • 0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

  • 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.

For a complete list of exception codes, see the Ntstatus.h file that is located in the inc directory of the Microsoft Windows Driver Kit (WDK).

Resolution

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.

  • Make sure you have enough disk space.

  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

  • Try changing video adapters.

  • Check with your hardware vendor for any BIOS updates.

  • Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.


If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is started with the /DEBUG switch.


If exception code 0x80000002 occurs, the trap frame supplies additional information.


If you do not know the specific cause of the exception, consider the following issues:

  • Hardware incompatibility. Make sure that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.

  • Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you must start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E. 

You can also disable memory caching of the BIOS might to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.

BCCode: 7E    0x00000007E  which is also 0x1000007E <-- read this link
http://www.faultwire.com/solutions-fatal_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-*1141.html?order=votes 

===============================================================

Look in the Event Viewer to see if anything is reported about those.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.
TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.

http://www.nirsoft.net/utils/my_event_viewer.html

---------------------------------------------------------------

Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen
info that would help. Such as the BCC and the other 4 entries on the lower left. And any other
error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or
PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000


This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death'
crashes, and displays the information about all crashes in one table - Free
http://www.nirsoft.net/utils/blue_screen_view.html


Many BlueScreens are caused by old or corrupted drivers, especially video drivers however
there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or
Recovery Options if your system has that installed by the maker.

How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Windows 7
http://www.sevenforums.com/tutorials/700-system-restore.html

-------------------------------------------------------------------------

Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to Repair Windows 7 System Files with System File Checker
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log (and Windows 7)
http://support.microsoft.com/kb/928228


The log might give you the answer if there was a corrupted driver. (Does not tell all the possible
driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.

How to Run Check Disk at Startup in Windows 7
http://www.sevenforums.com/tutorials/433-disk-check.html

-------------------------------------------------------------------------

Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
is preferred to ensure the latest drivers from System maker and Device makers are found)
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

Stop Windows 7 from Automatically Installing Device Drivers
http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/


How To Disable Automatic Driver Installation In Windows 7 / Vista
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for Professional,
Ultimate, and Enterprise)
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

-------------------------------------------------------------------------

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
unexpectedly
http://support.microsoft.com/kb/958233

Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)
http://www.chicagotech.net/vista/vistabluescreen.htm

Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692

Windows - Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033

-------------------------------------------------------------------------

In some cases this might be required.

StartUp Repair from Recovery Options or Windows 7 disk

How to Run a Startup Repair in Windows 7
http://www.sevenforums.com/tutorials/681-startup-repair.html


How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html


How to Create a Windows 7 System Repair Disc
http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html


How to Do a Repair Install to Fix Windows 7
http://www.sevenforums.com/tutorials/3413-repair-install.html

Hope this helps.


Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

Rob Brown - past Microsoft MVP - Windows Insider MVP 2016 - 2021
Microsoft MVP Windows and Devices for IT 2009 - 2020

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

References to Vista also apply to Windows 7.

This is my generic how to for proper driver updates : (Check for BIOS and driver
updates.)

This utility makes it easy to see which versions are loaded :

DriverView - Free - utility displays the list of all device drivers currently loaded on
your system. For each driver in the list, additional useful information is displayed:
load address of the driver, description, version, product name, company that
created the driver, and more.
http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the
most current. Control Panel - Device Manager - Display Adapter - write down the
make and complete model of your video adapter - double click - Driver's tab -
write down the version info. Now click UPdate Driver (this may not do anything
as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this
will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard
if 3rd party with their own software and drivers and any other major device drivers
you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback)
and then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get
their latest versions. (Look for BIOS, Chipset and software updates at System
 Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -
REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are
installing actually shows up. This is because some drivers rollback before the
latest is installed (sound drivers particularly do this) so install a driver - reboot
- check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR
SCANNER - check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

Installing and updating drivers in Windows 7 (updating drivers manually using
the methods above is preferred to ensure the latest drivers from System maker
and Device makers are found)
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

If you update drivers manually then it is a good idea to disable Driver Installations
in Windows Updates, this leaves Windows Updates ON however it will not install
drivers which will usually be older and cause issues. If Updates suggests a new
driver then HIDE it (Right Click on it) and then go look for new ones manually if
you wish.

Stop Windows 7 from Automatically Installing Device Drivers
http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/


How To Disable Automatic Driver Installation In Windows 7 / Vista
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for
Professional, Ultimate, and Enterprise)
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

==========================================

Memory tests do not catch all errors such as mismatched memory (possible
even for sticks that appear to be identical) and when faster memory is placed
in system behind slower  memory. So it is best to also swap sticks in and out
to check for those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so.  <-- best method
www.memtest.org

For the Vista/Windows 7 Memory Diagnostic Tool

Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list
- Right Click - RUN AS ADMIN follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista
Memory Diagnostic Tool
http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

How to Run the Memory Diagnostics Tool in Windows 7
http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Hope this helps.


Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

Rob Brown - past Microsoft MVP - Windows Insider MVP 2016 - 2021
Microsoft MVP Windows and Devices for IT 2009 - 2020

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated February 5, 2020 Views 4,135 Applies to: