New
#1
BSOD: 0x0000000a
This is pretty much the BSOD that's been coming up lately. Sometimes twice a day. Here are the files for analysis.
This is pretty much the BSOD that's been coming up lately. Sometimes twice a day. Here are the files for analysis.
These two were caused by memory corruption. I would run memtest to check it.
Download a copy of Memtest86 and 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.
Analysis
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\110910-30609-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 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x84617000 PsLoadedModuleList = 0x8475f810 Debug session time: Tue Nov 9 10:45:06.031 2010 (GMT-5) System Uptime: 0 days 22:13:56.390 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list .................................................. 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 00000007, A driver has unlocked a page more times than it locked it Arg2: 00018eab, page frame number Arg3: 00011f95, current share count Arg4: 00000000, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8468e561 to 846a8b0c STACK_TEXT: aedab75c 8468e561 00018eab 00000000 8b926848 nt!MiPfnReferenceCountIsZero+0x24 aedab778 846c7d53 58ac0000 8bb68000 8b91f000 nt!MiRemoveLockedPageChargeAndDecRef+0x16b aedab7cc 8489ffb9 8751e008 c0464548 00000002 nt!MiValidateImagePages+0x38c aedab7f0 84895c52 8751e008 c0464548 8751e008 nt!MiSwitchBaseAddress+0x4a aedab814 8483a6c8 8b91f000 00000000 00000000 nt!MiRelocateImageAgain+0xe1 aedab930 84847ed1 aedab984 0000000d aedab9d4 nt!MmCreateSection+0x531 aedab9a4 8482ed95 aedaba14 0000000d aedab9d4 nt!NtCreateSection+0x16e aedaba1c 8482e9f3 aedabad4 ad1437f8 aedaba54 nt!PfSnGetSectionObject+0x1a4 aedabab4 848a15cd 00dabad4 00000001 00000000 nt!PfSnPrefetchSections+0x1d4 aedabc34 8486fb56 8c5a1000 aedabc64 aedabc70 nt!PfSnPrefetchScenario+0x1a9 aedabcc8 8489c266 8487aa4d 8ae30f40 aedabd20 nt!PfSnBeginAppLaunch+0x382 aedabcd8 8489676d 89b38b45 00000000 00000000 nt!PfProcessCreateNotification+0x65 aedabd20 846d70f9 00000000 773c64d8 00000001 nt!PspUserThreadStartup+0x113 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiPfnReferenceCountIsZero+24 846a8b0c cc int 3 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiPfnReferenceCountIsZero+24 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0x4E_7_nt!MiPfnReferenceCountIsZero+24 BUCKET_ID: 0x4E_7_nt!MiPfnReferenceCountIsZero+24 Followup: MachineOwner ---------
Old drivers
Code:mchInjDrv.sys 0xa36e4a00 0x00000a00 1/11/2006 02:07:52 0x43c4aec8 0xa36e4000 SSPORT.sys 0xa36d7000 0x00007000 11/21/2006 23:41:42 0x4563d506 0xa36d0000
I've already run memtest and didn't receive any errors.