Windows 7 Not a BSOD, but computer reboots occasionally in the evening

[howardtlcc]

When I come in to work my Win 7 computer has restarted. When I log back in Windows says it has recovered from an error. Any help figuring out what is crashing would be appreciated. I have attached a few dump files and screen images from CPU-Z as well as a report.

thanks!

Howard

 

[Trouble]

Two of your three dump files are very similar in that they report PAGE_FAULT_IN_NONPAGED_AREA

Cause

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

DUMP FILE:

..........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6a400455648, 0, fffff80002e7d27b, 5}

Could not read faulting driver name
[U][B]Probably caused by : memory_corruption[/B][/U] ( nt!MiAgeWorkingSet+1d1 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[U][B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B][/U]
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: fffff6a400455648, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e7d27b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
[U][B]Could not read faulting driver name[/B][/U]
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c5100
 fffff6a400455648 
FAULTING_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`02e7d27b 488b19          mov     rbx,qword ptr [rcx]
MM_INTERNAL_CODE:  5
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  vmware-vmx.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88003be77c0 -- (.trap 0xfffff88003be77c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6a400455648
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e7d27b rsp=fffff88003be7950 rbp=000000240045564e
 r8=0000000000000001  r9=fffffa800c5173f8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1d1:
fffff800`02e7d27b 488b19          mov     rbx,qword ptr [rcx] ds:fffff6a4`00455648=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002e3d3bf to fffff80002e92c40
STACK_TEXT:  
fffff880`03be7658 fffff800`02e3d3bf : 00000000`00000050 fffff6a4`00455648 00000000`00000000 fffff880`03be77c0 : nt!KeBugCheckEx
fffff880`03be7660 fffff800`02e90d6e : 00000000`00000000 fffff6a4`00455648 00000000`00000000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`03be77c0 fffff800`02e7d27b : 00000003`00000000 abd00001`5bed6867 00000000`00000000 00000000`0000cabd : nt!KiPageFault+0x16e
fffff880`03be7950 fffff800`02f0eac5 : fffffa80`0c5173f8 fffff880`00000001 00000000`00000001 fffff880`03be7bb0 : nt!MiAgeWorkingSet+0x1d1
fffff880`03be7b00 fffff800`02e7d826 : 00000000`000068ee 00000000`00000000 fffffa80`00000000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x4d786
fffff880`03be7b80 fffff800`02e7dcd3 : 00000000`00000008 fffff880`03be7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03be7bd0 fffff800`0312dfee : fffffa80`06754760 00000000`00000080 fffffa80`0671a040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03be7d40 fffff800`02e845e6 : fffff880`009b2180 fffffa80`06754760 fffff880`009bd0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03be7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`02e7d27b 488b19          mov     rbx,qword ptr [rcx]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!MiAgeWorkingSet+1d1
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
Followup: MachineOwner

So according to your attached images you have 2x4 gig sticks of Corsair 667 MHz (1333) memory which is being mis-identified as 533 MHz (1066). You should probably try to address this first by using the Motherboards BIOS Setup Utility and setting the RAM properly (manually), likely 1333 at 9 9 9 24 timings and a command rate of 2T.
Additionally AVG is a frequent offender in these types of issues so consider uninstalling it if Blue Screens persist follow up the normal uninstall with Link Removed to get rid of any lasting remnants. Get the proper one for you architecture.
Replace it with Link Removed due to 404 Error at least temporarily for testing
Keep us posted as to how you are progressing and attach any new .dmp files along with screen shots of the adjusted memory settings from CPUz.
Regards
Randy

EDIT: Almost forgot, one other thing, check with the Motherboard Mfg. and see if they have a more recent update for your system board's BIOS available.

 

[howardtlcc]

Thanks so much for your help. I got with Gigabyte yesterday (they were very helpful, nice surprise!) and we changed the bios settings for the memory. I will wait and see what happens and remove AVG and put on MS Security if the issue happens again.

Howard

 

[Trouble]

You're very welcome and glad to hear you are making some progress in addressing your problem. Also very good to hear that you were able to get some assistance from Gigabyte, I knew there was a reason why I liked their boards.
Please keep us posted as to your progress and yes please remove AVG and make sure you use the vendor's own removal tool that I linked to above to be sure that all remnants of the application or gone.
Regards
Randy