Jump to content

Malwarebytes

Blue screen during Quick Scan..


5 replies to this topic

#1
burf

    New Member

  • Members
  • Pip
  • 7 posts
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!

#2
GT500

    Mostly Cantankerous

  • Trusted Advisors
  • PipPipPipPipPipPip
  • 5,528 posts
  • Gender:Male
  • Location:Fortville, IN
That's odd... IRQL_NOT_LESS_OR_EQUAL is usually a hardware issue...

What do your event logs say?

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...

#3
AdvancedSetup

    Forum Deity

  • Administrators
  • PipPipPipPipPipPip
  • 22,575 posts
  • Gender:Male
  • Location:US
http://www.microsoft.com/technet/prodtechn...7.mspx?mfr=true
Ron Lewis
Manager, Online Support

Posted Image

Follow us: Twitter, Become a fan: Facebook

If you've posted to the HJT forum and it has been over 5 days without a response please send a Private Message asking for assistance.

#4
GT500

    Mostly Cantankerous

  • Trusted Advisors
  • PipPipPipPipPipPip
  • 5,528 posts
  • Gender:Male
  • Location:Fortville, IN

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
burf

    New Member

  • Members
  • Pip
  • 7 posts
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.

#6
GT500

    Mostly Cantankerous

  • Trusted Advisors
  • PipPipPipPipPipPip
  • 5,528 posts
  • Gender:Male
  • Location:Fortville, IN
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.

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

Follow Us