Computing.Net > Forums > Windows XP > Blue screens - no reason- at a loss

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Blue screens - no reason- at a loss

Reply to Message Icon

Name: Alex2002
Date: January 21, 2006 at 14:30:35 Pacific
OS: XP Pro
CPU/Ram: 3200-64, 1GB
Comment:

As the title says, I'm at a total loss as to why today, all of a sudden and for no apparent reason, i've had FOUR blue screen errors.

Some of you might remember me posting this towards the end of last year. Well, the only way I managed to sort the problem was by reinstalling XP. I did so. And for the last 6 weeks XP has been solid as a rock. No problems whatsoever, not one BSOD, nothing. But today, I went to install the latest FTP Explorer. And during the install, the screen went blank, and a blue screen appeared. I restarted thinking it was maybe just a one off. But since then, i've had 3 others, all at random times. However, I have noticed that it seems to happen a lot when clicking the 'X' to close an application - although like I said its totally random. These are the exact same patterns and symptoms I noticed when XP used to crash a lot in my last install. It can't be a hardware issue, because it's been totally solid for the last 6 weeks. Just as my old install was until I started getting these random BSODs. The 4 so far all show different error codes:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x000066d2, 0x856a8350

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000000, 0x00000002, 0x00000001, 0x804f31df)

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000c5 (0x61546552, 0x00000002, 0x00000001, 0x8054b907)

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x00005661, 0x8580c1f0).

It's really annoying me - does anyone have any ideas as to why this should just happen for no reason, after the PC for being fine? Is it likely to be a driver issue? Whatever it is, would i be able to easily pinpoint what could be causing this? I ran a system restore back to yesterday afternoon, when all was fine, but, as I thought, it didn't fix the problem and I've already had one BSOD since then.

Any ideas much MUCH appreciated, as I really don't want to have to reinstall so soon after havin a fresh installation of XP!!

Thanks,

Alex



Sponsored Link
Ads by Google

Response Number 1
Name: per
Date: January 21, 2006 at 15:30:27 Pacific
Reply:

Stop errors.
http://aumha.org/win5/kbestop.htm

http://computervitals.com/


0

Response Number 2
Name: gilloz
Date: January 21, 2006 at 20:16:05 Pacific
Reply:

Alex: Does the BSOD happen when you are Online or Offline? Do you have any background programs running, like anti-virus or spyware removal programs? You could start by removing all your PCI cards (modem, audio, etc.) and just leave the video card with nothing else installed. Disconnect your CD-ROM and/or DVD drives. Exit all background running programs. Inotherwords, run your computer with minimal components and see if you get your BSOD. I had a similar experience and it finally came down to finding one bent pin in my IDE connector for my CD-ROM drive unit. Continue to install one component at a time and see if this helps. Small steps. Its a place to start troubleshooting. Hope this helps some what.


0

Response Number 3
Name: cpc2000
Date: January 22, 2006 at 07:22:57 Pacific
Reply:

Hi,

Bugcheck 0x000000c2 (0x00000007, 0x00000cd4, 0x00005661, 0x8580c1f0) is the sign of faulty ram. Run memtest to stress test the ram.


0

Response Number 4
Name: Alex2002
Date: January 22, 2006 at 10:24:07 Pacific
Reply:

Thanks for all the replies here.

Firstly, Gilloz, it happens when i'm online (well i'm on a broadband connection via a router, so i'm always online i suppose!) but I have noticed that when i'm on myspace.com it has a tendency to do it - although like i said, it's totally random. It can happen anytime. About the removal of all the hardware, this morning I took out most components and re-seated them. Things seemed fine but I got another blue screen a minute or two ago. I'm finding it so difficult to pinpoint this - because I can't simply make it happen, so I don't know if removing the hardware (process of elimination) would work, seeing as the error can just happen anytime?

CPC2000 -

I will run a memtest sometime, if i can find a floppy disk - haven't had to use one in a long time now. The thing about this, though, is if is faulty memory, then how come i had a good 6 weeks or so before this started happening again (after, like i said, the last time i had the exact same problems)? I'm 90% sure it's a software issue, because after reinstalling XP it was solid. On the flip side though, I don't know what sort of software issue would cause such errors!



0

