Windows XP Blue Screens :(

**LaValva** · 03-04-2003, 10:31 PM

Well I'm getting kinda frustrated now, so I decided to stop trying to be a hero and ask for help

I just upgraded my Abit KG7/Athlon Tbird 1400 to a Asus A7N8X Deluxe/Athlon XP 2200+. I've been getting blue screens left and right. I'm going to take this one first, because I just got it and I wrote it down, the others.. I lost the papers with the info. So here goes, I was on AIM, listening to some MP3's and just about to load Musicmatch Jukebox to rip my new cd. Then I get this blue screen:

IRQL_NOT_LESS_OR_EQUAL

stop: 0x0000000A (0x00000000, 0x00000002, 0x00000001, 0x804F59B9)

I tried looking up the error code on Microsoft's support site, but can't find anything that strikes me. I'm currently running 512mb of Crucial PC-2700. MSI GeForce 4 Ti4600. I'm using onboard sound/NIC's at the moment. Any suggestions? Thanks for your help.

**Dasenergi** · 03-04-2003, 10:37 PM

http://support.microsoft.com/?kbid=311564

**LaValva** · 03-04-2003, 10:40 PM

I'm not upgrading to Windows XP, I forgot to mention, I just switched my hard drive, but I did reinstall Windows. I didn't format, but I did a reinstall from the Windows CD, and if I have to activate one more time, heads will roll

**LaValva** · 03-04-2003, 11:14 PM

OK, here's another error I just got:

PAGE_FAULT_IN_NONPAGED_AREA

Stop: 0x00000050 (0xBC64CBAC, 0X00000000, 0XBF8019FE, 0X00000002)

Win32k.sys - Address BF8019FE base at BF800000, datestamp 3bb6d462

Ahhhhhhhhhhhhhhhhhhh!

**Trunks** · 03-05-2003, 12:58 AM

yoyoyo I get that first blue screen you posted when I try to boot up at 180x13, anyone know how to fix that let me know also.

**epik_x** · 03-05-2003, 01:56 AM

Originally posted by lavalva
I'm not upgrading to Windows XP, I forgot to mention, I just switched my hard drive, but I did reinstall Windows. I didn't format, but I did a reinstall from the Windows CD, and if I have to activate one more time, heads will roll

Always format and do a FULL windows install after a major hardware change like that...Like trunks I usually get those BSOD when i OC too much, before u format try a bios reset to make sure everything is how it should be, if that doesnt work..do the format and FULL install...

**vikesrock** · 03-05-2003, 02:56 PM

Your problem is memory related. IRQL_NOT_LESS_OR_EQUAL means the memory tried to access a memory space that doesn't exist, which means that there is bad memory. Same with your other error message, again OS is trying to access a memory space that isn't shall we say "physically" accesible. 9 times out of 10 it is system memory, but that one time it is video memory on the video card. Your system accesses that memory in some of the same mannners as it does system memory. So the fix I would say is first swap RAM with a KNOWN good chip, usually you can take your RAM to COMPUSA or Best Buy and they have a RAM checker there and will usually check your RAM for you. If you swap RAM and there is still a problem, then swap video cards, that should clear up your problem.

**LaValva** · 03-05-2003, 03:45 PM

Now today I came back to my computer after work, moved the mouse which usually turns the monitor back on. Computer doesn't go into standby, I just have it turn the monitor on. And I just stays black. The green light comes on, like there is signal, but it's black. I checked the Event Viewer and this message is there:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xeb0799e8, 0x00000002, 0x00000000, 0xf82f81ec). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

I can't take this! I'm gonna try the memory thing later, it's too nice out to sit here

**idiotekniQues** · 03-05-2003, 03:49 PM

i also got that IRQL etc error message when OC'ing over 158 FSB. also I just got one blue screen that said BAD_POOL_CALL. is that ram related as well? man that ups guy cant get here fast enough today. been out on the truck for delivery since 7am this morning and its 3pm now hes got my fresh stick of ram! booyah!

crossing my fingers hoping its my ram holding me back and nothing else from hitting 3 ghz stable!

**vikesrock** · 03-05-2003, 04:17 PM

Let me qualify what I said above real quick, the official Microsoft Line on a Stop error of 0x0a with the IRQ_NOT_LESS_OR_EQUAL is hardware or software failure. What it is really saying is a device tried to access memory that is not available, I guess your Sound Card could do that if it is bad, but 99.9999% of the time, the memory is there, Windows mapped it, and it's bad when the device tries to access it.

**fLaPjAk** · 03-05-2003, 04:58 PM

I used to get those.... with generic RAM, but it can happen to any faulty RAM.

I just swapped in two sticks of Crucial (yes I know you're running Crucial as well, but it could be that yours are corrupt/bad) and I have been gaming non-stop since Saturday morning without a problem... in fact, after switching between SC and RvS contiously, I haven't even restarted yet... I'm amazed!

Try swapping another stick of Crucial in there and see if you get those errors again!

**DJBeanPole17** · 03-05-2003, 05:05 PM

Wasn't XP supposed to be BSOD-FREE? I get them every once and awhile... but they just flash REAL quick and the computer restarts. When it comes back up and it has that "computer just recovered from a serious error" I always send the data and it takes me to a link to fix things. But not all the time

**LaValva** · 03-05-2003, 06:26 PM

Originally posted by fLaPjAk
I used to get those.... with generic RAM, but it can happen to any faulty RAM.

I just swapped in two sticks of Crucial (yes I know you're running Crucial as well, but it could be that yours are corrupt/bad) and I have been gaming non-stop since Saturday morning without a problem... in fact, after switching between SC and RvS contiously, I haven't even restarted yet... I'm amazed!

Try swapping another stick of Crucial in there and see if you get those errors again!

Yeah I had 2 sticks of 512mb Crucial, went to one, then tried the other one. Still got the errors. I've been running on 2 x 256mb sticks now, 1 Crucial, one Kingston and I've been fine for about 3 hours now, so I'm gonna give Crucial a call and see what's up. I really hope this isn't just a coincidence, I'd rather take the time to send this RAM back then to have no clue what the problem is.

**vikesrock** · 03-05-2003, 08:30 PM

Wasn't XP supposed to be BSOD-FREE? I get them every once and awhile... but they just flash REAL quick and the computer restarts. When it comes back up and it has that "computer just recovered from a serious error" I always send the data and it takes me to a link to fix things. But not all the time

Well it kinda is, the only time you get BSOD is when you have total system failure, as with 98 and the like, you got BSOD if the wind blew right. As far as the BSOD's flashing real fast and restarting, XP has a setting in it to do that. You can turn it off by right clicking my computer, left click properties, click advanced tab, then click the settings button under startup and recovery. In there it will show under system failures, automatic reboot. Just uncheck that box and you will get the good ole blue screen of death just sitting there.

**freedon** · 03-05-2003, 08:43 PM

Originally posted by DJBeanPole17
Wasn't XP supposed to be BSOD-FREE?

it is, when you get a BSOD you have a hardware, software or driver problem

Thread: Windows XP Blue Screens :(

Thread Tools

Display

Windows XP Blue Screens :(

Posting Permissions