Constant Blue Screens of Death with different stop codes

November 17, 2013 at 13:17:53
Specs: Windows XP, 3.391 GHz / 2037 MB
Hey Guys/Gals,

I am having problems with my computer. For over around a month or so I have been getting constant blue screens of death. At first I thought it was because I was filling up my hard drive too fast because of all my torrenting and the fact that I have a small hard drive. But after deleting all my torrents I still have the problem. Normally I would search the web for a solution to my problem but the stop error codes are usually different each time.

If this is because I have some faulty or old hardware then I will just ignore the bsod's since i am getting a new computer soon but if this is caused by something else by either a program or software then I would like some help fixing it.

If you can provide any help to me getting rid of these bsod's then I would greatly appreciate.

Thanks again.


See More: Constant Blue Screens of Death with different stop codes

Report •

November 17, 2013 at 14:19:33
Have you performed an virus scan?

Post some of the error messages.

Report •

November 17, 2013 at 14:29:34
I have scanned for both viruses and malware using bitdefender and malwarebytes but no errors, viruses, or malware showed up. I would post some of the codes from the blue screens of death but the computer restarts before I have a chance. Also there are a variety of stop error codes that I get. I will try to post the next one I get if I get a chance. Do you have any other options, ideas, or help at this point? Thanks

Report •

November 17, 2013 at 14:45:59
Lots of issues Mcgrufer.

Lets see if this works. You probably will have to use Safe mode.

Disable Automatically restart

message edited by Johnw

Report •

Related Solutions

November 17, 2013 at 14:49:33
Ok I have disabled the automatic restart now i just have to wait for another BSOD right? Or is there something else I can do before then?

Report •

November 17, 2013 at 14:57:45
"Or is there something else I can do before then?"

Try this, boot into Safe mode & get the .dmp file.

Copy & Paste the dump (.dmp ) file onto your desktop & then upload using Image Uploader. I upload to for images & for files. Post the link please.
Minidump file is located in C:\Windows\Minidump
How to see hidden files in Windows

Upload to for images & for files. Neither need an account. Give us the link.
Image Uploader

How to use for files.

Report •

November 17, 2013 at 14:58:02
You could check your RAM. Faulty RAM can cause errors. Run memtest86+ from a boot disk to check for RAM errors. If any are found then shut down the PC, unplug it, depress the start button a couple of times and then snap each RAM module in and out 4 or 5 times to burnish the contacts. Then rerun memtest86+

If this rig has been assembled for a while there is a good chance of oxidation on those contacts.

Get memtest86+ from the link below.

Report •

November 17, 2013 at 15:14:53
@Johnw Here is the link:

@OtheHill I dont have a boot disk nor can my computer burn to disks sorry. Also it was factory assembled and if my problem is bad ram then I will wait for when I get my new computer around next month.

Report •

November 17, 2013 at 15:27:37
Here are the results for all to look at.

* Bugcheck Analysis *
* *

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: fffffff0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804e317a, address which referenced memory

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetUlongFromAddress: unable to read from 80561f50


804e317a 66813ffd02 cmp word ptr [edi],2FDh



TRAP_FRAME: a7f6353c -- (.trap 0xffffffffa7f6353c)
ErrCode = 00000000
eax=8a52aee0 ebx=8a52aed0 ecx=00000000 edx=00000000 esi=804e2801 edi=fffffff0
eip=804e317a esp=a7f635b0 ebp=a7f6363c iopl=0 nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
804e317a 66813ffd02 cmp word ptr [edi],2FDh ds:0023:fffffff0=????
Resetting default scope

LAST_CONTROL_TRANSFER: from 804e317a to 80544808

a7f6353c 804e317a badb0d00 00000000 00000001 nt!KiTrap0E+0x238
a7f6363c 804e44e4 8a52aed0 00000000 00001000 nt!CcAcquireByteRangeForWrite+0x384
a7f636c8 b9d4fbd8 00001000 00000000 00000000 nt!CcFlushCache+0x2d6
a7f6374c b9d4fd28 89981778 8a5a4100 00000001 Ntfs!NtfsFlushVolume+0x73f
a7f637ec b9d3d03b 89981778 89413b20 89e784e0 Ntfs!NtfsCommonVolumeOpen+0x341
a7f638c8 804ef1f9 8a5a4020 89413b20 89413b20 Ntfs!NtfsFsdCreate+0x14d
a7f638d8 b9ef76c3 89413b20 a7f60000 8a5ed280 nt!IopfCallDriver+0x31
a7f63908 804ef1f9 8a5ee3a8 89413b20 89e784e0 FLTMGR!FltpCreate+0x1d9
a7f63918 b9e7d876 00000000 8a5e9dc8 8957f738 nt!IopfCallDriver+0x31
a7f63964 804ef1f9 8a5a7e88 00000001 89413b20 sr!SrCreate+0x150
a7f63974 b9eeae9b 00000000 89413b20 89413cd4 nt!IopfCallDriver+0x31
a7f63998 b9ef7754 a7f639b8 8a5afde0 00000000 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
a7f639d4 804ef1f9 8a5afde0 89413b20 89413b20 FLTMGR!FltpCreate+0x26a
a7f639e4 80583232 8a5a58e8 89810c24 a7f63b7c nt!IopfCallDriver+0x31
a7f63ac4 805bf490 8a5a5900 00000000 89810b80 nt!IopParseDevice+0xa12
a7f63b3c 805bba1c 00000000 a7f63b7c 00000040 nt!ObpLookupObjectName+0x53c
a7f63b90 80576051 00000000 00000000 883cfc01 nt!ObOpenObjectByName+0xea
a7f63c0c 805769c8 025deecc 80100080 025dee6c nt!IopCreateFile+0x407
a7f63c68 805790d2 025deecc 80100080 025dee6c nt!IoCreateFile+0x8e
a7f63ca8 a80a7b59 025deecc 80100080 025dee6c nt!NtCreateFile+0x30
WARNING: Stack unwind information not available. Following frames may be wrong.
a7f63d30 8054172c 025deecc 80100080 025dee6c bdselfpr+0x7b59
a7f63d30 7c90e514 025deecc 80100080 025dee6c nt!KiFastCallEntry+0xfc
025deec4 00000000 00000000 00000000 00000000 0x7c90e514


