BlueScreen Page_Fault only on Cold Boot

[JohnPC]

Hello,

I'm new to the 7 forum, though I have been reading the posts now for several weeks now and have found them to be really helpful. Thanks!

I've been tinckering with my new Win 7 -64bit self-built machine, and I have to say that I haven't felt this excited about a new computer since my first encounter with a TRS-80-2...
Anyhow, I've had a consistant pattern of BlueScreen Page_Fault errors, and I'm very lost. Once the system reboots after the first crash, it runs excellent from that point on...

I downloaded the Win7 debugging tools/symbol sets thinking that I might fumble my way through them, but they are way over my head... So, I have attatched the mini dump files with the hope that someone might have an idea as to how I should go forth from this point.

Regards,
John

 

[zigzag3143]

Hello,

I'm new to the 7 forum, though I have been reading the posts now for several weeks now and have found them to be really helpful. Thanks!

I've been tinckering with my new Win 7 -64bit self-built machine, and I have to say that I haven't felt this excited about a new computer since my first encounter with a TRS-80-2...
Anyhow, I've had a consistant pattern of BlueScreen Page_Fault errors, and I'm very lost. Once the system reboots after the first crash, it runs excellent from that point on...

I downloaded the Win7 debugging tools/symbol sets thinking that I might fumble my way through them, but they are way over my head... So, I have attatched the mini dump files with the hope that someone might have an idea as to how I should go forth from this point.

Regards,
John

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

Given memory is the first likely cause
I would
download memtestx86 and run it for 5 passes

run a system file check
type cmd in search>right click and run as admin>SFC /SCANNOW

let us know the results

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\022610-30716-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03011000 PsLoadedModuleList = 0xfffff800`0324ee50
Debug session time: Fri Feb 26 16:22:20.075 2010 (GMT-5)
System Uptime: 0 days 0:00:51.371
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa2108f10ca0, 0, fffff800033708af, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!NtCreateSection+17e )

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

1: 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: fffffa2108f10ca0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033708af, 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 fffff800032b90e0
 fffffa2108f10ca0 

FAULTING_IP: 
nt!NtCreateSection+17e
fffff800`033708af 4c396640        cmp     qword ptr [rsi+40h],r12

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002a569a0 -- (.trap 0xfffff88002a569a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a005255660 rbx=0000000000000000 rcx=fffff8a004cdc820
rdx=ffffffdffd801390 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033708af rsp=fffff88002a56b30 rbp=fffff88002a56ca0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff8a005255660 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!NtCreateSection+0x17e:
fffff800`033708af 4c396640        cmp     qword ptr [rsi+40h],r12 ds:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003100b19 to fffff80003082f00

STACK_TEXT:  
fffff880`02a56838 fffff800`03100b19 : 00000000`00000050 fffffa21`08f10ca0 00000000`00000000 fffff880`02a569a0 : nt!KeBugCheckEx
fffff880`02a56840 fffff800`03080fee : 00000000`00000000 00000000`00000000 fffffa80`00000000 fffff8a0`05255678 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`02a569a0 fffff800`033708af : fffff880`02a56b80 00000000`00000000 00000000`00000000 fffffa80`08f10c98 : nt!KiPageFault+0x16e
fffff880`02a56b30 fffff800`03082153 : fffffa80`09070060 00000000`0010a118 fffff880`02a56bc8 00000000`00000000 : nt!NtCreateSection+0x17e
fffff880`02a56bb0 00000000`60402e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0010a0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x60402e3d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtCreateSection+17e
fffff800`033708af 4c396640        cmp     qword ptr [rsi+40h],r12

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!NtCreateSection+17e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x50_nt!NtCreateSection+17e

BUCKET_ID:  X64_0x50_nt!NtCreateSection+17e

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

 

[JohnPC]

Hi Ken,
I just updated to MemTest 3.4 (I had a very old version 1.6) and I'm about to boot off a CD to run the test.
I have tried running " SFC/ SCANNOW" before, but all I get is a CMD prompt window which stays open about 1/2 second with no other dialogs... so I'm not sure if it's working or if I am missing something.
I'll post an update on MemTest as soon as I get something.
Thanks,
John

 

[JohnPC]

Ken,
Well, I managed to do a SFC scan and it did reveal some corrupted files which it couldn't fix :-(
On the other hand, the good news is that the MEMTEST in 3.4 mode went through without a glitch, showing no errors.

In the mean time, I also tried something else. I backed up my current install and tried to start from scratch with a fresh one. The SFC on the new one revealed no errors present, the MEMTEST was fine, but I still got a critical error in the event log and a BlueScreen which only happened on the first ColdBoot this morning.
Besides this issue, everything is working so excellently (Amiga Forever/ WinXP Mode too) that I guessing I'll just have too live with it for now...
Thanks for the input,
John

 

[win7clutz]

Since it appears that mem is not the issue, might want to talk to the SSD manufactures and see if there's a firmware upgrade for those drives...

 

[JohnPC]

Thanks, I'll check up on that too.
It seems OCZ updates their firmware often.

Updated:
My OCZ is running the latest firmaware 1.5,
and my Kingston is so new, that there is nothing available yet.
So I'm assuming that is not the issue.