It appears you have a bad disk sector if I read the message correctly. Type
chkdsk c: /r
in a command prompt.
--
..
--
"amadeusmozart" <guest@unknown-email.com> wrote in message
news:3b12b0e60d92e17bd56645e6e4695510@nntp-gateway.com...[color=blue]
>
> Sorry everyone, I didn't have my computer for a while. However, I took
> your advice and stressed all drivers not from Microsoft with the
> verifier program and it worked, here is what it showed on the memory
> dump.
>
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
> A device driver attempting to corrupt the system has been caught. This
> is
> because the driver was specified in the registry as being suspect (by
> the
> administrator) and the kernel has enabled substantial checking of this
> driver.
> If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and
> 0xA will
> be among the most commonly seen crashes.
> Arguments:
> Arg1: 000000a0, A CRC error was detected on the sector (synchronously).
> Arg2: b789cf00, Request Irp.
> Arg3: 8490bd18, Device object of the lower device.
> Arg4: 0325ac3d, Sector number on which the CRC error was detected.
>
> Debugging Details:
> ------------------
>
>
> BUGCHECK_STR: 0xc4_a0
>
> CUSTOMER_CRASH_COUNT: 1
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 2
>
> LAST_CONTROL_TRANSFER: from 843bf9c1 to 81f0eb0d
>
> STACK_TEXT:
> 805ecb04 843bf9c1 000000c4 000000a0 b789cf00 nt!KeBugCheckEx+0x1e
> 805ecb34 843bfd01 849ec008 0225ac3d 00007ef4
> crcdisk!VerifyOrStoreSectorCheckSum+0x111
> 805ecb64 843bf21a 00000056 b789cf00 0325abe7
> crcdisk!VerifyCheckSum+0xa9
> 805ecba0 843bf570 009e00d0 0000f000 805ecc5c crcdisk!CompleteXfer+0x16a
> 805ecbb4 82123d4d 889e0018 b789cf00 8d397570
> crcdisk!CrcScsiReadCompletion+0x20
> 805ecbec 81ee81fb 889e0018 b789cf00 805ecc5c
> nt!IovpLocalCompletionRoutine+0x16e
> 805ecc24 82123b95 b789cf00 00000000 849070e8
> nt!IopfCompleteRequest+0x11d
> 805ecc94 82943047 89f951d4 805eccd8 82946658
> nt!IovCompleteRequest+0x11c
> 805ecca0 82946658 b789cf00 00000001 00000000
> storport!RaidCompleteRequestEx+0x1c
> 805eccd8 8294331f 8823b008 805ecd40 805ecd50
> storport!RaidUnitCompleteRequest+0x8f
> 805ecce8 81eeb6a2 848e80a4 848e8030 00000000
> storport!RaidpAdapterDpcRoutine+0x28
> 805ecd50 81ee987d 00000000 0000000e d17c0678 nt!KiRetireDpcList+0x147
> 805ecd54 00000000 0000000e d17c0678 6faf62cf nt!KiIdleLoop+0x49
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> crcdisk!VerifyOrStoreSectorCheckSum+111
> 843bf9c1 6685d2 test dx,dx
>
> SYMBOL_STACK_INDEX: 1
>
> SYMBOL_NAME: crcdisk!VerifyOrStoreSectorCheckSum+111
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: crcdisk
>
> IMAGE_NAME: crcdisk.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 4549b1cb
>
> FAILURE_BUCKET_ID: 0xc4_a0_crcdisk!VerifyOrStoreSectorCheckSum+111
>
> BUCKET_ID: 0xc4_a0_crcdisk!VerifyOrStoreSectorCheckSum+111
>
> Followup: MachineOwner
>
>
> --
> amadeusmozart[/color]