Response Number 5
Name: Alex2002
Date: January 23, 2006 at 05:32:03 Pacific
Reply:

Well I ran a memtest. It found no problems. I've been on the PC for only about 20 minutes this morning and already had one BSOD. It goes beyond taking the proverbial now. I just can't put my finger on it! For some reason i'm leaning towards thinking it might be down to the graphics card or the hard disk. But, CHKDSK won't let me do a full scan it seems, i get "Windows was unable to complete the disk check" which worries me somewhat. And what about Graphics drivers? I can find none specific for my card, Inno3D Geforce 6600 - the website just points me to the generic Nvidia ones (v77.77)

These BSODs are so irritating because, they give no indication about what is wrong. It's all very well telling me about BAD_POOL_CALLERs but I have no idea what that's telling me - plus it seems to be a random error anyway, different codes, etc. so I just cant determine what's wrong.

Definitely not a heating issue, my PC is well ventilated and the BIOS reports the CPU at 32 degrees and the M/B at 30, which isn't bad at all.

Any more ideas?!

Cheers,
Alex


0

Related Posts

See More



Response Number 6
Name: Alex2002
Date: January 23, 2006 at 08:31:30 Pacific
Reply:

Just got another BSOD STOP error which I noted:

Stop 0x00000024

Which I looked up, and it says:

Stop 0x00000024 or NTFS_FILE_SYSTEM
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives.

So now i'm getting told about NTFS errors too! I don't know where to start.


0

Response Number 7
Name: cpc2000
Date: January 23, 2006 at 21:33:35 Pacific
Reply:

Hi,

Most probably it is faulty ram.
Zip 5 to 6 minidumps to a zip file and attach it at any webspace. I will study the dump and confirm the culprit. You can use a free service like rapidshare to post the minidump files : http://www.rapidshare.de/
You cann find the minidumps at the folder of \windows\minidump.

cpc2000


0

Response Number 8
Name: Alex2002
Date: January 24, 2006 at 05:11:43 Pacific
Reply:

Hi CPC,

Thanks for your offer, I've uploaded the files to my own space -

http://uk.geocities.com/alexncfc/minidump.zip

If possible could you let me know when you have completed the download so I can remove the files from my space :)

Thanks,

Alex


0

Response Number 9
Name: Alex2002
Date: January 24, 2006 at 15:24:08 Pacific
Reply:

Would just like to add that I have now ran Memtest and MS Windows Memory Diagnostic programs extensively, and neither of them have reported memory errors at all. I still don't think it's a hardware error.


0

Response Number 10
Name: cpc2000
Date: January 24, 2006 at 23:14:24 Pacific
Reply:

Hi,

According to the debug report, it is faulty ram. Some faulty ram can past memtest.

Suugestio
1. Reseat the ram
2. Downclock the ram
3. Upgrade panda firewall which is 3 years behind
4. Upgrade the lan card driver nvnetbus.sys and nvatabus.sys

Your debug report
Mini012106-01.dmp BugCheck C2, {7, cd4, 66d2, 856a8350}
Owning Process 867c69c8 Image: System
Probably caused by : ntoskrnl.exe ( nt!ExFreePoolWithTag+2be )

Mini012106-02.dmp BugCheck 1000000A, {0, 2, 1, 804f31df}
Owning Process 85517990 Image: iedw.exe
Probably caused by : memory_corruption ( nt!MmCreateSection+369 )

Mini012106-03.dmp BugCheck 100000C5, {61546552, 2, 1, 8054b907}
Owning Process 867c69c8 Image: System
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+156 )

Mini012106-04.dmp BugCheck C2, {7, cd4, 5661, 8580c1f0}
Owning Process 866489f0 Image: i_view32.exe
Probably caused by : ntoskrnl.exe ( nt!ExFreePoolWithTag+2be )

Mini012106-05.dmp BugCheck 100000C5, {0, 2, 1, 8054ba39}
Owning Process 867c69c8 Image: System
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+fd )

Mini012206-01.dmp BugCheck C2, {7, cd4, 589e, 850bf910}
Owning Process 867c69c8 Image: System
Probably caused by : ntoskrnl.exe ( nt!ExFreePoolWithTag+2be )

cpc200


0

