hey i just built a new comp and put it all together...
im running windows xP servise pack 2
with 1g ram
Asus M2V-VIA motherboard
AM2-940 3500+
Gigabite GeForce 7300Gt

Computer had been constantly restartin and goin 2 the BSOD since i got it and started installin windows...first occured when formattin harddrive...i got no idea of what it could be... it happens while doin anythin prettymuch...also the comp jut conmpletely freezes...any help???

here are some of the dumps recorded...message if u need more

Attached Files

	Mini011407-01.zip (22.3 KB, 4 views)
	Mini011407-02.zip (29.1 KB, 2 views)
	Mini011407-03.zip (20.1 KB, 2 views)

Hi,

The first minidump is crashed with hardware error (instruction mis-aligned) and it is the symptom of hardware error. The other two minidumps maybe caused by hardware error as well. The faulty hardware may be ram, CPU or motherboard. I want more minidump to pinpoint which hardware is faulty. Meanwhile reaset the ram to another memory slot and run memtest to stress test the ram.


Mini011407-01.dmp BugCheck 24, {1902fe, f784b3bc, f784b0b8, f73d86c0}
Probably caused by : hardware ( Ntfs!aeskey+1b )

Mini011407-02.dmp BugCheck 1000007E, {c0000005, 80577cdf, f7a3fc2c, f7a3f928}
Probably caused by : ntkrnlpa.exe ( nt!IopDeleteFile+185 )

Mini011407-03.dmp BugCheck 100000D1, {0, 2, 1, f5dee5e0}
Probably caused by : nv4_mini.sys ( nv4_mini+7513e )

kk here r a few more thnx 4 this...

Attached Files

	Mini011407-03.zip (20.1 KB, 1 views)
	Mini011407-04.zip (24.2 KB, 1 views)
	Mini011407-05.zip (18.3 KB, 1 views)
	Mini011407-06.zip (23.9 KB, 1 views)

Hi,

Mini011407-04.dmp has 4 bytes memory corruption. This is the sign of fautly memroy (ie RAM or L2 Cache memory). Probably the failing hardware is RAM. If overclock the RAM, set the ram to original speed. Reseat the ram to another memory slot. If it still crashes, run memtest to stress test the ram.


Debug report of Mini011407-04.dmp

BugCheck 1000000A, {809da7a4, 2, 1, 804e205b}
Probably caused by : memory_corruption

Followup: memory_corruption
---------
kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 809da7a4, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e205b, address which referenced memory

Debugging Details:
------------------
WRITE_ADDRESS: 809da7a4
CURRENT_IRQL: 2

FAULTING_IP:
nt!CcSetDirtyInMask+22d
804e205b ff05a4a79d80 inc dword ptr ds:[809DA7A4h]

CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 804e2f02 to 804e205b

STACK_TEXT:
bab1fadc 804e2f02 86487ed0 bab1fb0c 0000f000 nt!CcSetDirtyInMask+0x22d
bab1fb64 804e0cb1 86487ed0 01ba9008 bab1fb98 nt!CcMapAndCopy+0x3ba
bab1fbe4 f73bc278 86158900 01815000 0000f000 nt!CcFastCopyWrite+0x211
bab1fc4c f743ba27 86158900 bab1fcc4 0000f000 Ntfs!NtfsCopyWriteA+0x23d
bab1fc80 805713da 86158900 bab1fcc4 0000f000 sr!SrFastIoWrite+0x77
bab1fd38 8053c808 00000870 00000000 00000000 nt!NtWriteFile+0x324
bab1fd38 7c90eb94 00000870 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
02cde0e8 00000000 00000000 00000000 00000000 0x7c90eb94

STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
!chkimg -lo 50 -db !nt
8 errors : !nt (804e2047-804e207f)
804e2040 e1 1f c1 e8 05 8d 04 *20 33 d2 42 d3 e2 8b 4d *c1 ....... 3.B...M.

804e2050 3b 4d f0 7f 3b 7d 31 *5b 10 75 11 ff 05 a4 a7 *9d ;M..;}1[.u......

804e2060 80 ff 43 08 ff 46 18 *18 47 60 09 10 d1 e2 75 *74 ..C..F..G`....ut

804e2070 33 d2 83 c0 04 42 83 *24 f4 01 8b 4d f0 83 55 *78 3....B.$...M..Ux


MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE

hey ...soz im kinda new around comps...how u set the speed of the ram...and wat is the l2 caching and if thats the problem...how i fix it lolz???

...ive stared running a memtest...completed 17% coverage and had 42 errors so far....so is my ram faulty lol....?

Yes, your ram is faulty.