Edited by MALC, 10 February 2008 - 09:50 AM.

BLUE SCREENS
#46
Posted 10 February 2008 - 09:27 AM
Register to Remove
#47
Posted 10 February 2008 - 10:23 AM
#48
Posted 11 February 2008 - 11:33 AM
#49
Posted 11 February 2008 - 12:07 PM
It is important that you do not email me with the information.
Please be sure that any reply you send is in this forum, so that everyone can see what had been said and follow what is going on.
It is important that you get all your important stuff that is on your computer safely copied to removal media, before we do any thing else.
Thanks
paws
Edited by paws, 11 February 2008 - 12:10 PM.
#50
Posted 11 February 2008 - 04:45 PM
Hi Paws, I will e-mail you with the information you require shortly but I thought you should have the following information asp.
1. IRQL_NOT_LESS_OR_EQUAL STOP: OXOOOOOOOX (OXOOOOOOOO, OXOOOOOOIC, OXOOOOOOO1,
OX804FCBA4)
2. DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP: OXOOOOOOD1 (OXOO801597, OXOOOOOOO2 OXOOOOOOOO,
OX862E8A6B).
3. STOP: OXOOOOOO8E (OXCOOOOOO5, OXBF855B27, OX9A30069C, OXOOOOOOOO) Win 32k. sys - Address BF855B27
base at BF8OOOOO, datestamp 45f013f6.
Regards
Malc.
Hi again MALC
Well. I've been snooping around alittle for error's. And as I mentioned very early in this topic, this is due to either a buggy driver or
faulty / wrong installed hardware, possible also the RAM. I'll explain myself further.
1. This error is typical for driver's / hardware / software (applications, malwareprograms etc)
Following message is from the site Aumha.org. Where i found the info.
Typically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
2. This error is typical for driver / hardware / RAM
Following message is from the site Aumha.org. Where i found the info.
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by faulty or mismatched RAM, or a damaged pagefile.
3. Typical symptom of Driver / hardware / Haxdoor Virus and several Rootkit's / Wrong Setting in BIOS of RAM clock rate
Have no message for this one, as the info was scattered all over the place in various webpages. Mostly all messages said the RAM was to blame. But i wouldn't ignore that the virus Haxdoor have this error message as a symptom, or that several rootkit's can cause this error. So basically, you have to decide to if you wanna pursue the driver / hardware or try HJT-log(?) If you decide for the first, try follow the steps given by Aumha.org for troubleshooting STOP error's, which can be found here: LINK
Those may or may not be the only solutions. I am sure Paws will investigate this also, so maybe theres more solutions to this.
I'll try put aside some more time to this issue, as this have been going on for awhile, and I am sure you want your PC up and running flawless.
Kind regards Abydos
Abydos
Asking for Technical Help
Preventing Malware Slow PC? Recovery Console!
"I am not young enough to know everything" - Oscar Wilde
#51
Posted 12 February 2008 - 02:52 AM
however:
MALC
please follow my previous directions and get all your important stuff safely copied off BEFORE you do anything else
Regards
paws
#52
Posted 13 February 2008 - 06:49 AM
#53
Posted 13 February 2008 - 07:40 AM
That is good news that you have the Dell Restore discs so if the worst comes to the worst you should be able to restore your computer to exactly how it was when it left the factory.
However lets not be goomy, as it may not come to that...........once you have copied off all your important stuff maybe we can follow some of the valuable suggestions already made here on the forum and get rid of those pesky blue screens!
Have a look here as it sets out a joly good way of copying your stuff.
http://forums.whatth...ngs_t16627.html
Let us know if you have any problems with it or when you have done it all
Regards
paws
#54
Posted 13 February 2008 - 09:45 AM
Reason for move: To keep all the important Stop Error information in the same thread.
Hi rand 1038 thanks for the tip.
paws I enclose another two STOP Notices;
1. STOP: COOOO21a [Fatal System Error] The windows Login Process system process terminated unexpectedly
with a status of OX8OOOOOO4 (OXOOOOOOOO OXOOOOOOOO) THE SYSTEM HAS BEEN SHUT DOWN.
2. BAD_POOL_HEADER STOP: OXOOOOOO19 (OXOOOOOO2O, OX86DE413O, OX86DE4148, OXOAO3OOO2)
Do you still want me to keep sending you these STOP Notices?
Regards
Malc.
#55
Posted 14 February 2008 - 11:25 AM
Register to Remove
#56
Posted 14 February 2008 - 01:42 PM
#57
Posted 14 February 2008 - 03:17 PM

#58
Posted 14 February 2008 - 06:04 PM
#59
Posted 15 February 2008 - 07:41 AM
Edited by paws, 15 February 2008 - 07:42 AM.
#60
Posted 19 February 2008 - 08:28 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users