We seem to have two main bugchecks here from the attached dumps:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
A kernel-mode driver attempted to access pageable memory at a process IRQL (Interrupt Request Level) that was too high.
Usual causes are a device driver has a bug and attempted to access invalid memory, the pagefile has been corrupted or there is a memory problem.
All of the *D1 dumps appear to be faulting pacer.sys, which is the QoS Packet Scheduler Windows driver (not the true cause). It's likely another device driver is causing it to crash. Usually when we see network related drivers and such on the stack and throughout the dumps, it's an indication of a 3rd party antivirus or firewall causing the issue. However, it can be hardware as well.
IRQL_NOT_LESS_OR_EQUAL (a)
A kernel-mode driver or process attempted to access a protected memory location it does not have permission for, or a kernel interrupt request level (IRQL) attempted to access a memory address that is too high.
This bugcheck usually occurs when a driver uses an incorrect memory address. Other possible causes of this error include: bug in a device driver, system service, the BIOS, an old Anti-virus program or backup tool, or possibly memory issues.
I see you have Norton installed. I am going to recommend temporarily removing and replacing Norton with Microsoft Security Essentials for troubleshooting purposes.
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
Thanks for the update, I will mark this post as solved in 24 hours if you have no issues by then. If you do, you can always repost and I will unmark it.
Regards,
Patrick
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Forum
4.7M posts
957.9K members
Since 2002
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!