BSOD

[Gamingphreek]

So i just finished upgrading my computer:

DFI LanParty UT Ultra-D
X2 3800+
1 gig Corsair DDR400 VS
EVGA 7800GT
Seasonic S12 500 Watt
Samsung Spinpoint 160GB HDD

I keep getting BSOD. Mort particularly "IRQL_NOT_LESS_THAN_OR_EQUAL"

Sometimes it happens when i boot into windows, sometimes it doesn't. Does anyone know what could be going on. Also, where should an event like this be logged in the System Event Manager? What should it look like there?

-Kevin

 

[xeno2060]

New HD? did you do a fresh install of OS?

 

[PurdueRy]

Could be a RAM problem, are you overclocking?

 

[Medea]

"IRQL_NOT_LESS_THAN_OR_EQUAL" = Typically due to a bad driver, or faulty or incompatible hardware.

 

[Gamingphreek]

I am not OCing at all.

As for the HDD, my copy of Win XP....well it got scratched so it doesn't format by itself. I have to install 2000Pro and then upgrade to XP from there.

"IRQL_NOT_LESS_THAN_OR_EQUAL" = Typically due to a bad driver, or faulty or incompatible hardware.

Anyway we can narrow that down a bit

-Kevin

 

[Gamingphreek]

At the bottom it says "HTTP.SYS". Is that the file that is malfunctioning.

-Kevin

 

[Medea]

Originally posted by: Gamingphreek

"IRQL_NOT_LESS_THAN_OR_EQUAL" = Typically due to a bad driver, or faulty or incompatible hardware.

Anyway we can narrow that down a bit

Yeah, I'm sure that *really* clinched it for you.

That little pearl of info came from Troubleshooting Windows Stop Messages. I was too tired to insert the source....

 

[imported_nocturne]

Basically, a piece of hardware is trying to access a virtual address that windows doesn't recognize. If you've had this problem since upgrading to SP2, chances are you have a driver that's incompatible with SP2. Also, I've had this occur when I've tried to enforce IRQ rules in the BIOS. This can also be caused with XPSP2 not agreeing with advanced mem settings in the BIOS. If the debug points you to IRQ 3 or 9, it could be virtual IRQ steering causing a conflict, which would be fixed by uninstalling and reinstalling devices in new slots (in case of vga, you have to uninstall drivers, then disable assign IRQ to VGA in BIOS).

In any case, good luck. A lot of these crashes can have many different causes, and half the time I don't even know how I fix them.

 

[Gamingphreek]

Originally posted by: nocturne
Basically, a piece of hardware is trying to access a virtual address that windows doesn't recognize. If you've had this problem since upgrading to SP2, chances are you have a driver that's incompatible with SP2. Also, I've had this occur when I've tried to enforce IRQ rules in the BIOS. This can also be caused with XPSP2 not agreeing with advanced mem settings in the BIOS. If the debug points you to IRQ 3 or 9, it could be virtual IRQ steering causing a conflict, which would be fixed by uninstalling and reinstalling devices in new slots (in case of vga, you have to uninstall drivers, then disable assign IRQ to VGA in BIOS).

In any case, good luck. A lot of these crashes can have many different causes, and half the time I don't even know how I fix them.

Is it weird at all that this happens every other time i boot up. Exactly every other time.

-Kevin

 

[KeepItRed]

Originally posted by: Gamingphreek
So i just finished upgrading my computer:

DFI LanParty UT Ultra-D
X2 3800+
1 gig Corsair DDR400 VS
EVGA 7800GT
Seasonic S12 500 Watt
Samsung Spinpoint 160GB HDD

I keep getting BSOD. Mort particularly "IRQL_NOT_LESS_THAN_OR_EQUAL"

Sometimes it happens when i boot into windows, sometimes it doesn't. Does anyone know what could be going on. Also, where should an event like this be logged in the System Event Manager? What should it look like there?

-Kevin

Good luck, and Good luck with that Corsair VS RAM. I couldn't install windows because of that lol. Kept getting the Blue screen and a bunch of memory errors. Crucial = GOD

 

[Gamingphreek]

It worked fine on my last board. I even had it running with a lower CAS latency (2.5) on my last board.

-Kevin

 

[imported_Leporello]

I had a similar problem using 1GB Corsair TwinXL 3200Pro that had previously worked well in a Pentium system. I discovered that my Corsair memory did not like my new Epox 9NPA+Ultra. I replaced the memory with 2GB Patriot 3200LLK and my problems disappeared. I could run the Corsair twinset with lights in the Epox mobo but only if I reduced its FSB from 400Mhz to 333Mhz.

I'm no expert in these matters. In my search for the solution to my BSODs I found many references to AMD systems having problems with Corsair memory.

 

[DAPUNISHER]

There have been a lot of reports of compatibility issues between the Ultra-D and Corsair VS. Some have resolved it with a bios flash, others just can't make 'em play nice at all. Check dfi-street.com Kev, and Happy Holidays.

 

[Gamingphreek]

Thanks guys. Well if it is the RAM, ill have to suffer every other reboot until i can afford to buy my 2 Gig.

Happy Holidays guys!

-Kevin

 

[dclive]

Originally posted by: Gamingphreek
Thanks guys. Well if it is the RAM, ill have to suffer every other reboot until i can afford to buy my 2 Gig.

Happy Holidays guys!

-Kevin

If you boot in safe mode does this happen? (Reboot into safe mode 2-3x in a row)
Do you have minidump files in c:\windows\minidump? If so, send them to me and run MPSReports and send me the resulting .cab file; follow all the directions in my .sig.