Recently re installed Windows 7 Home Premium x64 OEM on my system and have been getting pretty random BSODs and reboots. I've had this problem before and eventually it went away before re installing windows, but I'm still using all of the same hardware.
AMD Phenom II X4 970 @ 3500
ASUS M4A88TD-V
8gb
2x AMD HD6870
60gb OCZ Agility
500gb WD Caviar Black
Any help would be very appreciated.
Thanks in advance.
These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
1-Memtest.
RAM - Test with Memtest86+*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*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.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
2-Driver verifier
Driver Verifier - Enable and DisableUsing Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
In addition to zigzag3143's helpful suggestions, and after following those suggestions, please proceed through the followingCode:
- Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011512-12246-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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 Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e70 Debug session time: Sun Jan 15 03:20:15.692 2012 (UTC - 7:00) System Uptime: 0 days 1:07:09.394 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ......................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8800531ffab, fffff88003ae2750, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8800531ffab, Address of the instruction which caused the bugcheck Arg3: fffff88003ae2750, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: dxgmms1!VidMmReferencePrimaryAllocationForSubmission+27 fffff880`0531ffab 488b28 mov rbp,qword ptr [rax] CONTEXT: fffff88003ae2750 -- (.cxr 0xfffff88003ae2750) rax=f7fff8a0075aaf80 rbx=0000000000000000 rcx=fffff8a009b43520 rdx=fffff8a011945a00 rsi=fffff88003ae3720 rdi=fffffa8009940010 rip=f7fff8800531ffab rsp=fffff88003ae3120 rbp=0000000000000002 r8=f7fff88003ae3780 r9=fffff8800532e8c0 r10=f7fff8a00cbd4b50 r11=fffff88003ae3540 r12=f7fff8a009b43520 r13=0000000000000000 r14=0000000000000001 r15=0000000000000001 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 f7fff880`0531ffab ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: swtor.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffffa8008846b98 to f7fff8800531ffab STACK_TEXT: fffff880`03ae3120 fffffa80`08846b98 : fffff800`02ebebeb fffff880`04e40314 f7fff800`02ebf711 00000000`00000000 : 0xf7fff880`0531ffab fffff880`03ae3128 fffff800`02ebebeb : fffff880`04e40314 f7fff800`02ebf711 00000000`00000000 f7fff880`03ebff0b : 0xfffffa80`08846b98 fffff880`03ae3130 fffff880`0532c050 : 00000000`00000001 fffff880`03ae34e8 fffff880`00000001 fffff880`00000000 : nt!KeWaitForMultipleObjects+0x271 fffff880`03ae33e0 fffff8a0`10de8790 : fffff880`03ae3401 00000000`00000000 00000000`00000000 fffffa80`093f7bb0 : dxgmms1!VidSchWaitForEvents+0x9c fffff880`03ae3440 fffff880`03ae3401 : 00000000`00000000 00000000`00000000 fffffa80`093f7bb0 00000000`00000000 : 0xfffff8a0`10de8790 fffff880`03ae3448 00000000`00000000 : 00000000`00000000 fffffa80`093f7bb0 00000000`00000000 f7fffa80`093f7410 : 0xfffff880`03ae3401 CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 51 errors : !nt (fffff80002ebb15f-fffff80002ebbf3f) fffff80002ebb150 01 00 00 e8 f8 05 0c 00 48 8b 4d 80 48 8b 45 *80 ........H.M.H.E. ... fffff80002ebb1b0 24 90 00 00 00 44 0f 29 ac 24 a0 00 00 00 44 *07 $....D.).$....D. ... fffff80002ebb230 38 48 8d 54 24 70 48 *81 54 24 58 48 8d 55 80 *40 8H.T$pH.T$XH.U.@ fffff80002ebb240 89 54 24 50 48 0f ba 74 24 48 00 48 8b cc e8 *b5 .T$PH..t$H.H.... fffff80002ebb250 02 12 00 4c 8b a4 24 *80 01 00 00 4c 8b ac 24 90 ...L..$....L..$. fffff80002ebb260 01 00 00 4c 8b b4 24 *90 01 00 00 48 81 c4 a8 01 ...L..$....H.... ... fffff80002ebb2d0 0f 6f b8 c0 00 00 00 4c 8b a0 18 01 00 00 4c *83 .o.....L......L. ... fffff80002ebb2f0 01 00 00 fb 65 48 8b 1c 25 88 01 00 00 65 0f *a6 ....eH..%....e.. ... fffff80002ebb4d0 48 48 8d 54 24 70 48 *81 54 24 58 48 8d 55 80 *40 HH.T$pH.T$XH.U.@ fffff80002ebb4e0 89 54 24 50 48 8b cc *e0 c4 f3 11 00 48 8d 44 24 .T$PH.......H.D$ ... fffff80002ebb500 50 66 44 0f 6f 48 60 66 44 0f 6f 50 70 66 44 *07 PfD.oH`fD.oPpfD. ... fffff80002ebb550 8b b8 30 01 00 00 48 *83 b8 08 01 00 00 48 8b b0 ..0...H......H.. ... fffff80002ebb5c0 48 89 4c 24 08 48 89 54 24 10 4c 89 44 24 18 *44 H.L$.H.T$.L.D$.D fffff80002ebb5d0 89 4c 24 20 9c 48 83 *e4 30 fa 65 48 8b 0c 25 20 .L$ .H..0.eH..% ... fffff80002ebb700 40 44 0f 29 44 24 50 44 0f 29 4c 24 60 44 0f *21 @D.)D$PD.)L$`D.! ... fffff80002ebb720 24 90 00 00 00 44 0f 29 ac 24 a0 00 00 00 44 *07 $....D.).$....D. ... fffff80002ebb990 41 03 c9 0f 32 41 89 80 88 00 00 00 8b 0d ae *71 A...2A.........q fffff80002ebb9a0 23 00 41 89 90 8c 00 00 00 41 03 c9 0f 32 41 *81 #.A......A...2A. fffff80002ebb9b0 80 80 00 00 00 41 89 90 84 00 00 00 8b 0d ba *72 .....A.........r ... fffff80002ebba10 0f 23 ca 48 8b 45 68 *40 8b 55 70 0f 23 d0 0f 23 .#.H.Eh@.Up.#..# fffff80002ebba20 da 48 8b 95 80 00 00 00 33 c0 0f 23 f0 0f 23 *f2 .H......3..#..#. ... fffff80002ebba50 c0 74 12 44 8b c0 b9 *d1 01 00 00 0f 32 83 e0 *f4 .t.D........2... ... fffff80002ebba70 65 4c 8b 0c 25 18 00 00 00 0f 21 c0 0f 21 ca *40 eL..%.....!..!.@ fffff80002ebba80 89 45 58 48 89 55 60 *07 21 d0 0f 21 da 48 89 45 .EXH.U`.!..!.H.E fffff80002ebba90 68 48 89 55 70 0f 21 f0 0f 21 fa 48 89 45 78 *40 hH.Up.!..!.H.Ex@ fffff80002ebbaa0 89 95 80 00 00 00 33 c0 0f 23 f8 65 f6 04 25 *42 ......3..#.e..%B ... fffff80002ebbac0 f8 7b 23 00 45 0b c0 74 08 41 8b c8 0f 32 44 *83 .{#.E..t.A...2D. ... fffff80002ebbaf0 c8 0f 32 89 85 90 00 00 00 89 95 94 00 00 00 *83 ..2............. fffff80002ebbb00 0d 77 79 23 00 0f 32 *81 85 a8 00 00 00 89 95 *a4 .wy#..2......... ... fffff80002ebbb20 00 89 95 a4 00 00 00 *b1 d9 01 00 00 0f 32 83 e0 .............2.. fffff80002ebbb30 fc 0f 30 66 41 f7 81 08 02 00 00 55 03 74 6c *41 ..0fA......U.tlA fffff80002ebbb40 8b 81 e0 01 00 00 49 *83 91 e8 01 00 00 0f 23 c0 ......I.......#. ... fffff80002ebbd80 0f 83 21 02 00 00 81 *32 26 00 00 80 0f 85 00 01 ..!....2&....... fffff80002ebbd90 00 00 48 8b 42 20 4c *83 40 08 4c 89 81 90 00 00 ..H.B L.@.L..... ... fffff80002ebbdb0 4c 89 81 a0 00 00 00 *44 8b 40 20 4c 89 81 a8 00 L......D.@ L.... fffff80002ebbdc0 00 00 4c 8b 40 28 4c *81 81 b0 00 00 00 4c 8b 40 ..L.@(L......L.@ ... fffff80002ebbde0 00 00 00 4c 8b 40 40 4c 89 81 e8 00 00 00 4c *83 ...L.@@L......L. ... fffff80002ebbe00 f8 00 00 00 44 8b 40 *50 44 89 41 34 0f 28 40 60 ....D.@PD.A4.(@` ... fffff80002ebbe30 0f 28 80 90 00 00 00 0f 29 81 30 02 00 00 0f *20 .(......).0.... ... fffff80002ebbe70 29 81 70 02 00 00 0f *20 80 e0 00 00 00 0f 29 81 ).p.... ......). ... fffff80002ebbea0 0f 28 91 c0 01 00 00 0f 28 99 d0 01 00 00 0f *20 .(......(...... fffff80002ebbeb0 a1 e0 01 00 00 0f 28 *a1 f0 01 00 00 0f 28 b1 00 ......(......(.. ... fffff80002ebbf00 00 00 44 0f 28 b9 90 02 00 00 0f ae 51 34 66 *83 ..D.(.......Q4f. fffff80002ebbf10 41 42 66 89 44 24 20 *40 8b 81 98 00 00 00 48 *81 ABf.D$ @......H. fffff80002ebbf20 44 24 18 8b 41 44 89 44 24 10 66 8b 41 38 66 *81 D$..AD.D$.f.A8f. fffff80002ebbf30 44 24 08 48 8b 81 f8 00 00 00 48 89 04 24 48 *83 D$.H......H..$H. MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE STACK_COMMAND: .cxr 0xfffff88003ae2750 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------
- Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011612-13026-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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 Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be70 Debug session time: Mon Jan 16 08:48:06.623 2012 (UTC - 7:00) System Uptime: 0 days 0:00:20.324 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff8800b46c228, fffff8800b46ba90, fffff80002fb207a} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1ee ) Followup: Pool_corruption --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800b46c228 Arg3: fffff8800b46ba90 Arg4: fffff80002fb207a Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800b46c228 -- (.exr 0xfffff8800b46c228) ExceptionAddress: fffff80002fb207a (nt!ExDeferredFreePool+0x00000000000001ee) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800b46ba90 -- (.cxr 0xfffff8800b46ba90) rax=f7fffa8006c9b870 rbx=0000000000000001 rcx=fffffa8006c9b870 rdx=fffff8a007307900 rsi=0000000000000000 rdi=fffff8a007331e00 rip=fffff80002fb207a rsp=fffff8800b46c460 rbp=0000000000000000 r8=fffff8a0073011b0 r9=fffff8a0073078f0 r10=fffff8a007307900 r11=0000000000000001 r12=fffffa8006c9b140 r13=0000000000000000 r14=0000000000000016 r15=0000000000000001 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!ExDeferredFreePool+0x1ee: fffff800`02fb207a 48895008 mov qword ptr [rax+8],rdx ds:002b:f7fffa80`06c9b878=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b60e0 ffffffffffffffff FOLLOWUP_IP: nt!ExDeferredFreePool+1ee fffff800`02fb207a 48895008 mov qword ptr [rax+8],rdx FAULTING_IP: nt!ExDeferredFreePool+1ee fffff800`02fb207a 48895008 mov qword ptr [rax+8],rdx BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff80002fb34c1 to fffff80002fb207a STACK_TEXT: fffff880`0b46c460 fffff800`02fb34c1 : 00000000`000004b6 fffff8a0`033dde60 00000000`008e008e fffff8a0`0756bf00 : nt!ExDeferredFreePool+0x1ee fffff880`0b46c4f0 fffff880`0108c513 : ffffffff`ffffffff 00000000`00000000 fffff8a0`6e664d46 00000000`00000000 : nt!ExFreePoolWithTag+0x411 fffff880`0b46c5a0 fffff880`0108ce19 : ffffffff`ffffffff fffffa80`09f5f250 fffffa80`07ef3010 fffffa80`09ff5b90 : fltmgr!DeleteNameCacheNodes+0x143 fffff880`0b46c5e0 fffff880`0109c2af : fffffa80`09f5f250 fffffa80`09ff5b90 00000000`00000000 00000000`00000000 : fltmgr!PurgeStreamNameCache+0xa9 fffff880`0b46c620 fffff880`01093a30 : fffffa80`0a06ecd0 fffffa80`07ef3010 00000000`00000000 fffffa80`09f0e840 : fltmgr!FltpPurgeVolumeNameCache+0x7f fffff880`0b46c660 fffff880`0108cd4b : fffffa80`07ef3010 00000000`00000000 fffffa80`09f0e840 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1a04 fffff880`0b46c6a0 fffff880`0106f06a : fffffa80`0a153010 fffffa80`07c7ede0 00000000`00f8001e fffffa80`06d359f0 : fltmgr!FltpReinstateNameCachingAllFrames+0x4b fffff880`0b46c6d0 fffff800`02e80bb6 : 00000000`00000000 fffffa80`09a26010 00000000`00000000 fffff880`0106e0a2 : fltmgr!FltpPassThroughCompletion+0x8a fffff880`0b46c710 fffff880`01220cb4 : fffffa80`09777010 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x336 fffff880`0b46c800 fffff880`012a7eda : fffff8a0`07359bc0 fffffa80`07d6d180 00000000`00000000 00000000`00000701 : Ntfs!NtfsExtendedCompleteRequestInternal+0x114 fffff880`0b46c840 fffff880`01219ba0 : fffffa80`09777010 fffffa80`09e19c10 fffff880`0b46c901 fffff880`0b46c900 : Ntfs!NtfsCommonSetInformation+0xef1 fffff880`0b46c920 fffff880`0106c23f : fffffa80`09e19fb0 fffffa80`09e19c10 fffffa80`09777010 fffff880`0b46c948 : Ntfs!NtfsFsdSetInformation+0x11c fffff880`0b46c9a0 fffff880`0106a6df : fffffa80`07c7ede0 fffffa80`09e19c10 fffffa80`07c7ed00 fffffa80`09e19c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`0b46ca30 fffff800`0315e2ed : 00000000`000000ae fffff880`0b46cca0 00000000`00000000 fffffa80`09efbc80 : fltmgr!FltpDispatch+0xcf fffff880`0b46ca90 fffff800`02e7d813 : 00000000`000005b8 fffffa80`09ff2660 00000000`0314e4e8 00000000`000000ae : nt!NtSetInformationFile+0x909 fffff880`0b46cbb0 00000000`7767f92a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0314e4c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7767f92a SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ExDeferredFreePool+1ee FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption STACK_COMMAND: .cxr 0xfffff8800b46ba90 ; kb FAILURE_BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+1ee BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+1ee Followup: Pool_corruption ---------
Begin by updating the following drivers.
Code:scmndisp fffff880`0148b000 fffff880`01495000 Wed Jan 17 00:48:03 2007 (45add4b3) 00008b81 scmndisp.sys AsUpIO fffff880`02c20000 fffff880`02c26000 Sun Jul 05 20:21:38 2009 (4a515fb2) 0000edf8 AsUpIO.sys
- scmndisp Netgear Neutral Wireless Solution driver: Support Home Page
- AsUpIO ASUS hardware monitoring software related driver: ASUSTeK Computer Inc. -Support- Drivers and Download
Your first blue screen crash could be related to system or hardware problems.
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors.
In case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
Your second blue screen crash is related to your hard disk and may be due to hard disk errors or your antivirus program.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
I did see AVG secure search installed on your computer. Please uninstall AVG secure search through add/remove programs in control panel (Start Menu -> Control Panel -> Uninstall a program).
What other antivirus software do you currently use on your system? Have you had any other antivirus programs in the past, and if so, how were they uninstalled?
Thank you both for the quick replies. I ran the Memtest for one pass with no errors, I will run overnight tonight for better verification. I also Ran the driver verifier and had a bsod. Will include the dump with this post. I've also ran the scannow with no errors and did a disk check on both hdds also with no errors. Also, uninstalled the AVG search. I'm currently running Microsoft Security Essentials but that's it as I reformatted and reinstalled 2 days ago. I'm wondering if it would be a good idea to udate the bios, don't think I've done that yet.
The last crash was due to AsUpIO.sys and was a driver verified crash (as expected). It is also one of the drivers I recommended updating. Please update the driver, or uninstall the software associated with it for testing purposes.
As for updating the BIOS, yours is from 2010, so it is current with Windows 7. We may try updating it as a last resort, but as of now, I see no need. Since BIOS flashing is risky, we try to narrow problems down to other possible causes first.
I uninstalled pretty much all the provided ASUS software, and have been running the verifier, got another BSOD. Took a while to get Windows to load, kept rebooting, but got it back up now. Looks like something different now. I really do appreciate this help, off to see if it will BSOD again. Hehe.
None of these were verifier based, but all point toward a related problem. It may be an underlying driver, but I am not seeing one. These are all likely do to a conflict involving your RAM. Definitely let us know what happens when you run those memory tests.Code:
- Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011612-17253-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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 Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`0303fe70 Debug session time: Mon Jan 16 16:47:08.926 2012 (UTC - 7:00) System Uptime: 0 days 0:14:52.284 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C1, {fffff98043bdeee0, fffff98043bde697, 690118, 32} Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: fffff98043bdeee0, address trying to free Arg2: fffff98043bde697, address where one bit is corrupted Arg3: 0000000000690118, (reserved) Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error Debugging Details: ------------------ BUGCHECK_STR: 0xC1_32 SPECIAL_POOL_CORRUPTION_TYPE: 32 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 IRP_ADDRESS: fffffa7fffffff89 LAST_CONTROL_TRANSFER: from fffff80002f023a3 to fffff80002e725c0 STACK_TEXT: fffff880`079cf688 fffff800`02f023a3 : 00000000`000000c1 fffff980`43bdeee0 fffff980`43bde697 00000000`00690118 : nt!KeBugCheckEx fffff880`079cf690 fffff800`02f79393 : fffff880`00000003 fffffa80`0a4a3b60 00000000`00000293 fffff800`03305dfe : nt!MiCheckSpecialPoolSlop+0x83 fffff880`079cf6d0 fffff800`02fa5356 : fffff800`02e02000 00000000`2b707249 00000000`006a6040 00000000`00000001 : nt!MmFreeSpecialPool+0x1d3 fffff880`079cf800 fffff800`03317026 : fffffa80`07dbf402 fffffa80`07dbf420 00000000`00000000 fffff980`43bdeee0 : nt!ExDeferredFreePool+0xf13 fffff880`079cf8b0 fffff800`033175ec : fffff800`02e91a22 fffff980`43bdeee0 fffff880`079cfca0 00000000`00000000 : nt!VfIoFreeIrp+0xe6 fffff880`079cf8e0 fffff800`02e91a22 : fffff880`079cfca0 fffff980`43bdeee0 00000000`00000000 ffffffff`fffffffd : nt!IovFreeIrpPrivate+0x5c fffff880`079cf920 fffff800`02e4516d : fffffa80`00000001 00000000`00000000 fffff980`5f81ce00 fffff800`0318a5a7 : nt!IopCompleteRequest+0x402 fffff880`079cf9f0 fffff800`0316abc7 : 00000000`00000000 fffff880`079cfb60 fffff980`5f81cee0 00000000`00000000 : nt!IopPostProcessIrp+0x4d fffff880`079cfa70 fffff800`0312a495 : 00000000`00000000 fffff880`079cfb68 fffff880`079cfb60 00000000`00000501 : nt!IoRemoveIoCompletion+0xe7 fffff880`079cfb00 fffff800`02e71813 : fffffa80`0a4a3b60 00000000`02d1f538 fffff880`079cfbc8 fffff880`079cfc20 : nt!NtRemoveIoCompletion+0x145 fffff880`079cfbb0 00000000`7748f74a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`02d1f518 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7748f74a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiCheckSpecialPoolSlop+83 fffff800`02f023a3 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiCheckSpecialPoolSlop+83 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xC1_32_nt!MiCheckSpecialPoolSlop+83 BUCKET_ID: X64_0xC1_32_nt!MiCheckSpecialPoolSlop+83 Followup: MachineOwner ---------
- Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011612-17191-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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 Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03042e70 Debug session time: Mon Jan 16 17:34:29.767 2012 (UTC - 7:00) System Uptime: 0 days 0:00:24.109 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C1, {fffff98010938c10, fffff98010938317, 903e8, 32} Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: fffff98010938c10, address trying to free Arg2: fffff98010938317, address where one bit is corrupted Arg3: 00000000000903e8, (reserved) Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error Debugging Details: ------------------ BUGCHECK_STR: 0xC1_32 SPECIAL_POOL_CORRUPTION_TYPE: 32 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: userinit.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002f053a3 to fffff80002e755c0 STACK_TEXT: fffff880`09bf30e8 fffff800`02f053a3 : 00000000`000000c1 fffff980`10938c10 fffff980`10938317 00000000`000903e8 : nt!KeBugCheckEx fffff880`09bf30f0 fffff800`02f7c393 : fffffa80`00000004 00000000`00000001 00000000`00000293 fffff800`03308dfe : nt!MiCheckSpecialPoolSlop+0x83 fffff880`09bf3130 fffff800`02fa8356 : fffff800`02e05000 00000000`2b707249 00000000`00038d00 00000000`00000001 : nt!MmFreeSpecialPool+0x1d3 fffff880`09bf3260 fffff800`0331a026 : fffffa80`0a1ff402 fffffa80`0a1ff410 00000000`00000000 fffff980`10938c10 : nt!ExDeferredFreePool+0xf13 fffff880`09bf3310 fffff800`0331a5ec : fffff800`0317564d fffff980`10938c10 fffff800`03174f90 fffff880`09bf3710 : nt!VfIoFreeIrp+0xe6 fffff880`09bf3340 fffff800`0317564d : 00000000`00000045 fffff800`03174f90 00000000`00000000 fffff980`10938c10 : nt!IovFreeIrpPrivate+0x5c fffff880`09bf3380 fffff800`0316bba4 : fffffa80`08aed940 00000000`00000000 fffffa80`09ebb760 fffff800`02e82a01 : nt!IopParseDevice+0x6bd fffff880`09bf3510 fffff800`03170b7d : fffffa80`09ebb760 fffff880`09bf3670 00000000`00000040 fffffa80`06d4cf30 : nt!ObpLookupObjectName+0x585 fffff880`09bf3610 fffff800`0315602a : fffff880`09bf37d0 00000000`000aeb50 00000000`00000001 fffff800`02f1d859 : nt!ObOpenObjectByName+0x1cd fffff880`09bf36c0 fffff800`02e74813 : fffffa80`0a74ab60 fffffa80`07a00000 fffffa80`0a74ab60 fffffa80`0a74ab60 : nt!NtQueryAttributesFile+0x149 fffff880`09bf3960 00000000`7723fa8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000aeab8 fffff800`02e6cf00 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7723fa8a fffff880`09bf3d70 00000000`00000000 : 00000000`00000000 00000000`000000c0 fffff800`02f6b6fb fffff8a0`02ebc000 : nt!KiCallUserMode STACK_COMMAND: kb FOLLOWUP_IP: nt!MiCheckSpecialPoolSlop+83 fffff800`02f053a3 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiCheckSpecialPoolSlop+83 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xC1_32_nt!MiCheckSpecialPoolSlop+83 BUCKET_ID: X64_0xC1_32_nt!MiCheckSpecialPoolSlop+83 Followup: MachineOwner ---------
- Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Kapinoida\Windows_NT6_BSOD_jcgriff2\011612-17487-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\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 Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`03042e70 Debug session time: Mon Jan 16 17:35:24.256 2012 (UTC - 7:00) System Uptime: 0 days 0:00:25.988 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80002faa0f3, fffff88003371788, fffff88003370ff0} Probably caused by : rdyboost.sys ( rdyboost!SmFpFree+d4 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002faa0f3, The address that the exception occurred at Arg3: fffff88003371788, Exception Record Address Arg4: fffff88003370ff0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExFreePoolWithTag+43 fffff800`02faa0f3 418b45f0 mov eax,dword ptr [r13-10h] EXCEPTION_RECORD: fffff88003371788 -- (.exr 0xfffff88003371788) ExceptionAddress: fffff80002faa0f3 (nt!ExFreePoolWithTag+0x0000000000000043) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88003370ff0 -- (.cxr 0xfffff88003370ff0) rax=0000000000000000 rbx=fffffa8008c0df00 rcx=fffff6fb7dbed000 rdx=0000ef0600004bbe rsi=0000000000000000 rdi=fffff8800ef43000 rip=fffff80002faa0f3 rsp=fffff880033719c0 rbp=fffffa80093fb390 r8=0000000000004bbe r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000002 r13=0000ef0600004bbe r14=fffffa8009b550d0 r15=fffff88003371bc8 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!ExFreePoolWithTag+0x43: fffff800`02faa0f3 418b45f0 mov eax,dword ptr [r13-10h] ds:002b:0000ef06`00004bae=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ad0e0 ffffffffffffffff FOLLOWUP_IP: rdyboost!SmFpFree+d4 fffff880`0101aff0 488b5c2440 mov rbx,qword ptr [rsp+40h] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff8800101aff0 to fffff80002faa0f3 STACK_TEXT: fffff880`033719c0 fffff880`0101aff0 : 00000000`00000002 fffffa80`093fb390 00000000`00000000 00000000`000006c6 : nt!ExFreePoolWithTag+0x43 fffff880`03371a70 fffff880`01010a78 : fffffa80`08c0d078 00000000`000006c6 00000000`00000000 fffffa80`09b550d0 : rdyboost!SmFpFree+0xd4 fffff880`03371ab0 fffff880`0100f9b7 : 00000000`000006c6 fffff800`00000020 fffffa80`09b550d0 fffff880`03371b80 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageRetrieve+0x2e8 fffff880`03371b50 fffff880`0100f5fc : 00000000`0000000a 00000000`00000008 fffffa80`09b550d0 fffffa80`08c0d010 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageRetrieve+0x153 fffff880`03371c80 fffff880`0100e3fe : fffffa80`09b550d0 00000000`00000080 00000000`00000080 fffffa80`08c0dee8 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x224 fffff880`03371ce0 fffff800`031156fa : 00000000`00000000 fffff880`00000000 fffffa80`08addb60 fffffa80`06d43ae0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152 fffff880`03371d40 fffff800`02e53b46 : fffff880`02f64180 fffffa80`08addb60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03371d80 00000000`00000000 : fffff880`03372000 fffff880`0336c000 fffff880`03371820 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: rdyboost!SmFpFree+d4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: rdyboost IMAGE_NAME: rdyboost.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc48a STACK_COMMAND: .cxr 0xfffff88003370ff0 ; kb FAILURE_BUCKET_ID: X64_0x7E_rdyboost!SmFpFree+d4 BUCKET_ID: X64_0x7E_rdyboost!SmFpFree+d4 Followup: MachineOwner ---------
Well I'm gettimg some pretty bad errors and freezes, windows isn't letting it load, can only get on safe mode. Gonna run the memtest again. Is it possible that its the memory or could it possibly be a bad motherboard.
Edit- looks like I'm getting errors in memtest, 133 of them so far, yippee hehe.
Last edited by Kapinoida; 16 Jan 2012 at 21:27. Reason: update
The Memtest86+ tutorial contains information about what to do when you get errors. The steps will test both your modules and the slots the modules are seated in to determine if it is a bad module or bad modules or a bad motherboard slot or bad slots.
Quote