I will experiment some more to see if I can trigger it without mm2 running.[/s]
edit 2: not more than a couple minutes when I edited this post above, I blue screened (only mm2 had been running the whole time).
As an aside, no strikethru bbcode makes me sad.
--------------------------------------------------------------------------------
I recently built a new computer, quad core q6600, 4 gig ram, x38 motherboard.
I had been getting infuriatingly random blue screen errors, "page fault in non-paged area".
I came across an article which helped me get the right tools to help figure out what was the root cause of the error; http://apcmag.com/7577/beat_those_bluescreen_blues
So I loaded up the mini dumps and so I see this..
Code: Select all
Loading Dump File [C:\WINDOWS\Minidump\Mini110107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.070321-2337
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Thu Nov 1 07:06:09.859 2007 (GMT-6)
System Uptime: 0 days 7:02:23.098
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa8009304000, 0, fffff97fff17efd4, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!NtUserfnINDEVICECHANGE+1bb )
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: fffffa8009304000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff97fff17efd4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: fffffa8009304000
FAULTING_IP:
win32k!NtUserfnINDEVICECHANGE+1bb
fffff97f`ff17efd4 8b4630 mov eax,dword ptr [rsi+30h]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: MediaMonkey.exe
CURRENT_IRQL: 1
TRAP_FRAME: fffffadfc12fdbb0 -- (.trap 0xfffffadfc12fdbb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000008006 rcx=fffffa8009303fd0
rdx=0000000000000016 rsi=0000000076647355 rdi=fffff97fff000000
rip=fffff97fff17efd4 rsp=fffffadfc12fdd40 rbp=000000001035cdd8
r8=0000000000000000 r9=fffffa8009303fd0 r10=000008f400000000
r11=fffffa8009303fd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!NtUserfnINDEVICECHANGE+0x1bb:
fffff97f`ff17efd4 8b4630 mov eax,dword ptr [rsi+30h] ds:8f86:00000000`76647385=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800010a6072 to fffff8000102e890
STACK_TEXT:
fffffadf`c12fdad8 fffff800`010a6072 : 00000000`00000050 fffffa80`09304000 00000000`00000000 fffffadf`c12fdbb0 : nt!KeBugCheckEx
fffffadf`c12fdae0 fffff800`0102d459 : 00000000`00000000 fffffadf`c12fdc30 fffffa80`0349e800 00000000`0000002c : nt!MmAccessFault+0xa1f
fffffadf`c12fdbb0 fffff97f`ff17efd4 : 00000000`00000000 00000000`1035cdd8 00000000`00000000 00000000`0000002c : nt!KiPageFault+0x119
fffffadf`c12fdd40 fffff97f`ff0a5a31 : fffff97f`f7c773f0 00000000`000902a2 00000000`0000002c fffffa80`09303fd0 : win32k!NtUserfnINDEVICECHANGE+0x1bb
fffffadf`c12fdde0 fffff800`0102e33d : 00000000`00000000 00000000`00000001 fffffadf`c12fe0a0 fffff800`01031286 : win32k!NtUserMessageCall+0x142
fffffadf`c12fde80 00000000`6b2b5e8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`0a4bd6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b2b5e8a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtUserfnINDEVICECHANGE+1bb
fffff97f`ff17efd4 8b4630 mov eax,dword ptr [rsi+30h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!NtUserfnINDEVICECHANGE+1bb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310
FAILURE_BUCKET_ID: X64_0x50_win32k!NtUserfnINDEVICECHANGE+1bb
BUCKET_ID: X64_0x50_win32k!NtUserfnINDEVICECHANGE+1bb
Followup: MachineOwner
---------