a80a7b59 ?? ???


SYMBOL_NAME: bdselfpr+7b59


MODULE_NAME: bdselfpr

IMAGE_NAME: bdselfpr.sys


FAILURE_BUCKET_ID: 0xA_bdselfpr+7b59

BUCKET_ID: 0xA_bdselfpr+7b59

Followup: MachineOwner

Report •

November 17, 2013 at 15:29:46
Good test to find out if it is a driver, is to run in Safe mode, no blue screens & it will probably be a driver.


Report •

November 17, 2013 at 15:37:44
Have you looked in Device Manager to see if there are any errors?

Upload SS ( screenshots ) if not sure.
How to use for images.

Run this program & upload SS (may need several ) of what it finds.


Report •

November 17, 2013 at 15:40:02
You receive a "Stop error code 0x0000000A (IRQL_NOT_LESS_OR_EQUAL)" error message in Windows XP

Report •

November 17, 2013 at 15:58:27
@Johnw I followed the instructions at then I took the screen shots you asked here:

Should I attempt to update the drivers or not?

Report •

November 17, 2013 at 16:14:10
"Should I attempt to update the drivers or not?"
That is a lot of out of date drivers, the best strategy I will have a better idea after seeing your Device Manager SS.

Report •

Report •

November 17, 2013 at 17:03:51
Perfect SS Mcgrufer.

If you have to go offline, let me know please.

I'm here.

The ideal process of trying to find a problem driver, is to install one at a time & test.

Start at the top of the Slim list & work your way down, the program will ask if you want to install a driver that it considers not as good as what you have installed.

If after each reboot, something squawks, roll back that driver.

How To Use the Roll Back Driver Feature in Windows XP

message edited by Johnw

Report •

November 17, 2013 at 17:09:13
I will start this process probably tomorrow as this is the current time where I am at: I will post an update once everything goes through or if something happens later on. Thanks again for your help.

Report •

November 17, 2013 at 17:13:30
Ok, catch you later.

Report •

November 18, 2013 at 03:40:10
I see that your problem is already receiving plenty of responses and advice. I've nothing useful to add to the thread.

Report •

November 19, 2013 at 18:33:37
@Johnw I have not been able to download the drivers and test them as I have been very busy this week. I will try to do them this weekend as soon as I get a chance. Sorry if this has been of any inconvenience to you. I did however get another blue screen of death. Here is the link to the mini dump file:

Report •

November 19, 2013 at 19:39:19
Ok, got it Mcgrufer, it points to other issues, we can only work in one direction at a time, process of elimination.

Shall wait until you have finished doing the driver updates, no rush.

message edited by Johnw

Report •

November 22, 2013 at 17:53:50
@Johnw Ok after a long and stressful week I was able to sit down and go through the drivers. There were no squawks or problems after updating the drivers though I dont think they were installed properly as some said there was an error or that my system setup wasnt correct but I wasnt able to record it in time. My bad sorry. Other than that here are the screenshots of the Slim Drivers Program after all the updates:

And here is the screenshots of the Device Manager after the updates:

Also early this week on November 19th (or 20th where you are) when I sent you the second BSOD mini dump I got another one right after it (this was all before I updated the drivers). Here is the mini dump file for it:

Thanks again so much for your constant help. I will await the next steps you give me.

Report •

November 22, 2013 at 18:21:48
"(this was all before I updated the drivers)"
Ok, the only thing that matters now, is if you don't get any more blue screens.

Everything looks good with your drivers, any blue screens from now on, we shall have to start using special programs to look for infections.

Report •

November 22, 2013 at 19:18:33
Ok so just to be clear there is nothing at this point that I can do to prevent the blue screens or check for more problems?

If so thank you so much for your help with this problem. I will choose your answer as best answer in about a week just to see if any problems or blue screens arise or not.

Report •

November 22, 2013 at 19:39:08
"nothing at this point that I can do to prevent the blue screens"
Not until I see a dump file produced by the new configuration.

" or check for more problems?"
Sure, but I first need a clue in what direction to head.

Report •

November 22, 2013 at 19:43:33
I must of spoke too early as just after I sent the reply I got another blue screen. Here is the minidump file:

Report •

November 22, 2013 at 20:02:23
That error gives a lot of possibles.

Start by removing your memory & all the other cards, cleaning the contacts & if available, different slots.

Clean the contacts with an pencil eraser & try it again. May need cleaning or reseating. If multi sticks, try just one stick to test. Touching an unpainted part of the case will dissipate any static electricity.
Trick To Clean Pins Of Physical Memory ( RAM ) From Dirt

Report •

Ask Question