Gettin' Random BSOD's and Application Errors

Status
Not open for further replies.

greenflash

Posts: 99   +0
Hi Techspot stuff and members i just discovered this web page while i was searching BSOD's.

I have a desktop pc.Here is the configuration of my pc

Barton 2400 M@1666 mhz CPU
Abit AN7 Rev2 MB
2*512 MB TWINMOS CADT DUAL KIT DDR 400@333
80 GB SEAGATE SATA 8MB
200 GB SEAGATE SATA 8MB
SAMSUNG 763 MB
and TTLANPARTY TOWER CASE

Since last week im getting randomly displayed BSOD and app errors on my pc and seriosly confussed.I dunno what to do :(

Im going to try to upload my minidump files here.Pls help me to solve the problem

Im using Ghost image on my pc but still get BSODs do u recommend a fresh install or usage of old image file?
 
From the stack trace of the minidump, I believe that it is faulty ram.

STACK_TEXT:
ae24db44 804fc22a cb3e0000 e2e2c880 ae24dbec nt!MiResolveMappedFileFault+0x69
ae24db74 804f01e7 00000000 cb3e0000 c032cf80 nt!MiResolveProtoPteFault+0x122
ae24dbf0 804f2ace 00000000 cb3e0000 c032cf80 nt!MiDispatchFault+0x13b
ae24dc40 804fe383 00000000 cb3e0000 00000000 nt!MmAccessFault+0x5bc
ae24dc80 8050adb1 cb3e0000 00000000 8055d618 nt!MmCheckCachedPageState+0x461
ae24dd2c 8050ab65 867c61f0 80568440 85772c18 nt!CcPerformReadAhead+0x1f1
ae24dd74 804eb26b 867c61f0 00000000 85772c18 nt!CcWorkerThread+0x147
ae24ddac 80582e15 867c61f0 00000000 00000000 nt!ExpWorkerThread+0x100
ae24dddc 805014da 804eb196 80000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
nt!MiResolveMappedFileFault+69
804fc828 8b1e mov ebx,[esi]

SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiResolveMappedFileFault+69
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiResolveMappedFileFault+69
BUCKET_ID: 0xA_nt!MiResolveMappedFileFault+69
 
yes sir i reseated rams in random order and tested one by one and discovered that one of them corrupted ill send it to the distr. service to change
 
Status
Not open for further replies.
Back