BSOD - irql

I know this has probably been asked thousands of times before - I've looked at the threads and still no idea.
I randomly get a bsod with the error
'IRQL_not_less_or_equal
disable/remove h/ware or s/ware
disable bios memory (caching/shadowing)
*stop 0x00000a(0x0a06001f,0x000000,0x804e35f9)'

It's a panasonic cf-51 running xp sp3
I've pressed f2 and can't change the bios settings and have no idea where to disable the bios mem.
I don't have a xp repair disc and can't think of any h/ware or s/ware that's been loaded recently.
I've got plenty of hard disc space so that's not the problem (or maybe it is ,I just don't know anymore )
Any help would be greatly appreciated
 
Please post the minidumps for analysis.

First locate your minidump files, they are usually found by clicking on your C: drive, in windows explorer, then click on Windows to view the contents. If your operating system is installed under a different drive letter then look there. They should be stored under a file called minidump.The files will have a .dmp extension.

Zip up at least 6 of the most recent files into one zip folder and save on your desktop (if there are less then just zip up what you have).

Below the reply box click on Go Advanced. Then scroll down until you see a button, Manage Attachments. Click on that and a popup-window opens.

Click on the Browse button, find the zip folder you made earlier and doubleclick on it.

Now click on the Upload button in the popup. When done, click on the Close this window button.

Enter your message-text, then click on Submit Message.
 
Thanks for the help so far -I've had a fiddle with my mem as I seem to recall taking it out to check it for some reason ,wasn't sure if it was in properly
 

Attachments

  • New Compressed (zipped) Folder.zip
    167.8 KB · Views: 1
Three of the .dmp files are incomplete but I managed to get the error codes, one did debug correctly. Three are 8E and one is 77. They have numerous causes but I would start with a check on the memory.

As you have just reseated the memory the problem may not return, if it was just badly seated, this would explain the incomplete crash dumps.

If the BSOD's continue please post any new ones and follow this routine to check your memory.

Power off the PC and remove the mains connection, always touch the metal of the case with your hands to avoid any static electricity from causing component damage. (On laptops ALWAYS remove the battery before removing or replacing memory modules). Remove all your memory modules. Clean the contacts with a soft rubber (up and down not from end to end) then insert just one module and reboot to test for any change in performance. Repeat this for every module one at a time and run for at least 24 hours (or until an error occurs) with memory intensive programs, playing games or a video. Obviously if you only have one module this cannot be done, but you should still remove and clean the module and reseat it and test.

If you only have one stick download this to test it. http://www.memtest.org/

You need to scroll down the page until you see the three blue screenshots. Just below is the list of downloads for Memtest86+ V4.20. Click on Download - Pre-Compiled Bootable ISO (.zip)and save to your desktop, When the download is complete right click the file and select Extract Here and burn the image to a CD. In windows 7 right click the extracted file, select Open With, then select Windows Disc Image Burning Tool then follow the prompts. For all other versions of windows (if you do not have an ISO burner) download this free software. http://www.isoimageburner.com/

Boot the PC into the Bios setup and set the CD/DVD drive to 1st in the boot sequence. Insert the disk in the drive then reboot and the disc will load into dos. Leave the test to run through at least 8 cycles.

The memtest will not be 100% accurate but should easily detect any major faults.
 
Thanks

Thanks for your help -laptop has been running fine since I reseated the memory ,suppose it's a matter now of wait and see ,but thanks anyway
 
I think you may well have stumbled across the cause of the problem. Let us know if it goes wrong again.
 
Back