Driver Used Excessive PTEs (stop code 0X000000D8)
Causes and remedies are similar to ???No More System PTEs (stop code
0X0000003F),??? later in this section.
Hardware Interrupt Storm (stop code 0X000000F2)
This error occurs when a hardware device (such as a USB or SCSI controller)
fails to release an IRQ, a condition typically caused by a buggy
driver or firmware. This error can also appear if two devices are incorrectly
assigned the same IRQ (discussed later in this chapter).
Inaccessible Boot Device (stop code 0X0000007B)
You may see this error during Windows startup if Windows cannot read
data from the system or boot partitions (described in Chapter 1). Faulty
disk controller drivers are often to blame, but this problem can also be
caused by hard disk errors, or even a corrupted boot.ini file (also
described in Chapter 1).
If all is well with your drivers and your drive, and you haven??™t been
messing with the boot.ini file (such as while installing multiple operating
systems), check your system BIOS settings (described in
Appendix A).
If you encounter this message while upgrading to Windows Vista (see
Chapter 1), it may mean that one or more devices in your system are not
compatible with Vista. Try disconnecting unnecessary devices, or at
least look for updated drivers and firmware. Also, disable any antivirus
software you may have running.
Kernel Data Inpage Error (stop code 0X0000007A)
This error implies a problem with virtual memory (discussed in
Chapter 5), most often in the case that Windows wasn??™t able to read
data from??”or write data to??”the swap file.
Pages:
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439