IRQL NOT LESS OR EQUAL Bsod in Vista 64bit on Network Transfer

[Furton]

I've recently updated my main rig (Which is an Opteron 165, 2GB PC3200 RAM, DFI LanParty UT4, Radeon X1800XT) with Vista Ultimate 64Bit edition. It's all running smoothly except when I've been trying to transfer files from my this system onto m Shuttle PC I get a IRQL NOT LESS OR EQUAL BSDO. However, this is what's bugging me, it can do a file transfer no problem if I leave the system alone (the one crashing that is), but if I try and say watch a video, or browse with a few tabs open it BSOD on me. Any ideas?

[amjedm]

My boss bought his PC to work the other day suffering from the same problem - BSOD and IRQ error.

Had a quick look on the Net and read it was either hardware or driver related. He hadn't installed any drivers or software so I swapped the RAM in to another slot and the error disappeared.

[funnelhead]

This is usually either a Driver, RAM or overheating issue.

90% of times it is a ram issue though.... try swapping a stick out, or changing slots.

f

[yamangman]

Let's face it, it could be pretty much anything. The BSOD is an occurance due to your computer, for whatever reason, attempting to perform a dangerous operation in kernel space that would cause loss of data. In a past life when I fixed other peoples poorly maintaind PC's, this was primarily due to 'dodgy drivers', which is a phrase I use to cover a vast tract of common windows problems with one fell swoop (particularly older dll hell wins). I'd start with drivers if I were you, though swapping out a stick of RAM is a relatively painless task as i'm sure you're aware.

[directhex]

what's your network controller? i had major network issues with the bundled drivers for my old board

[Agent]

This error is a pain. Many things can cause it.

Add PSU to your list. I've seen that many times!
Worth a check

Make sure you do a memtest off a CD (Google UBCD) to see if you have any hardware issues that come to light

[Paul Adams]

Actually the majority of these events are caused by drivers - they are trying to address virtual memory which is not resident in physical memory during an interrupt or DPC.
Most of the time the address is garbage too, not just "paged out" (i.e. 0).

If it occurs during a file transfer over the network, I would guess at network adapter drivers first.
Sometimes with network adapters it can be when they have TCP checksum offloading enabled - if your NIC has this feature then try turning it off.

[directhex]

Actually the majority of these events are caused by drivers - they are trying to address virtual memory which is not resident in physical memory during an interrupt or DPC.
Most of the time the address is garbage too, not just "paged out" (i.e. 0).

If it occurs during a file transfer over the network, I would guess at network adapter drivers first.
Sometimes with network adapters it can be when they have TCP checksum offloading enabled - if your NIC has this feature then try turning it off.

it's never quite that simple though. one bad driver can cause another bad driver to crash - and i had a sound card where unplugging the speakers at the wrong moment would also cause issues