-
July 26th, 2006 07:32 PM
#21
Usually there is a stop error, lots of numbers and a file name
EG
STOP_ERROR_OF_BSOD
0x00000000 ( 0x00000000, 0x00000000, 0x000000000, 0x0000000000)
filename.ext
Easier if we had all the info.......als
http://en.wikipedia.org/wiki/Blue_screen_of_death
On the right you will see the various blue screens for windows....
MLF
How people treat you is their karma- how you react is yours-Wayne Dyer
-
July 26th, 2006 07:54 PM
#22
Member
BAD_POOL_HEADER
0x00000019 (0x00000020, 0x86913ae0, 0x86913ed0, 0x0a7e0001)
it doesnt specify any file name
-
July 26th, 2006 08:04 PM
#23
Faulty driver
Windows XP Service Pack 2 is usually a good thing. However, it's not without it's problems. Most notably is it's crashing of more 'sloppily' written drivers. If you're now experiencing the BAD_POOL_HEADER Blue Screen Of Death on bootup and have a NetGear wireless network card in your machine, then remove it. More than likely this will allow you to boot. I've also heard of some LinkSys wireless network cards causing this same error as well. As of the writing of this article, there are no new drivers from either LinkSys or NetGear. I've also been unable to find any support on their site about the issue. If your NetGear card uses the Atheros chipset, then you may be able to use those drivers to get back up and running.
from a quick scan looks like it has to do with older NIC drivers....
http://www.google.ca/search?hl=en&q=...00000019&meta=
MLF
How people treat you is their karma- how you react is yours-Wayne Dyer
-
July 26th, 2006 10:19 PM
#24
Member
i dont have any netgear equipment onboard and i have up to date NIC drivers and i haven installed any new hardware / upgrade driver prior to the problem
so i guess either i could look for the faulty equipment driver or reformat it (its about time to reformat it again anyway)
-
July 26th, 2006 10:20 PM
#25
Member
btw i have a broadcom wireless nic card and a realtek 10/100Mbps card (came with OEM)
-
July 27th, 2006 02:08 AM
#26
try and update your nic driver.......maybe all your drivers
if it doesnt crash in safe mode....it usually is a driver\application issue
MLF
How people treat you is their karma- how you react is yours-Wayne Dyer
-
July 27th, 2006 03:54 AM
#27
Member
yeah thanks for the advice MLF i would try to do that
-
July 27th, 2006 02:31 PM
#28
One other possibility,
I notice that you have some HP stuff?
I have heard of problems with HP drivers and XP SP2. You might go to the HP website and get the latest drivers for whatever you have.
If that doesn't work straight off, please try uninstalling and reinstalling the device(s) with the new drivers.
If you cannot do someone any good: don't do them any harm....
As long as you did this to one of these, the least of my little ones............you did it unto Me.
What profiteth a man if he gains the entire World at the expense of his immortal soul?
-
July 27th, 2006 03:03 PM
#29
Member
yeah i have gotten all latest OEM Drivers.. i tried the ones in MS's updates site but it messes up my system so i stick with HP's drivers.
but yeah i will try to reinstall the drivers later
-
July 27th, 2006 03:10 PM
#30
Personally...I never use MSes drivers....ever
unless its some MS product.
I always use the manufacturers site...or the machines OEM drivers...(dell\hp etc)...and they are pretty good at releasing new drivers when a MS patch breaks them
MLF
How people treat you is their karma- how you react is yours-Wayne Dyer
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
|
|
Bookmarks