my pc bluescreens a few minutes after i log in! I AM PISSED! i can't do anything to fix it as nothing works. i doubt it is anything internal as RedHat Linux 9 works ok (i am posting in it) i can boot into safemode and system restore didn't work. if you need my pc specs it is a...
AMD Athlon 950 MHZ with 3D-Now
384 megs ram
----------------------
Another case of diseased Tags 
. [Help] tags use only 1 pair of square brackets, thank you.
The Topic Has Been Tagged
// Seph
A few more details, for example what error you're getting when you bluescreen, would be helpful.
If you could get the STOP error and paramaters, it's easy to look up on Google to try to figure out why it's happening.
As well, if it happens in a certain file, post that here too.
-=edit=- Oh, and the tag is [Help], please don't make your own up. If you want to make your topic more urgent, then type [Help] Windows Bluescreens - URGENT! or something, don't change the tags. -=/edit=-
-=edit2=- Ah, Seph, you tag-machine you, I see you've fixed it. 
Well, my advice still stands, appending "URGENT!" to a topic will work better. -=/edit2=-
Talk about perfect tagging... 
now i just noticed that i log on real fast as ir gets it whether i log on or not. i tried Googling it andi got nothing. it was BAD_POOL_ERROR but i can boot linux ok so i doubt i have bad ram. please help.
oh and i can boot into safe mode.
Okay, when you get a blue screen, you'll see a message that says
STOP 0x00000081 (0x00234023, 0x134032423, 0x343234334, 0x342342340)
or some crazy stuff like that. That's what I need to know. Also, if there's a file listed (eg. tcpip.sys, ntoskrnl.sys, hidclass.sys, and so on) that'd be very useful to know.
Otherwise, what changes have you recently made to your system? Just installing Linux? That really shouldn't break Windows. If you have a virus scanner and made a boot disk (which you really should have done), boot from the disk and run the virus scanner to check for viruses.
If all else fails, you may have to reinstall windows.
thx so much for help. i'll rebootand give you the crap that you can actually understand.
***STOP: 0x000000c2 (0x00000007, 0x0000CD4, 0x020020C00B, 0x837D4FA8) no drivers listed.
From Common Stop Messages
Stop 0xC2 or BAD_POOL_CALLERThe Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:
* By allocating a memory pool size of zero bytes.
* By allocating a memory pool that does not exist.
* By attempting to free a memory pool that is already free.
* By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.
Possible Resolutions:
* A Stop 0xC2 messages might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
* A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.
* If you encounter a Stop 0xC2 message while upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.
Sounds to me like you have a screwed up driver installed, or perhaps some hardware is on its way out. If you go to the site linked above and scroll down to the 0xc2 area, you will see a few links to microsoft KB articles, although I'm not sure how much help they'll be. If you've recently updated a driver, that may very well be the source of your problem -- boot into safe mode and roll back the new driver.
Very recent versions of Linux overwrite BIOS information about the number
of cylinders a detected hard drive is reporting. Have a look at the FAQ of your
distribution on how to remedy this.
1: what's weird is i installed redhat linux 9 previously with no problems. i'll check my bios.
2: nope. nothing
3: i deleted my linux partitions to try and fix it and i had to use the grub command line to boot windows. boy was that hard. i did
rootnoverify (hd0,0)
chainloader +1
boot (hd0,0)
for those curious.
4: i think i fixed it. apparently, though i have to boot with the grub command line
Posts Merged.
Don't double-post, bump, or whatever.
-------------------
Stevie BM
Aqua-Soft Forums