Response Number 11
Name: Alex2002
Date: January 25, 2006 at 01:33:14 Pacific
Reply:

Hi cpc,
I'll look into it and see how it goes. Thanks much for taking the time to check them and come up with some info and ideas!

Alex


0

Response Number 12
Name: Alex2002
Date: January 26, 2006 at 14:12:28 Pacific
Reply:

Just thought i'd post back - i've been trying a few different methods before conceding that my memory is faulty. None had worked, until I moved my pagefile from drive C to drive E. And it hasn't crashed since. So no idea if the problem is sorted or not but hopefully so!


0

Response Number 13
Name: cpc2000
Date: January 26, 2006 at 19:15:03 Pacific
Reply:

Hi,

If it is paging space problem, you will get bugcheck 77 or 7A or nt status code c0000006 (ie inpage I/O error). Repost if your windows still crashes.

cpc2000


0

Response Number 14
Name: Alex2002
Date: January 29, 2006 at 07:14:47 Pacific
Reply:

Unfortunately the PC has still crashed a few times since. Looks like my 'solution' didn't work.


0

Response Number 15
Name: cpc2000
Date: January 30, 2006 at 08:01:40 Pacific
Reply:

Hi Alex,

Your windows is crashed less freqent as before and some of my suggestion are working. Attach the latest minidump at webspace. Maybe I have new finding.

cpc2000


0

Response Number 16
Name: Alex2002
Date: January 30, 2006 at 08:19:20 Pacific
Reply:

Thanks for getting back to me.

I was all ready to post the latest minidump file, which would have been today as i got a BSOD not that long ago - but I went to the MINIDUMP folder, and the latest one is the 25th Jan! It hasn't been creating them since then for some reason, even though it's enabled in system properties. So I don't know what to do now.


0

Response Number 17
Name: cpc2000
Date: January 30, 2006 at 16:35:28 Pacific
Reply:

Hi,

Post the system event log 1001/1003 here.


0

Response Number 18
Name: Alex2002
Date: January 31, 2006 at 03:24:14 Pacific
Reply:

Hi again,

I've checked the event log, and the last 1003 entry was on the 28th - 3 days ago, and it has crashed since then, but i'll post anyway:

Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 00005898, parameter4 86690140.

I've realised that the system is not creating dump files because I have moved my PageFile to another drive. I'll move it back, and if (more likely when!) it crashes again, i'll upload the dump file.

Cheers


0

Response Number 19
Name: Alex2002
Date: January 31, 2006 at 11:44:36 Pacific
Reply:

Just had another crash, i've uploaded the minidump this time:

http://uk.geocities.com/alexncfc/Mini013106-01.zip

Cheers



0

Response Number 20
Name: cpc2000
Date: January 31, 2006 at 22:40:54 Pacific
Reply:

Probably your latest crash is caused by faulty ram. Why do you still use panda firewall which is 3 years behind?

Suugestion
1. Run memtest
2. Reseat the ram
3. Downclock the ram



0

Response Number 21
Name: Alex2002
Date: February 1, 2006 at 10:23:50 Pacific
Reply:

Hi again,

I use Outpost Firewall v1, not Panda. I've always wondered, can a firewall go out of date? Is there any reason why I should change it?

Also,

1) I have ran memtest for hours on end and it has found no errors.
2) I've reseated the RAM many times with no success.
3) The memory is DDR400, yet it still crashes even when I downclock to 333Mhz.

I'm going to wipe the hard drive soon and reinstall I think.


0

Response Number 22
Name: cpc2000
Date: February 1, 2006 at 11:08:10 Pacific
Reply:

Hi,

Outpost firewall is also called Panda Firewall. An outdated firewall may also causes blue screen problem. Some faulty ram can pass memtest test. If you have more than one memory module, take out memory module one by one and reboot windows normally. If windows does not crash, the removed memory module is faulty.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows XP Forum Home


Sponsored links

Ads by Google


Results for: Blue screens - no reason- at a loss

I'm at a loss www.computing.net/answers/windows-xp/im-at-a-loss/168864.html

trouble shoot Blue Screen www.computing.net/answers/windows-xp/trouble-shoot-blue-screen/146183.html

No users at profile selection screen!!! www.computing.net/answers/windows-xp/no-users-at-profile-selection-screen/13179.html