BSOD at random time

hollywaste · 18 Jun 2014

there is my debug file and i hope that it can be solve.

thanks.

PeregrineX · 18 Jun 2014

A page table page has been corrupted:

Code:

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80006c1110
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  nvSCPAPISvr.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030e9d50 to fffff80003078bc0

STACK_TEXT:  
fffff880`09cf36e8 fffff800`030e9d50 : 00000000`0000001a 00000000`00041790 fffffa80`006c1110 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09cf36f0 fffff800`030ab7d9 : 00000000`00000000 00000000`103a0fff fffffa80`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`09cf38b0 fffff800`03391631 : fffffa80`03db6140 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`09cf39d0 fffff800`03391a33 : 0000007f`00000000 00000000`10000000 fffffa80`00000001 fffffa80`05095630 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09cf3a90 fffff800`03077e53 : 00000000`00000000 00000000`10396000 fffffa80`04f18060 00000000`00000001 : nt!NtUnmapViewOfSection+0x5f
fffff880`09cf3ae0 00000000`77ca155a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`003ce808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ca155a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`030e9d50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

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

This means that your physical RAM is corrupted. I got this in another dump that also supports that:

Code:

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29041

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29041

That also indicates a hardware problem.

If you are still able to boot into windows, I would recommend running Memtest86, and check to see if there are any errors. If errors do sow up, I'm sorry to say that your RAM is indeed corrupted, and will need a replacement.

Best of luck,

PeregrineX