Repeating BSOD

PeterWesson · 22 Oct 2013

Hello,
so for the last few days I keep on experiencing BSODs. It always happens ca after one hour of work, no matter what I do, the computer can even stand "idle".
I already tried everything I could think of with my limited OS skills, also tried to restore the computer to earlier point in time.

Any advices, please?

Arc · 22 Oct 2013

Disable driver verifier now. It is no more needed.

When two dumps, one DV enabled and one without DV enabled, gives exactly the same result of memory corruption, it is not any driver issue at all.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.
_________________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, c080210a, ffff, 0}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+41a )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: c080210a
Arg3: 0000ffff
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82ada632 to 82ada060

STACK_TEXT:  
aefddaa8 82ada632 0c1d0002 0c2cffff 91ee4c28 nt!MiDeleteVirtualAddresses+0x41a
aefddb78 82ada2e7 91ee4c28 9c599280 b362b580 nt!MiRemoveMappedView+0x325
aefddba0 82c824f6 b362b580 00000000 ffffffff nt!MiRemoveVadAndView+0xe5
aefddc04 82ca0a0f 91ee4c28 0c1d0000 00000000 nt!MiUnmapViewOfSection+0x265
aefddc24 82a788c6 ffffffff 0c1d0000 097ed638 nt!NtUnmapViewOfSection+0x55
aefddc24 775d70f4 ffffffff 0c1d0000 097ed638 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
097ed638 00000000 00000000 00000000 00000000 0x775d70f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDeleteVirtualAddresses+41a
82ada060 cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+41a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521e9cb6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_41790_VRF_nt!MiDeleteVirtualAddresses+41a

BUCKET_ID:  0x1a_41790_VRF_nt!MiDeleteVirtualAddresses+41a

Followup: MachineOwner
---------