BSOD - Various Errors

Hi Gasmanjc.

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.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
___________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffba3061ee4e8, 0, fffff800034043e0, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+2b0 )

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

0: 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: fffffba3061ee4e8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800034043e0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003513100
GetUlongFromAddress: unable to read from fffff800035131c0
 fffffba3061ee4e8 Nonpaged pool

FAULTING_IP: 
nt!MiGetWorkingSetInfo+2b0
fffff800`034043e0 498b4228        mov     rax,qword ptr [r10+28h]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800983c760 -- (.trap 0xfffff8800983c760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff68000379000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034043e0 rsp=fffff8800983c8f0 rbp=fffff8800983cb60
 r8=fffff88009cd0b30  r9=fffff70001085f20 r10=fffffba3061ee4c0
r11=fffff700010885a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiGetWorkingSetInfo+0x2b0:
fffff800`034043e0 498b4228        mov     rax,qword ptr [r10+28h] ds:fffffba3`061ee4e8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000335853b to fffff800032dbbc0

STACK_TEXT:  
fffff880`0983c5f8 fffff800`0335853b : 00000000`00000050 fffffba3`061ee4e8 00000000`00000000 fffff880`0983c760 : nt!KeBugCheckEx
fffff880`0983c600 fffff800`032d9cee : 00000000`00000000 fffffba3`061ee4e8 fffff880`0983c700 fffffa80`09561060 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`0983c760 fffff800`034043e0 : fffff880`0983cb60 00000000`00000000 00000000`00000010 fffff880`00000000 : nt!KiPageFault+0x16e
fffff880`0983c8f0 fffff800`0363ba25 : 00000000`fffeffff 00000000`0917c101 fffffa80`09561060 fffffa80`00000001 : nt!MiGetWorkingSetInfo+0x2b0
fffff880`0983c980 fffff800`032dae53 : 00000000`00001260 fffffa80`09561060 00000000`00000000 00000000`0545e028 : nt! ?? ::NNGAKEGL::`string'+0x4c5f3
fffff880`0983ca70 00000000`76d314ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0545e008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d314ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetWorkingSetInfo+2b0
fffff800`034043e0 498b4228        mov     rax,qword ptr [r10+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiGetWorkingSetInfo+2b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+2b0

BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+2b0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_nt!migetworkingsetinfo+2b0

FAILURE_ID_HASH:  {8a7a1726-eb26-0c5c-558a-74066c003dba}

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

Thanks for your reply ARC. I tried running memtest before and couldnt get it to work. Kept telling me I needed a 64 bit version. I will have another go at it.

"64"

There ate two DV enabled crash dumps, and both of them indicates the same thing.

Code:

BugCheck C9, {23b, fffff88005f51710, fffff980046c2cf0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

Update ASmedia USB3 and Intel USB3 from ASRock > Z77 Extreme4

How old the keyboard and mouse are? Can you replace those, on a test basis?

After doing those, run the computer normally and observe the situation. Let us know for any further BSODs.