I did my normal database update, before doing a quick scan today.
A couple of minutes into the scan, I got ye olde Blue Screen - -
Stop 0x0000000A (0x00000004, 0x00000002, 0x00000000, 0x804ED4E9)
IRQL_NOT_LESS_OR_EQUAL
This never happened before. Running XP Pro Sp3, GB memory. Very tight, clean install, with no problems ever. Just chugs along flawlessly, so this was a surprise.
Any help/ideas would be appreciated.
Thanks!
#1
Posted 06 February 2009 - 04:03 PM
#2
Posted 06 February 2009 - 07:03 PM
Quote
For we wrestle not against flesh and blood, but against principalities, against powers, and against the worldly governors, the princes of the darkness of this world...
#4
Posted 06 February 2009 - 09:33 PM
AdvancedSetup said:
Yes, and usually when I see it it's caused by bad RAM...
Quote
For we wrestle not against flesh and blood, but against principalities, against powers, and against the worldly governors, the princes of the darkness of this world...
#5
Posted 07 February 2009 - 12:01 AM
Thanks for the responses.
I actually did a memory test, over 7 hours, thinking the same thing. All came out ok.
Nothing in my event logs.
It's never happened before, nor did it happen with any other scans I did today to test (KAV & Spybot), which are much longer scans.
It happened that first time, then I did a bit of simple maintenance (chkdsk & a defrag)... happened a second time, with the exact same error (same numbers).
But the third time I tried it, a while ago, it was fine.
I also do a lot of memory/cpu intensive video processing, and nothing happens.
It seemed to happen shortly after the scan moved from the registry to files.
Weird. I'll keep my eye on it.
Thanks again for the responses... I was wondering if you guys had seen it before.
I actually did a memory test, over 7 hours, thinking the same thing. All came out ok.
Nothing in my event logs.
It's never happened before, nor did it happen with any other scans I did today to test (KAV & Spybot), which are much longer scans.
It happened that first time, then I did a bit of simple maintenance (chkdsk & a defrag)... happened a second time, with the exact same error (same numbers).
But the third time I tried it, a while ago, it was fine.
I also do a lot of memory/cpu intensive video processing, and nothing happens.
It seemed to happen shortly after the scan moved from the registry to files.
Weird. I'll keep my eye on it.
Thanks again for the responses... I was wondering if you guys had seen it before.
#6
Posted 07 February 2009 - 12:08 AM
There are occasional issues like this, but not enough to pin down a common cause. I have to assume it's something unique about the setup or drivers on each system that encounters it, but it's hard to tell.
Now that I think about it though, we can always use DebugView to get the developers a log of what happened.
Now that I think about it though, we can always use DebugView to get the developers a log of what happened.
Quote
For we wrestle not against flesh and blood, but against principalities, against powers, and against the worldly governors, the princes of the darkness of this world...
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Sign In
Create Account

Back to top










