Yes, close Frank.
It's really an attempt that has been made to access a pageable (or completely invalid) address at an interrupt request level that is too high. This is usually caused by drivers using improper addresses.
In most cases, if the offending driver has an update, it would fix the problem (only if the vendor knows about it). Because the hardware works and is not tested long enough, the companies tend to just get a driver that works for varying OS's as fast as possible which makes things worse for us.
I take it most of you are using Windows XP? And the drivers you are using are for more than one OS in the Windows family? If you really care about your hardware working with your current OS, then make sure it is certified..... Nothing more to say. If it is in fact certified, then there is a bigger issue. And then it's time to call up MS. Only after you have followed these steps.
If your system is overclocked, reset it to the default settings.
A lot of BSOD`s are caused by faulty ram. The steps below are to help in removing the possibility of faulty ram.
Make sure your ram is not overclocked, as this can cause stability issues.
Make sure that the ram you are using is compatible with your mobo (motherboard). Check with your mobo manufacturers website.
Turn off your computer, and unplug the mains cable.
First. Take out your ram stick(s) and clean the contacts with an eraser (rubber you use to rub out pencil mistakes). Blow away the remnants and replace one stick at a time, and test your system.
You might also want to try putting your ram into a different dimm slot.
While you have your case open, it`s also a good idea to clean out any dust, that may have accumulated. Also check all connections, and cables etc.
You can also download, and run the Memtest86+ programme from http://www.memtest.org.
Test each stick of ram individually first, and then together.
Let the programme run for at least seven passes for each stick of ram.
If you don`t have a floppy drive, there is a pre-built iso version available, that you can burn to cd(as an image), and then boot from that.
If memtest gives you errors then most likely your ram is bad. However, please be aware that some faulty ram can pass Memtest.
Also check with your motherboard manufacturers website, and your motherboard manual for supported manufacturers, and types of ram.
If you suspect a damaged page file(virtual ram). Here`s how to delete, and create a new page file.
Right click my computer, and select properties, and then the advanced tab.
Under performance, click settings. Click on the advanced tab, and then on the change button.
Click on the custom size button, and click in the initial size box and make the size of the page file 0. Click in the maximum size box, and make the size of the page file 0.
Now reboot your machine. After your system has restarted run a defrag.
Once the defrag has finished, go back to the pagefile settings above, and click on the change button. For the initial, and maximum pagefile size make it 1.5 times the amount of ram your have. I.E if you have 512mb of ram set the page file to 768mb.
Click on the set button again, and reboot your system. You now have a brand new page file.
Also, check that you have all the correct, and latest drivers for your system. And remember that you should rollback if those don't work up to this point.
If your mobo has onboard sound, or onboard video, and you are using a separate soundcard, or video card. Please make sure that your onboard sound/video is disabled.
Finally. Run a disk check. Click start/run and type cmd. When the command window opens, at the command prompt type chkdsk /r /f and hit the enter key. Note the space between the chkdsk command and the forward slash, and again between the r command, and the forward slash.
You will receive a message saying that "Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?" Type y and hit the enter key.
Now type exit followed by the enter key.
Restart your computer, and during the bootup process the disk check will start.
Depending on the size of your hard drive this can take quite some time to complete. Once the disk check has finished your computer will reboot.
If after all of these steps have been performed, and you still get BSOD's, then please zip up 3 - 5 of your most recent Minidumps (or what you have) and post them to SpamMe@only-the-truth.com
for analysis. You can find your minidumps in the following directory. c:/windows/minidumps
If your system just randomly restarts without BSOD's (Blue Screen Of Death) then do the following.
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. Take the check out of the box for "Automatically Restart" for System Failures.
5. In the Write debugging information list, click Small memory dump (64k).
To change the folder location for the small memory dump files, type a new path in the Dump File box (or in the Small dump directory box, depending on your version of Windows).
The only real way to fix problems like these is for people like us to send in reports to the vendors to tell them what has happened and on what OS. Send it with a debug report. Don't bother MS about your BSOD's. The OS has already been created with hardware that has been certified by them. Hardware vendors have the job to get their hardware working on a system that has already been made. MS won't make you a personal hot fix even if the problem is wide. It's not their problem. It is easier to tell the vendor of your hardware or software about your problem for future customers and hopefully working updates. So if you have new hardware, you can bet you have the latest updates. So I urge you to downgrade or rollback to a previous version of your drivers or buy hardware that is certified by MS. It won't always be drivers, it can also be hardware faults like heat, cpu, motherboard, PSU's, faulty RAM etcetera..
Many of the problems here are based on the former. And most are not always the same, but can have the same symptoms. That's why we got debugging tools to help us
I will look over your dumps soon as I finished working on some other important emails Frank. You are important to me, but since you have already fixed your problem, it's not very important