I have done a clean install, checked ram and passed. The computer will give faulty module errors with explorer and media player, others not as often. Then after a few errors it would give me a BSOD.
I have been running everything fine in Safe Mode for a day without issues. Below is a posting of the Minidump log.
---------
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
WARNING: Whitespace at end of path element
kd> .reload
Loading Kernel Symbols
.............................................................................................................
Loading unloaded module list
.........
Loading User Symbols
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: dba8748d, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf87234d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: dba8748d
FAULTING_IP:
win32k!LFONTOBJ:pfeMapFont+108
bf87234d 0089450c8955 add [ecx+0x55890c45],cl
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from bf846fa9 to bf87234d
STACK_TEXT:
f6c54d20 bf846fa9 f6c54d60 f6c54d48 f6c54d40 win32k!LFONTOBJ:pfeMapFont+0x108
f6c54d58 804da140 e13069c8 00000000 863ceba0 win32k!GreGetCharSet+0xbf
f6c54d58 7ffe0304 e13069c8 00000000 863ceba0 nt!KiSystemService+0xc4
0012be88 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
16 errors : !win32k (bf872340-bf8723b8)
bf872340 *00 89 55 f8 83 c2 04 c7 *00 f0 01 00 00 00 89 45 ..U............E
bf872350 *0c 89 55 ec 8b 45 c4 8b *45 f8 3b 01 0f 85 e1 b9 ..U..E..E.;.....
bf872360 *e8 ff 8b 4d ec 57 e8 ef *4d ff ff 85 c0 0f 84 d0 ...M.W..M.......
bf872370 *fb fb ff 8b 4d e8 8d 47 *fe 50 e8 db fe ff ff 85 ....M..G.P......
bf872380 *b9 0f 84 bc b9 fb ff 8b *08 e4 8d 47 10 50 e8 c7 ...........G.P..
bf872390 *c0 ff ff 85 c0 0f 84 a8 *4d fb ff 8b 4d e0 8d 47 ........M...M..G
bf8723a0 *fe 50 e8 b3 fe ff ff 85 *b9 0f 84 94 b9 fb ff 8b .P..............
bf8723b0 *18 f8 8b 48 24 b2 0c e8 *c0 fe ff ff 89 45 d0 8b ...H$........E..
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
Followup: memory_corruption
---------
I have been running everything fine in Safe Mode for a day without issues. Below is a posting of the Minidump log.
---------
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
WARNING: Whitespace at end of path element
kd> .reload
Loading Kernel Symbols
.............................................................................................................
Loading unloaded module list
.........
Loading User Symbols
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: dba8748d, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf87234d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: dba8748d
FAULTING_IP:
win32k!LFONTOBJ:pfeMapFont+108
bf87234d 0089450c8955 add [ecx+0x55890c45],cl
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from bf846fa9 to bf87234d
STACK_TEXT:
f6c54d20 bf846fa9 f6c54d60 f6c54d48 f6c54d40 win32k!LFONTOBJ:pfeMapFont+0x108
f6c54d58 804da140 e13069c8 00000000 863ceba0 win32k!GreGetCharSet+0xbf
f6c54d58 7ffe0304 e13069c8 00000000 863ceba0 nt!KiSystemService+0xc4
0012be88 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
16 errors : !win32k (bf872340-bf8723b8)
bf872340 *00 89 55 f8 83 c2 04 c7 *00 f0 01 00 00 00 89 45 ..U............E
bf872350 *0c 89 55 ec 8b 45 c4 8b *45 f8 3b 01 0f 85 e1 b9 ..U..E..E.;.....
bf872360 *e8 ff 8b 4d ec 57 e8 ef *4d ff ff 85 c0 0f 84 d0 ...M.W..M.......
bf872370 *fb fb ff 8b 4d e8 8d 47 *fe 50 e8 db fe ff ff 85 ....M..G.P......
bf872380 *b9 0f 84 bc b9 fb ff 8b *08 e4 8d 47 10 50 e8 c7 ...........G.P..
bf872390 *c0 ff ff 85 c0 0f 84 a8 *4d fb ff 8b 4d e0 8d 47 ........M...M..G
bf8723a0 *fe 50 e8 b3 fe ff ff 85 *b9 0f 84 94 b9 fb ff 8b .P..............
bf8723b0 *18 f8 8b 48 24 b2 0c e8 *c0 fe ff ff 89 45 d0 8b ...H$........E..
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
Followup: memory_corruption
---------