BCCode: 1E 0x0000001E
Remove ALL power and reseat all the cards, memory, and cables (both ends when
possible) - 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
Cause
This is a very common bug check. To interpret it, you must identify which exception was generated.
Common exception codes include:
0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.
0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
0xC0000005: STATUS_ACCESS_VIOLATION
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 theinc directory of the Windows Driver Kit.
Resolution
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 listed in the Microsoft Windows Marketplace Tested Products List.
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.
BCCode: 1E 0x0000001E <-- read this link
http://www.faultwire.com/solutions-fatal_error/Check-to-be-sure-you-have-adequate-disk-space-0x0000001E-*1045.html
======================================================================
Driver Verifier can help find some BSOD issues :
Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617
How To Troubleshoot Driver Problems in Windows Vista or 7.
http://www.winvistaclub.com/t79.html
Using Driver Verifier
http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx
How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM