
Quote: Originally Posted by
mikeneezy
This is starting to become a pattern. It will run flawlessly for several days then will BSOD. Its starting to get irritating. Please help!
All my specs are on the tab below. Attached is my BSOD/Perfmon reports.
Thank you all!!
Memory management caused by Nvidia (NvXDSync.exe. I would re-install or remove the sync file and test my memory with memtest
Download a copy of Memtest86and burn the ISO to a CD using Iso Recorder or another ISO burning program.
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\031411-17187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`0325fe90
Debug session time: Mon Mar 14 14:38:42.709 2011 (GMT-4)
System Uptime: 0 days 0:10:53.803
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8005780370, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8005780370
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: NvXDSync.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003107fd0 to fffff8000309a640
STACK_TEXT:
fffff880`07d09e98 fffff800`03107fd0 : 00000000`0000001a 00000000`00041790 fffffa80`05780370 00000000`0000ffff : nt!KeBugCheckEx
fffff880`07d09ea0 fffff800`0306c4f9 : ffffffff`00000000 00000000`026cffff fffffa80`00000000 fffffa80`097c2060 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`07d0a060 fffff800`0337009a : fffff8a0`025906d0 fffff880`07d0a3a0 00000000`00000000 fffffa80`097c2060 : nt!MmCleanProcessAddressSpace+0x679
fffff880`07d0a0b0 fffff800`0335537d : 00000000`40010004 00000000`00000401 000007ff`fffde000 fffffa80`079c7060 : nt!PspExitThread+0x56a
fffff880`07d0a1b0 fffff800`0308ddfa : fffff880`07d0a380 fffff880`01267d06 fffff880`07d0a6d0 fffff8a0`02012bb0 : nt!PsExitSpecialApc+0x1d
fffff880`07d0a1e0 fffff800`0308e140 : 00000000`0012fe30 fffff880`07d0a260 fffff800`033552f0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`07d0a260 fffff800`03099977 : fffffa80`097c2060 00000001`40000000 00000000`00000020 00000000`00989290 : nt!KiInitiateUserApc+0x70
fffff880`07d0a3a0 00000000`77531206 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0012fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77531206
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36024
fffff800`03107fd0 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Followup: MachineOwner
---------