这个：
错误类型 ： Windows 停止错误（蓝屏上出现一条消息，显示错误代码信息）
是否有解决方案可用？ ： 无（参见“后续步骤”）
此错误意味着什么？ ： Windows 遇到无法恢复的错误，需要重新启动
原因 ： 未知设备驱动程序
计算机症状 ： 蓝屏上出现一条消息，显示错误代码信息（例如： 0x0000001E、KMODE_EXCEPTION_NOT_HANDLED）
要采取的其他步骤 ： 重要： 请继续发送错误报告，以便 Microsoft 的分析师可以研究并尝试尽快纠正该问题

经常重启，然后说电脑系统已经从一个严重错误中恢复。
为什么啊，那里出了问题，该怎么解决啊，谢谢了~~
--------------------------------------------------------------

你说的那些是在系统日志里看到的吧.这些信息都没什么用,真正有用的是蓝屏上显示的数据,有时候会显示有问题的文件.五个数据非常关键,形如0xXXXXXXXX(0xXXXXXXXX,0xXXXXXXXX,0xXXXXXXXX,0xXXXXXXXX).
如果你忘了蓝屏上显示的数据.最好是能有MiniDump文件,默认是在C:\\Windows\\MiniDump文件夹下,命名方式为"月日年_序号.DMP"的文件,找一个最新的用Windbg打开就可以看到有问题的设备.如果你不会用WinDbg,可以把DMP文件发到我邮箱里.longwangdage@163.com
另有来自WINDOWS DDK的帮助如下:
Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
The KMODE_EXCEPTION_NOT_HANDLED bug check has value 0x0000001E. This signals that a kernel-mode program generated an exception which the error handler did not catch.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Exception code that was not handled
2 Address at which exception occurred
3 Parameter 0 of exception
4 Parameter 1 of exception

Cause
To interpret this error message, it is necessary to 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, which 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 DDK.

Resolving the Problem
As this bug check often does not display full stack information, obtaining a stack trace can be difficult. 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 on the Microsoft Windows Hardware Compatibility List (HCL).

Buggy device driver or system service. In addition, a bug-ridden 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 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. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.