New
#11
How many sticks of RAM do you have. Errors are often detected after 8 passes too. The latest dumps does not reveal anything specific.
Upload a screenshot of your hard disk using crystal disk info and "Summary" tab using Speccy:
- Speccy - System Information - Free Download
- CrystalDiskInfo - Software - Crystal Dew World
- Screenshots and Files - Upload and Post in Seven Forums
Make a hard drive test from the hard drive manufacturers website:
Run these tools and delete anything they may find:
ESET online scanner:
Edit: The previous dump states what exactly is causing the BSOD-s so I need to know how many sticks of RAM you have and how many passes you took memtest for.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {8887, fffffa8003fd7fd0, fffffa8003fd3290, 604} Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000008887, The subtype of the bugcheck. Arg2: fffffa8003fd7fd0 Arg3: fffffa8003fd3290 Arg4: 0000000000000604 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_8887 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: dwm.exe CURRENT_IRQL: 2 STACK_TEXT: fffff880`055567c8 fffff800`02e927ce : 00000000`0000001a 00000000`00008887 fffffa80`03fd7fd0 fffffa80`03fd3290 : nt!KeBugCheckEx fffff880`055567d0 fffff800`02eb23fb : fffffa80`03fd7fd0 fffffa80`0a729ec8 fffffa80`03fbb260 fffffa80`0a729ec8 : nt!MiUnlinkPageFromLockedList+0x1de fffff880`05556850 fffff800`02e9fed5 : 00000000`00000000 00000001`547ff860 00000000`00000000 fffffa80`0a729ec8 : nt!MiResolveTransitionFault+0x16b fffff880`055568e0 fffff800`02e9e893 : 00000000`00153e62 000007fe`f9155124 fffff683`ff7c8aa8 fffffa80`0a729ec8 : nt!MiResolveProtoPteFault+0x325 fffff880`05556970 fffff800`02e8e549 : 00000000`00000000 000007fe`f9155124 00000000`039bf630 fffff880`00000000 : nt!MiDispatchFault+0x1c3 fffff880`05556a80 fffff800`02e800ee : 00000000`00000008 000007fe`f9155124 00000000`0027bc01 00000000`020db0e0 : nt!MmAccessFault+0x359 fffff880`05556be0 000007fe`f9155124 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`039bf618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f9155124 STACK_COMMAND: kb SYMBOL_NAME: ZEROED_PAGE_CORRUPTED FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware_ram DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x1a_8887_ZEROED_PAGE_CORRUPTED BUCKET_ID: X64_0x1a_8887_ZEROED_PAGE_CORRUPTED Followup: MachineOwner ---------