BlueScreen Error for Win7; STOP: 0x0000001E

 Dear Reader,

 I have recently purchased a used Toshiba Satellite, which I believe was upgraded from Vista to Win7 because it has a Vista sticker but on startup it says Windows 7 Home Premium. I was told that the battery life is uncertain. From experience, I saw the battery go from around 60% to 3%. I was updating something, I can't remember the name of it, and my laptop turned off. I immediately plugged in the laptop charger and turned the laptop back on. Every time I start the laptop I receive a blue screen after I sign in or before I sign in. At the bottom of the screen it says "Technical Information: *** STOP: 0x0000001E (0x0000000000000000, 0x0000000000000000, 0x0000000000000000) I can't run windows normally without the error. I am currently on Safe Mode with Networking. During start up I go to advanced options and the option at the top, can't remember the name, It says It will try to fix what's causing windows to shut down. That doesn't work, I've tried using windows recovery, that doesn't work, I get errors. Something popped up earlier saying, "

Problem Event Name: BlueScreen

OS Version: 6.1.7601.

Locale ID: 1033


BCP1: fffff8811500C878

BCP2: 0000000000000000

BCP3: fffff8800195CAB0

BCP4: 0000000000000005

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1


Methods to troubleshoot :

Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows. 

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

We can analyze the minidumps if you make them available from the OneDrive 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.

Adding files to your OneDrive

One-Drive - Share files and folders and change permissions

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

Use OneDrive to upload collected files


BCCode: 1E   0x0000001E 

Remove ALL power and reseat all the cards, memory, and cables (both ends when
- actually remove and replace - do not just snug. Those are for a PC and about all
that can be done for a laptop is reseat the memory and clear the vents. Make sure the BIOS,
low level chipset drivers, and major device drivers are all up to date by check manually at the
makers' sites.

Many Bluescreens are caused by BIOS, low level chipset drivers, and other major device drivers
which are not the most current even though the computer is new. Check manually for updates
using the methods for updates as indicated in the troubleshooter linked above and/or the
methods below (which are the same).

BCCode: 1E   0x0000001E


The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which 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.

The following parameters are displayed on the blue screen.

Parameter Description


The exception code that was not handled


The address at which the exception occurred


Parameter 0 of the exception


Parameter 1 of the exception


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

Common exception codes include:


    An unaligned data reference was encountered.

  • 0x80000003: STATUS_BREAKPOINT

    A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.


    A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)

For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.


If you are not equipped to debug this problem
, you should use some basic troubleshooting techniques. 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 may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that 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 a kernel debugger is connected and the system is started with the /DEBUG switch.

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

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility.
First, make sure that any new hardware 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.
In addition, 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 need to 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, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on 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 a system BIOS incompatibility. BIOS problems can be resolved by upgrading the system BIOS version.

To get a stack trace if the normal stack tracing procedures fail

  1. Use the kb (Display Stack Backtrace) command to display parameters in the stack trace. Look for the call to NT!PspUnhandledExceptionInSystemThread. (If this function is not listed, see the note below.)

  2. The first parameter to NT!PspUnhandledExceptionInSystemThread is a pointer to a structure, which contains pointers to an except statement:
    typedef struct _EXCEPTION_POINTERS { PEXCEPTION_RECORD ExceptionRecord; PCONTEXT ContextRecord; } EXCEPTION_POINTERS, *PEXCEPTION_POINTERS; ULONG PspUnhandledExceptionInSystemThread( IN PEXCEPTION_POINTERS ExceptionPointers )

    Use the dd (Display Memory) command on that address to display the necessary data.

  3. The first retrieved value is an exception record and the second is a context record. Use the .exr (Display Exception Record) command and the .cxr (Display Context Record) command with these two values as their arguments, respectively.

  4. After the .cxr command executes, use the kb command to display a stack trace that is based on the context record information. This stack trace indicates the calling stack where the unhandled exception occurred.

Note  This procedure assumes that you can locate NT!PspUnhandledExceptionInSystemThread. However, in some cases (such as an access violation crash) you will not be able to do this. In that case, look for ntoskrnl!KiDispatchException. The third parameter passed to this function is a trap frame address. Use the .trap (Display Trap Frame) command with this address to set the Register Context to the proper value. You can then perform stack traces and issue other commands.

Here is an example of bug check 0x1E on an x86 processor:

Bug_Check 0x1E - read link for the example

BCCode: 1E   0x0000001E  <-- read this link*1045.html


Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users 

How To Troubleshoot Driver Problems in Windows Vista or 7. 

Using Driver Verifier 

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues


Driver Verifier 

Using Driver Verifier 

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues

You can disable Driver Verifier 

Start - type in Search box -> verifier /reset      hit enter to disable

Use BlueScreenView to see if there is a driver specified in the error message. Also check with
MyEventViewer at the time of the BlueScreen.

If DriverVerifier creates a minidump upload it and provide a link to it so we can analyze it.


References to Vista also apply to Windows 7.

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

This utility makes it easy to see which versions are loaded : Run DriverView - set VIEW
to Hide Microsoft drivers - update those without Dump in their names. (Also update
the BIOS and chipset drivers.)

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.

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

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.

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)

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.

How to stop Windows 7 automatically installing drivers


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

For the Windows 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

How to Run the Memory Diagnostics Tool in Windows 7

Hope this helps.

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

Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

1 person was helped by this reply


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

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

How satisfied are you with this response?

Thanks for your feedback.


Question Info

Last updated June 28, 2020 Views 6,708 Applies to: