Question : Battlefield 2: IRQL_NOT_LESS_THAN_OR_EQUA<wbr />L

Specs
---------------
ASUS A8N-SLI Deluxe
AMD 64 3500+
2 GB PCi DDR-3200
GeForce 6800 256MB
Dual 152 GB Maxtor SATA
Win XP Home

This does not occur in any other game I have nor during regular usage.

I start the game up & everything works fine until I connect to a server & load everything up (possibly a timing thing).  Rarely, it'll crash earlier.  But always it's a pretty consistent DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x0000000A (0xE29FF390, 0x000000FF, 0x00000000, 0x805AF6B4).  The last parameter seems to be exactly the same pretty often.  Neither first nor last parameters venture far from the numbers listed above.  I have a duplicate computer with exact same hardware & specs that doesn't have this problem.  Also, I have played for a long time on my problem pc until suddenly it started acting up.  The only mentionable differences I remember are installing Adobe Encore and After Effects, which I've removed to no avail.

I've tried swapping all hardware & updating drivers/BIOS & turning off uneeded devices & turning off PnP-OS in BIOS.  
I've tried using Driver Verifier & checking acpi.sys gives the exact same stop error when I boot up into Windows.  Usually the desktop will show up & anywhere from 1-15 seconds the error will occur.  I've tried copying the file over from the working computer incase it was corrupted; no luck.  Also checking nvata.sys and nvatabus.sys for Driver Verifier recreates an IRQL error.  My duplicate computer does not give the stop error when Verifying any of the above drivers.

I have my pagefile set to clear on shutdown & this kind of worked (restart before playing & it'll work for a while - usually when map changes it crashes), until the new patch came out.  

I'll probably try a recovery install, but I'd like to know what the issue is & how I can fix it without reinstall.

Thanks in advanced.

Answer : Battlefield 2: IRQL_NOT_LESS_THAN_OR_EQUA<wbr />L

Re-install and upgrade  Norton AV and it will resolve your blue screen problem


Debug report of your problem.
Mini100105-01.dmp BugCheck A, {e29c50f0, ff, 0, 805af6b4}
Probably caused by : ntkrnlpa.exe ( nt!KiTrap0E+233 )

Mini100305-01.dmp BugCheck D1, {e23cfa2c, ff, 0, 88b73521}
Probably caused by : ntkrnlpa.exe ( nt!KiTrap0E+233 )

Mini101005-01.dmp BugCheck A, {e2a7e1c8, ff, 0, 805af6b4}
Probably caused by : ntkrnlpa.exe ( nt!KiTrap0E+233 )

Mini101105-09.dmp BugCheck 100000D1, {e2b83cec, ff, 0, 88d6c521}
Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+461 )

Mini101205-13.dmp BugCheck 1000000A, {e1bb3d20, ff, 0, 80603235}
Probably caused by : ntkrnlpa.exe ( nt!ExMapHandleToPointerEx+2d )