Random BSOD minidumps included

[Crazyerchris]

I've been reading th fourms for like the past 2 days and I still can't figure out whats causing my BSOD's here is everything


this is what it says when I type !process in the windows debugger


!process
GetPointerFromAddress: unable to read from 8055f534
PROCESS fb298020 SessionId: none Cid: 0be0 Peb: 7ffde000 ParentCid: 05d0
DirBase: 07d59000 ObjectTable: e17bf5e8 HandleCount: <Data Not Accessible>
Image: IEXPLORE.EXE
VadRoot 818b6e40 Vads 296 Clone 0 Private 4527. Modified 5884. Locked 0.
DeviceMap e28e6950
Token e17f1968
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
ffdf0000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 84340
QuotaPoolUsage[NonPagedPool] 16592
Working Set Sizes (now,min,max) (1892, 50, 345) (7568KB, 200KB, 1380KB)
PeakWorkingSetSize 9561
VirtualSize 140 Mb
PeakVirtualSize 148 Mb
PageFaultCount 26280
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 5284

*** Error in reading nt!_ETHREAD @ 81aef8c8

 

[cpc2004]

One minidump is crashed with 1 bit memory corruption and this is symptom of faulty ram. Run memtest to stress test the ram.

Mini120806-02.dmp
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: e4d3b32e, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804e6b95, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: e4d3b32e

FAULTING_IP:
nt!_wcsicmp+5
804e6b95 8b540856 mov edx,dword ptr [eax+ecx+56h]

MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: IEXPLORE.EXE
LAST_CONTROL_TRANSFER: from bf811955 to 804e6b95

STACK_TEXT:
f3aa2168 bf811955 e2fceab4 bf993c94 f3aa2710 nt!_wcsicmp+0x5
f3aa2258 bf810d8a f3aa22c0 e2fcea98 f3aa240c win32k!bGetNtoW_Win31+0x73
f3aa2388 bf8110e2 f3aa23f0 e2fcea98 f3aa240c win32k!bGetNtoD_Win31+0x179
f3aa23bc bf8072d9 f3aa2710 e2fcea98 f3aa23f0 win32k!PFEOBJ::bSetFontXform+0x53
f3aa2440 bf807462 e2fce978 00000000 00000002 win32k!RFONTOBJ::bInit+0x1a8
f3aa2458 bf812314 f3aa2710 00000000 00000002 win32k!RFONTOBJ::vInit+0x16
f3aa26c4 bf81c619 f3aa2710 000000f7 000000d7 win32k!GreExtTextOutWLocked+0x443
f3aa2708 bf82a454 e2fba9c8 000000f7 000000d7 win32k!GreExtTextOutWInternal+0x6e
f3aa2858 804df06b 30010bf4 000000f7 000000d7 win32k!NtGdiExtTextOutW+0x2b6
f3aa2858 7c90eb94 30010bf4 000000f7 000000d7 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013c8e8 00000000 00000000 00000000 00000000 0x7c90eb94

STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
804e6b96 - nt!_wcsicmp+6

[ 55:54 ]
1 error : !nt (804e6b96)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption