The BSOD's are driving me mad, here's a little history;
I purchased the hardware in 2009/2010 and built the system sometime
during 2010, howerver I could not get it to work so it languished for
a couple of years in the wardrobe. I did no have the time to tinker
with it.
First of all the graphics card would not work, I traced this to the
blue PCI-E slots, none of which worked, white ones work fine.
Next was memory (2 x OCZ PC2 6400 800MHz DDR Unbuffered DIMM, Platinum) giving 4GB. Had it in Dual Channel but only recognised 2GB due to a
faulty slot !! Currently using slot 3 and 4, not dual channel.
Crashes are now less frequent but are usually IRQL_Not_Less_or_Equal
This may help too, I cannot get the 2 x 750G Seagate to work
in RAID, RAID is enabled but the system recognises C and D as
seperate drives. No mirroring has taken place. I have now
disabled this.
I cannot explain this but if I remove the power cable and SATA
connection from the non boot drive it does not boot, plug in the
power cable and leave the SATA cable disconected it boots.
The bootable drive has the first power connection and the non
bootable drive the second connection in the series.
OS - Vista Ultimate SP2 x86 (32-bit).
Vista Ultimate is the original installation.
OS is full retail version.
Hardware was purchased in 2009/2010, however when built sat in
wardrobe for a couple of years due to time constraints.
OS was installed when built and not re-installed.
CPU - Intel Q9650 Quadcore
Video Card - 1792MB XFX GTX295 DDR3
MotherBoard - Asus P5N32-E SLI
Power Supply 2 x Enermax EIN720AWT 720W
I have attached the relevant files and the most recent mini dumps.
Thanks in advance.
PS Have run memtest x86 for about 4 hours with no errors.
The <2009 versions are known to cause BSODs in Windows 7 x64 & likely is for a fully updated Vista SP2 system as well, The resulting dumps appear related to hardware failure -- like yours do.
Update the Asus drivers 1st and see if the system stabilizes.
Can't even load it today, constant BSOD. Tried re-installing Windows but just keeps BSOD IRQL etc. even when trying to input the activation key !!
Might just get another MOBO and start again.
Instead of a new mobo have opted for a clean install, however I am still getting BSOD's. I have run the tests on memory and HDD's with no errors.
I can safely say there are never any BSOD's in Safe Mode or Safe Mode with Networking so hopefully that narrows it down a little.
I have attached the necessary files, any help would be much appreciated, thanks.
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 am going to recommend enabling Driver Verifier since you mentioned you do not receive crashes in Safe Mode with networking:
Driver Verifier:
What is Driver Verifier? Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver. Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD. Before enabling Driver Verifier, it is recommended to create a System Restore Point: Vista - START | type rstrui - create a restore point Windows 7 - START | type create | select "Create a Restore Point" How to enable Driver Verifier: Start > type "verifier" without the quotes > Select the following options - 1. Select - "Create custom settings (for code developers)" 2. Select - "Select individual settings from a full list" 3. Check the following boxes - - Special Pool - Pool Tracking - Force IRQL Checking - Deadlock Detection - Security Checks (Windows 7) - Concurrentcy Stress Test (Windows 8) - DDI compliance checking (Windows 8) - Miscellaneous Checks 4. Select - "Select driver names from a list" 5. Click on the "Provider" tab. This will sort all of the drivers by the provider. 6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation. 7. Click on Finish. 8. Restart. Important information regarding Driver Verifier: - If Driver Verifier finds a violation, the system will BSOD. - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD. If this happens, do not panic, do the following: - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up. - Once in Safe Mode - Start > type "system restore" without the quotes. - Choose the restore point you created earlier. If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows: - Start > Search > type "cmd" without the quotes. - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes. - Restart and boot into normal Windows. How long should I keep Driver Verifier enabled for? It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier. My system BSOD'd, where can I find the crash dumps? They will be located in C:\Windows\Minidump Any other questions can most likely be answered by this article: http://support.microsoft.com/kb/244617
All of the attached dumps are verifier enabled, however it's not flagging any problematic driver, so we may be dealing with a hardware issue. For reference, all of the attached dumps are of the 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.
This is a driver for the Asus ATK0110 ACPI Utility. I recommend removing this utility and any other installed Asus utilities for troubleshooting purposes. They are known to cause issues.
If after removing any Asus utilities, you're still crashing, let's run a Memtest:
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:
I have had a few crashes since the last update, mostly when entering hibernation, however I have found numerous new drivers so I will install them and run for two or three weeks and let you know how it goes. Thanks for the help to date.
Thanks for the update, let me know how the system behaves. If you'd like, you can attach the DMP files here and see if there's anything else I can see in the latest.
The latest attached dumps are of the IRQL_NOT_LESS_OR_EQUAL (a) bugcheck:
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.
The device, ATK0110 ACPI UTILITY, is reporting "tv_ConfigMgrErr39". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ACPI\ATK0110\1010110.
I told you to remove it earlier, but I meant update - so an incorrect instruction on my part. My sincere apologies.
Please navigate to Asus' website and update any and all Asus utilities available for your motherboard. If you need help accessing this information, let me know.
Let me know the system behavior after updating your Asus utilities~
No probs, I will update the driver and let you know how it goes. I will give it a couple of weeks as am not going to be around much until the end of the month. Thanks for the help.
Thanks for the update, I will look forward to your response.
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!