I'm about to give up

[stumpedplshelp]

I'm starting to really get frustrated with this build. I've already changed the MB and ram.....now I have had a new wave on BSODs. Please help guys before I toss this POS out the window.

 

[CarlTR6]

Hi stumped. I will take a look at your dump; but please read the tutorial below and follow the instructions. This will help us help you better. We will have more to go on than just one dump.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

The dump blames memory corruption; but does not tell us the cause.

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`0303ee50
Debug session time: Wed Nov 17 10:40:31.536 2010 (GMT-5)
System Uptime: 0 days 0:33:47.800
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffb8005e03adb, 0, fffff80002e855ff, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )

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

2: 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: fffffb8005e03adb, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e855ff, 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 fffff800030a90e0
 fffffb8005e03adb 

FAULTING_IP: 
nt!MiAgeWorkingSet+4df
fffff800`02e855ff 410fb6471b      movzx   eax,byte ptr [r15+1Bh]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031167a0 -- (.trap 0xfffff880031167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff68000076108
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e855ff rsp=fffff88003116930 rbp=0000000000000000
 r8=0000000000000001  r9=fffffa8008b1bec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!MiAgeWorkingSet+0x4df:
fffff800`02e855ff 410fb6471b      movzx   eax,byte ptr [r15+1Bh] ds:0e10:00000000`0000001b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ef0849 to fffff80002e71740

STACK_TEXT:  
fffff880`03116638 fffff800`02ef0849 : 00000000`00000050 fffffb80`05e03adb 00000000`00000000 fffff880`031167a0 : nt!KeBugCheckEx
fffff880`03116640 fffff800`02e6f82e : 00000000`00000000 b15f5557`4abe4867 00000000`00000000 fffff800`02fa5bfe : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`031167a0 fffff800`02e855ff : 00000003`00000000 b1200000`1c969867 00000000`00000000 00000000`00006b12 : nt!KiPageFault+0x16e
fffff880`03116930 fffff800`02ef3a5e : fffffa80`08b1bec8 fffff880`00000001 00000000`00000001 fffff880`03116bb0 : nt!MiAgeWorkingSet+0x4df
fffff880`03116ae0 fffff800`02e85ee2 : 00000000`000007ec 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x496d6
fffff880`03116b80 fffff800`02e86173 : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03116bd0 fffff800`03115c06 : fffffa80`06a2db60 00000000`00000080 fffffa80`069abb30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`02e4fc26 : fffff880`02d64180 fffffa80`06a2db60 fffff880`02d6efc0 85119485`33665533 : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+4df
fffff800`02e855ff 410fb6471b      movzx   eax,byte ptr [r15+1Bh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+4df

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+4df

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+4df

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

I suggest that your run Memtest following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Let it run for at least 7 passes which will take 6-8 hours. Errors will show on your screen red. If you get errors, you can stop the test. If you get no errors, run Memtest again from a cold boot after your computer has been off for a while.

If you get no errors at all from Memtest, enable Driver Verifier following the instructions in this tutorial. Please read the instructions carefully. Upload any and all dumps generated by driver Verifier.

Driver Verifier - Enable and Disable

Don't forget to upload the files by running the tool in the first tutorial I listed.