WinXP crash with BSOD

Status
Not open for further replies.
Hi

My OS crashes randomly with the "blue screen of death". I happen to run a lot of regression tests on my machine. Am not sure if some code is causing this problem or it's due to some hardware or driver issue. Have attached the crash dump file.

The error message was

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x023f0000, 0x85306008). A dump was saved in: C:\WINDOWS\Minidump\Mini092905-01.dmp.

Srikanth
 

Attachments

  • Mini092905-01.zip
    27.6 KB · Views: 5
Hi,

Most probably it is faulty ram. Attach 6 to 8 minidumps if you want me to confirm it is bad ram.
 
Hi,

This is hardware error and probably it is faulty ram or motherboard.

The following case are crashed with bugcheck code C2 and the problem owner does not feed back the solution. You can send them a private message.
https://www.techspot.com/vb/topic18084-pg2.html&pp=20 (dna boy)
https://www.techspot.com/vb/showthread.php?p=175578#post175578 (bowie)
https://www.techspot.com/vb/topic17691-pg12.html&pp=20 (computra)

One confirmed case is faulty m/b
https://www.techspot.com/vb/topic32555.html (andys_uk)


Your debug report
Mini100305-01.dmp C2 (00000007, 00000cd4, 02410003, 85862e00) hclnfs+147dd -> nt!ExFreePoolWithTag+2c1
Mini092905-01.dmp 00 (00000000, 00000000, 00000000, 00000000) mvfs50+0x1ea03 -> nt!KeBugCheck+0x00000014

Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------
PROCESS_NAME: java.exe
FAULTING_IP:
nt!KeBugCheck+14
8053717f 5d pop ebp

EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: 8053717f (nt!KeBugCheck+0x00000014)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000001
NumberParameters: 0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x0
 
From the stack of one of the minidumps. I find the footprint of hclnfs.sys which is hummingbird. Upgrade hummingbird.

hclnfs hclnfs.sys Tue Jul 30 01:10:05 2002 (3D4576ED)

STACK_TEXT:
aa0c3714 80550fc5 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
aa0c3764 805503e3 85862e00 00000000 aa0c3788 nt!ExFreePoolWithTag+0x2c1
aa0c3774 aa8957dd 85862e00 8531c2c8 85862e00 nt!ExFreePool+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
aa0c3788 aa895a2d 85b976e0 85862e00 00000001 hclnfs+0x147dd
aa0c37c4 aa89b332 85b976e0 85862e00 00000001 hclnfs+0x14a2d
aa0c3a78 aa884d1d 00000000 84faf0c0 84faf008 hclnfs+0x1a332
aa0c3b38 aa884f61 85e676e8 84faf008 84faf0c0 hclnfs+0x3d1d
aa0c3b7c 804e13d9 85e573e0 84faf008 84faf0e4 hclnfs+0x3f61
aa0c3c0c 804e13d9 85b8d380 84faf008 84faf0c0 nt!IopfCallDriver+0x31
aa0c3c64 804e13d9 85a6eb48 84faf008 84faf008 nt!IopfCallDriver+0x31
aa0c3c74 8057c627 852c93a8 863e7040 00000001 nt!IopfCallDriver+0x31
aa0c3ca4 8056e943 859f2bb0 85a6eb48 00010080 nt!IopCloseFile+0x26b
aa0c3cd4 8056ea96 859f2bb0 012c93a8 863e7040 nt!ObpDecrementHandleCount+0x11b
aa0c3cfc 8056e9bc e2947250 852c93c0 000012c4 nt!ObpCloseHandleTableEntry+0x14d
aa0c3d44 8056ea06 000012c4 00000001 00000000 nt!ObpCloseHandle+0x87
aa0c3d58 804dd99f 000012c4 0314f930 7c90eb94 nt!NtClose+0x1d
aa0c3d58 7c90eb94 000012c4 0314f930 7c90eb94 nt!KiFastCallEntry+0xfc

Some minidumps crashes with bugcheck code 00 which is an invalid bugcheck code. They are crashed at module mvfs50.sys and it is clearcase. It is worthwhile to upgrade clearcase as well.
 
Hey
Thanks man...we too were suspecting clearcase...for your prev post regarding the m/b, the pc vendor asked us to reinstall the OS...that's something they say we got to do before they'll send in tech support...though i believe it won't be of much help...
anyways will see if we can upgrade clearcase/hummingbird
 
Status
Not open for further replies.
Back