Random reboots

I'm back to being unconvinced again. I just had the system crash while trying to change resolution and I only have the 1 stick of RAM in that tested good on MemTest. Maybe I do need to flash the BIOS. Is there any way you know to test and isolate if the CPU or Mobo is bad? They are both pretty new.

Still running with Windows XP SP2 x64 ? If so, and if you are also running any older applications, you may be periodically bumping into conflicting .dll processes. What if anything are you seeing in Event Viewer - System, and Event Viewer - Applications. Have you turned of Automatically Reboot after failure… thereby obtaining a Blue Screen with Error, Stop, or Warning messages?

Yes, bluescreen with PAGE_FAULT_IN_NONPAGED_AREA. I'm not sure what you are asking about in the Event Viewer. Yes, there are lots of Information items and a few Errors in the System section, as I mentioned in post #3 but I don't know if anything there will help me discover what the problem is. I do run MS Office 2003. There's not much else old that I run. If I could duplicate the condition, that would help. I have tried Win7 a few times but can't get it configured to my satisfaction (yet) to be able to run it long enough to see if the machine still crashes or locks up.

read here http://www.resplendence.com/whocrashed

Download Who Crashed and run it.

Post back with any information you may discover.

I installed it several days ago. Most of the information says "unknown driver". What I don't understand is why the system ran fine for several months and then started crashing, freezing, rebooting when I hadn't made any significant changes. I'm still considering flashing the BIOS this weekend, and I have new RAM (same model/brand) on the way. Here is the report if it will tell you more than I am seeing. The crashes before today may be due to bad RAM. System Information (local) ——————————————————————————– computer name: MAIN1 windows version: Windows XP x64 Service Pack 2, 5.2, build: 3790 windows dir: C:\WINDOWS CPU: AuthenticAMD AMD Phenom™ II X4 945 Processor AMD586, level: 16 4 logical processors, active mask: 15 RAM: 4292702208 total VM: 2147352576, free: 2023489536 ——————————————————————————– Crash Dump Analysis ——————————————————————————– Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Thu 10/18/2012 12:49:54 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini101712-01.dmp This was probably caused by the following module: Unknown (0xFFFFFADF903A1912) Bugcheck code: 0x50 (0xFFFFFADF6EE56FF8, 0x0, 0xFFFFF80001025BD0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA On Thu 10/18/2012 12:49:54 AM GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: Unknown (0xFFFFFADF903A1912) Bugcheck code: 0x50 (0xFFFFFADF6EE56FF8, 0x0, 0xFFFFF80001025BD0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA On Mon 10/15/2012 1:50:52 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini101412-02.dmp This was probably caused by the following module: Unknown (0xFFFFFADF044020A0) Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0xFFFFF800011A9F93) Error: DRIVER_CORRUPTED_EXPOOL Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown DRIVER_CORRUPTED_EXPOOL On Sun 10/14/2012 6:55:51 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini101412-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0xC4 (0x81, 0xFFFFFADF380F5B10, 0x8A, 0x0) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver called MmMapLockedPages. (You should use MmMapLockedPagesSpecifyCache instead, with the BugCheckOnFailure parameter set to FALSE.) This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 10/14/2012 2:04:13 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini101312-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0x50 (0xFFFFFADF07535264, 0x0, 0xFFFFF80001025B51, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 10/12/2012 3:56:34 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini101112-02.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0x50 (0xFFFFFADF1672F264, 0x0, 0xFFFFF80001025B51, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 10/12/2012 3:55:43 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini101112-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0xC4 (0x81, 0xFFFFFADF36314210, 0x8A, 0x0) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver called MmMapLockedPages. (You should use MmMapLockedPagesSpecifyCache instead, with the BugCheckOnFailure parameter set to FALSE.) This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 10/4/2012 2:59:43 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini100312-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8000101C351) Error: UNEXPECTED_KERNEL_MODE_TRAP file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 9/23/2012 6:12:08 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini092312-03.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0x4E (0x99, 0x40570, 0x1, 0x0) Error: PFN_LIST_CORRUPT file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 9/23/2012 6:05:41 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini092312-02.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000102FD04, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 9/23/2012 4:22:20 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini092312-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890) Bugcheck code: 0xD1 (0x768B00000000, 0x2, 0x8, 0x768B00000000) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. ——————————————————————————– Conclusion ——————————————————————————– 11 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: unknown If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

So the system, running XP, crashed while I was DISCONNECTING a monitor! Then today I booted into Win7 and was installing updates and watching a video and IT crashed! Gotta be hardware because there is virtually NO software in common. Unless there is some rogue malware on a separate hard drive that is somehow being activated in different OSes on different HDs. So I flashed the BIOS since it mentioned stability. I also made sure the onboard video is disabled. I downloaded some utils to test hardware and software but I'm not sure what they are doing and what it means. If it crashes again, I may take it to Staples or somewhere because they say they will test the HW and SW for $69. I can fix it, I just need to know WHAT to fix.