Need some help to analyse this file

Attached Files

debuglog.txt (13.3 KB, 3 views)

It is faulty RAM. As you know the minidump is the snap shot windows kenel when the crash occurs. If you attach 3 or 4 more debug reports. I can confirm whether it is faulty RAM or not.

2 More logs, by the way thank for the help

Attached Files

	debuglog2.txt (17.2 KB, 2 views)
	debuglog3.txt (14.1 KB, 1 views)

It is confirmed it is bad ram as your debug reprot has memory corruption.

CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs
!chkimg -lo 50 -db !Ntfs
2 errors : !Ntfs (f840e7c2-f840efc2)
f840e7c0 fe ff *46 f3 ab 66 c7 85 d4 fe ff ff 0a 07 66 c7 ..F..f........f.

...

f840efc0 b4 89 *5a 1c 8b 83 10 01 00 00 c1 e8 09 8b 4d 2c ..Z...........M,


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

It my first posting here and i got anwser below 2 hours WOW

Your a master man

Thank for the help