Hello,

I got a problem with my HP nc6400 notebook. It somehow produced a blue screen with error code: 000000C2. Does anyone have further idea to solve this? Here are what I already did:

1) I ran a memory test tool on the BIOS and it is ok.
2) I ran a memory test tool downloaded from www.memtest.org and it is ok.
3) I ran a memory test tool from microsoft webiste and it is also ok.
4) I replaced one memory with the new one borrowed from my friend. The problem still happen once or twice a day. (There are another memory located uner the keyboard so I cannot test by replacing this one)
5) I also picked a harddisk and usb mouse from my another notebook to test. The problem is still remaining.

The sample from Event viewer log are:

7/3/07 10:42:03 PM
Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 0213000d, parameter4 876226d8.

7/2/07 10:57:59 PM
Error code 10000050, parameter1 bad0b148, parameter2 00000000, parameter3 805b9e1d, parameter4 00000003.

7/2/07 7:42:31 PM
Error code 000000c2, parameter1 00000040, parameter2 00000000, parameter3 80000000, parameter4 00000000.

7/2/2007 11:06:28 AM
Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 02130006, parameter4 86ab7238.

7/1/2007 10:43:44 PM
Error code 10000050, parameter1 8c480000, parameter2 00000008, parameter3 8c480000, parameter4 00000000.

I do not know what to do with windows dump files. I have some at C:\Windows\minidump. So I attached if any of you can help me find the root cause of the problem.

Many thanks for your further help. Let me know if you wish more information.

I found some helpful information to extract windows dump files and here are the result. However, I have no idea to interpret the log files. Please help, thank you.

Today, I got give times blue screen and system reboot

Here are those windows dump files. Please kindly help. Many many thanks.

The five most recent ones are all the same. This could be a software problem, but without giving a clue. I would start by updating Windows. You should also update Zonealarm as your version is known to cause problems.

My updated

I had updated zonelarm to version 6 as your suggested, but the problem remains. Nowaday, I got approximately 6-10 crashed per day. Here are the sample of today's dump files. Can anyone help?

Did you install anything recently, hardware or software?

Have you run an anti-virus full scan lately?

Are you using anti-spyware utilities?

Is there not a windows update for this. AKA "BAD_POOL_CALLER"

If i am right the fix for is here http://support.microsoft.com/kb/309155

McAfee antivirus, ZoneAlarm (firewall with anti spyware) are all updated. Also with HP software/drivers updates.

Thanks for suggestion but KB309155 is applied to only windows 2000 family. My hardware configuration are:

HP nc6400 notebook
Intel Core Duo T2400
Ram 1.5Ghz
Harddisk 160 Gb.
Windows XP Professional SP2 (OEM, bundled with HP notebook)

Minidump #06 looks to have a conflict between McAfee and ZoneAlarm. From what I can find out mfetdik.sys is a Firewall module. If it is a Firewall then I would try uninstalling ZoneAlarm for problem isolation.

STACK_TEXT:
f78de8e8 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f78de938 aad0b417 886f7e38 00000000 f78de980 nt!ExFreePoolWithTag+0x2a3
f78de948 aad0aca7 876563d0 87656464 87656464 tcpip!TCPClose+0x16
f78de980 aac9c741 88abff18 876563d0 aac9c04d tcpip!TCPDispatch+0x101
WARNING: Stack unwind information not available. Following frames may be wrong.
f78dea28 804f14c6 00000000 87e43000 87e591c0 vsdatant+0x44741 <---------- Zonealarm.
f78dea44 aad02ae0 f78deafc 874e4b0c f78deac8 nt!IopfCompleteRequest+0xa2
f78dea54 aad02897 87813008 aad3fd00 f78ded2c tcpip!DelayDerefAO+0x57
f78deac8 aad0e2f4 87813008 0100007f 0000a407 tcpip!UDPDeliver+0x37a
f78deb20 aac80cb4 aac58d58 ffffffff f78deb64 tcpip!UDPRcv+0x164
f78deb64 804f15ad f78debdc 00000000 00000000 vsdatant+0x28cb4
f78deb94 eb2e7b3d 88bf2030 88fd62e8 88abff18 nt!IopfCompleteRequest+0x189
f78debc4 8058266b 876563d0 878459c8 89afc730 mfetdik+0x3b3d <----------- McAfee.
f78dec78 804eef95 88abff18 876563d0 876563d0 nt!IopCloseFile+0x2a7

And you are using the kernel debugging tool, and creating a user dump file.

Thanks for your reply. Dump #06 was created after I upgraded zonealarm from 5.5 to 6.5. I will keep monitor the problem and if it occure once again, I will uninstall zonealarm and change to use only windows firewall for a while to identify if zonealarm is the real root-cause. Will keep post in here for the update. Many thanks for helps ;-)

It reboots once again ;-(

Here is the newest dumpfile. Does anyone has a further suggestion? Thanks.

The 0xC2 event can be caused by bad drivers - run an 'sfc/scannow' and see if it repairs anything.

I did what you recommended

I did what you recommended (sfc /scannow). It took quite of times but it automatically closed that windows after finished. I did not see any warning so what does it mean? Anything to do next? or keep waiting?

Still getting problems?

Stay off-line and shut both McAfee and Zonealarm off via msconfig and reboot - play a non-online game for a few hours. See if you BSOD.

Problem is still remaining...please help

Hello:

I reinstalled windows XP from recovery CD and still got the problem. For this time, event viewer came with various error codes. For e.g.

Error code 1000007e, parameter1 c0000005, parameter2 000f000f, parameter3 f79d6c84, parameter4 f79d6980.

Error code 10000050, parameter1 bad0b148, parameter2 00000000, parameter3 805b9e1d, parameter4 00000000.

Error code 000000c2, parameter1 00000040, parameter2 00000000, parameter3 80000000, parameter4 00000000.

Have you any recommends? And I see something weird (what I make a blue highlight text. Can anyone tell me about these? Further thanks for you helps.

I found this thread which has similar bugchecks and failing routines that you're getting (see post #8). The culprit was Zonealarm.

BugCheck 1000007E, {c0000005, f000f, f79d6c84, f79d6980}
Probably caused by : ntkrpamp.exe ( nt!ObpRemoveObjectRoutine+df ) <-- Quite a few have crashed at this routine.

BugCheck C2, {40, 0, 80000000, 0}
Probably caused by : ntkrpamp.exe ( nt!ObpFreeObject+142 )

Suriya,
Your are using 2 different versions of Zonealarm (version 5.5 an 6.5) and they are unstable. They will cause undpredicatable problem such as BSOD.

vsdatant.sys Wed Apr 20 05:37:55 2005 (42657A33)
vsdatant.sys Mon Jun 19 07:26:23 2006 (4495e11f) --> Refer problem 1 and problem2


Mini072207-01.dmp BugCheck C2, {7, cd4, 2060001, 86fcd4f0}
Probably caused by : vsdatant.sys ( vsdatant+44741 )


BTW Memtest is not 100% accurate. Some faulty ram can pass memtest. If Suyria de-install ZA and the BSOD still occurs, RAM is the culprit.