Frequent Blue Screens, and suddenly nothing.

[Jay3k]

Hi........

Another computer in my house has been having a lot of STOP errors coming up, I've had multiple ones not always referring to the same thing. I've had....

STOP:0x0000008E (0xC000001D, 0xBF8268C9, 0xF532D7B4, 0x00000000)
win32k.sys - Address BF8268C9 base at BF800000, DateStamp 422511a2

----------------------------------------------

STOP: C000021a {FATAL SYSTEM ERROR} The Windows SubSystem system process terminated unexpectedly with a status of 0xC0000005 (0x00ffeae5 0x00ffe7e4). The system has been shut down.

----------------------------------------------

DRIVER_IRQL_NOT_LESS_OR_EQUAL.
STOP: 0x000000D1 (0x0000000C, 0x00000002, 0x00000000, 0xF93963E5)
rdbss.sys - Address F93963E5 base at F9396000, DateStamp 418047d5.

-----------------------------------------------

STOP: C0000135 {unable to locate component}: This application has failed to start because vct3216.dll was not found.



Those are some of the blue screens that come up, then suddenly windows stopped booting up.
The screen just stayed black, and the computer stopped trying to load anything.
So I tryed to re-install windows but the computer decided to restart itself halfway through, and now, when I try to re-install it, there is a message on-screen along the lines of, "sparrow.sys is corrupted".

Unfortunatly, because the computer wont load, I am unable to provide the minidumps which I was about to post just before it stopped loading

Any help would be appreciated. If I forgot to mention something, or there is something you need to know, just let me know.


Specs: (from memory, can't remember exactly)
Microsoft Windows XP Home Edition SP2
AMD Duron Processor
256mb RAM

 

[cpc2004]

Your PC has the following problem which is the symptom of hardware error. Most probably it is faulty motherboard.

0x0000008E (0xC000001D, 0xBF8268C9, 0xF532D7B4, 0x00000000)

 

[Jay3k]

Thank you for your help.

I managed to re-load windows, by using the start up disks and re-installing. The blue screen came on again, and have the minidumps to go with it. the errors were similar to the ones already mentioned. Just thought the minidumps might help more.

-J-

 

[cpc2004]

I find memory corruption at your minidump. Probably it is caused by overheat or faulty ram. Make sure that your PC is not overheat. If the problem still occurs, replace the ram.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff3bc8bd, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 80603367, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ff3bc8bd

FAULTING_IP:
nt!HvpGetCellMapped+113
80603367 894dcc mov [ebp-0x34],ecx

MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 80601558 to 80603367

TRAP_FRAME: f7233b7c -- (.trap fffffffff7233b7c)
ErrCode = 00000002
eax=8060326d ebx=e13ef5c0 ecx=00000078 edx=00000920 esi=e13a4b68 edi=000008a8
eip=80603367 esp=f7233bf0 ebp=f7233c38 iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010283
nt!HvpGetCellMapped+0x113:
80603367 894dcc mov [ebp-0x34],ecx ss:0010:f7233c04=c215d9d0
Resetting default scope

STACK_TEXT:
f7233c38 80601558 e13a4b68 0005c8a8 00000000 nt!HvpGetCellMapped+0x113
f7233c58 805fd5e8 0001009e 0012d3c4 e119ca90 nt!CmpConstructName+0xa8
f7233cb0 805f2d47 e194d248 00000003 0012d22c nt!CmQueryKey+0x4e
f7233d48 805283c1 00000346 00000003 0012d22c nt!NtQueryKey+0x20f
f7233d48 7ffe0304 00000346 00000003 0012d22c nt!KiSystemService+0xc4
0012d20c 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
8069bfb8-8069bfd5 30 bytes - hal!KeGetCurrentIrql+a94
[ 00 00 00 00 00 00 00 00:12 10 1a 02 54 29 c4 03 ]
8069bfd8-8069bfdc 5 bytes - hal!KeGetCurrentIrql+ab4 (+0x20)
[ 00 00 00 00 00:c4 03 de 20 1a ]
8069bfde-8069bfe0 3 bytes - hal!KeGetCurrentIrql+aba (+0x06)
[ 00 00 00:d4 03 1a ]
8069bfe2-8069bfe3 2 bytes - hal!KeGetCurrentIrql+abe (+0x04)
[ 00 00:f2 3d ]
8069bfe8-8069bfe9 2 bytes - hal!KeGetCurrentIrql+ac4 (+0x06)
[ 00 00:b8 36 ]
8069bfeb-8069bfed 3 bytes - hal!KeGetCurrentIrql+ac7 (+0x03)
[ 00 00 00:f0 df ff ]
8069bfef-8069bff3 5 bytes - hal!KeGetCurrentIrql+acb (+0x04)
[ 00 00 00 00 00:20 04 80 02 08 ]
8069bff6-8069bff7 2 bytes - hal!KeGetCurrentIrql+ad2 (+0x07)
[ 00 00:ac 20 ]
8069bffa-8069bffe 5 bytes - hal!KeGetCurrentIrql+ad6 (+0x04)
[ 00 00 00 00 00:2c a8 52 80 12 ]
57 errors : !hal (8069bfb8-8069bffe)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .trap fffffffff7233b7c ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------