Specas Posted January 20, 2007 Share Posted January 20, 2007 The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011907-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000008f, 0x00028a50, 0x00028a4c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini011907-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011807-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011807-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011707-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011507-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x00000099, 0x000fffff, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini011407-03.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011407-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011407-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011307-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011207-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini011107-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x01042ff4, 0x00000002, 0x00000000, 0x804e65de). A dump was saved in: C:\WINDOWS\Minidump\Mini010907-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x00000099, 0x000fffff, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini010907-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x000001a1, 0xb3f119c4, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini010807-02.dmp.My computer craches 2 times or 1 times a day and i can't understand why. So i decided to write in this forum.Thanks for your help Link to comment Share on other sites More sharing options...
cluberti Posted January 20, 2007 Share Posted January 20, 2007 STOP 0x1a (same as a STOP 0xa): IRQL_NOT_LESS_OR_EQUALTypically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)STOP 0x4E: PFN_LIST_CORRUPTThis indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.STOP 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLEDA kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).Sounds like you've got a driver problem - and since it's going to be a kernel-mode driver, you might start by uninstalling all antivirus/antispyware software running on the machine, and upgrade the rest of your hardware's drivers to the latest versions to see if it helps. I'd also strongly suggest running your memory through a memory test, and make sure you aren't overclocking any components as well.Otherwise, configure your machine for a complete memory dump and I'll analyze it the next time the issue occurs. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now