BSOD on a nearly new computer

Ok, you're temps are much better now anyway. Just run it with one fan will be fine.

Nick, here is what I can get out of the Dump. When Boozad comes on, maybe he can get more out of it.

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, 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: fffffa800a7ffe80
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------

BUGCHECK_STR:  0x1a_41790
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  firefox.exe

Please make sure your Windows Updates are current. You have been getting some error reports from Firefox and from Windows Media Player, which there is no reason for, that I know of.

Just for a test, uninstall Firefox and use another browser for the time being as a test. I know you have run Memtest86+, but we may end up having to run it again, just not right now. Again, if you have any Gigabyte Utilities installed, uninstall all of them.

I'll take a look later when I'm at the PC. For a browser Nick I'd recommend Firefox, I've been using it for years with no issues.

Just keep Firefox for now, Nick. Let Boozad take a look when he gets time.

Right, here's what I can glean from this. A page table page has become corrupt going on the first parameter.

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, 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: fffffa800a7ffe80
Arg3: 000000000000ffff
Arg4: 0000000000000000

Looking at the stack it seems a user-mode APC is causing the problem:

Code:

fffff880`0c6d17e8  fffff800`03552166 nt!PspExitThread+0x56a
fffff880`0c6d17f0  fffff8a0`01f0da00
fffff880`0c6d17f8  fffff880`0c6d1ae0
fffff880`0c6d1800  fffffa80`0cf5aab0
fffff880`0c6d1808  fffffa80`0cf5aab0
fffff880`0c6d1810  fffff800`033fde80 nt!KiInitialPCR+0x180
fffff880`0c6d1818  00000000`00000002
fffff880`0c6d1820  fffffa80`1022d2a0
fffff880`0c6d1828  fffff800`03412580 nt!NonPagedPoolDescriptor
fffff880`0c6d1830  fffffa80`0cf5aab0
fffff880`0c6d1838  fffff800`033b5501 nt!ExFreePoolWithTag+0x411
fffff880`0c6d1840  00000006`00300008
fffff880`0c6d1848  fffffa80`11ea1c30
fffff880`0c6d1850  00000000`00000000
fffff880`0c6d1858  00000000`00000001
fffff880`0c6d1860  00000000`00000100
fffff880`0c6d1868  01d0ae6e`1d42eeb7
fffff880`0c6d1870  fffffa80`1022d400
fffff880`0c6d1878  fffffa80`11790e60
fffff880`0c6d1880  fffff8a0`0465d620
fffff880`0c6d1888  fffff8a0`0102d790
fffff880`0c6d1890  00000000`00000000
fffff880`0c6d1898  00000000`00000000
fffff880`0c6d18a0  00060030`00010002
fffff880`0c6d18a8  00000000`00000000
fffff880`0c6d18b0  fffff880`0c6d1ae0
fffff880`0c6d18b8  fffffa80`1022d2a0
fffff880`0c6d18c0  00000000`1438fd01
fffff880`0c6d18c8  00000000`00000001
fffff880`0c6d18d0  fffffa80`0cf5ab10
fffff880`0c6d18d8  fffffa80`0cf5ab00
fffff880`0c6d18e0  00000000`00000001
fffff880`0c6d18e8  fffff800`03537ecd nt!PsExitSpecialApc+0x1d
fffff880`0c6d18f0  00000000`00000001
fffff880`0c6d18f8  00000000`00000001
fffff880`0c6d1900  00000000`ffecc000
fffff880`0c6d1908  fffffa80`0d138060
fffff880`0c6d1910  fffffa80`0cf5aab0
fffff880`0c6d1918  fffff800`032720da nt!KiDeliverApc+0x2ca
fffff880`0c6d1920  00000000`00000100
fffff880`0c6d1928  fffffa80`0cf5ab70
fffff880`0c6d1930  00000000`00000001
fffff880`0c6d1938  fffff800`0328280d nt!KiCommitThreadWait+0x3dd
fffff880`0c6d1940  fffff880`0c6d19b8
fffff880`0c6d1948  00000000`00000000
fffff880`0c6d1950  fffffa80`11ea1c40
fffff880`0c6d1958  00000000`00000001
fffff880`0c6d1960  00000000`75242450
fffff880`0c6d1968  00000000`1438ec10
fffff880`0c6d1970  00000000`1438fd20
fffff880`0c6d1978  00000000`ffecc000
fffff880`0c6d1980  00000000`00000000
fffff880`0c6d1988  00000000`00001090
fffff880`0c6d1990  fffff880`0c6d1b60
fffff880`0c6d1998  fffff800`03272420 nt!KiInitiateUserApc+0x70

The Used Page Table Entries reference count has dropped below zero.

Code:

6: kd> dt nt!_MMPFN fffffa800a7ffe80
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`40000270 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`40000270 Void
   +0x010 Lock             : 0n1073742448
   +0x010 PteLong          : 0xfffff6fb`40000270
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : 0xffff
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

I think Driver Verifier is in order again.

Nick, can I ask what form of installation media you're using? 0x1As can be (in exceptional cases) down to a problem with the Windows kernel. From what I've seen it's rare but I'm just wondering if that media could possibly be corrupt.