I've been doing what you said so far. As of now, I haven't had the BSOD
As for the RAM. I bought the ram all together as one type. Three 2 gig Sticks all placed in a row on the board. Hopefully, its not the RAM.
Thank you again for the help you provided. I didn't really expect to get this much help on any forum. As stated before, much appreciated.
As soon as I posted that, I crashed with BSOD once again. I don't expect you to continue to help me with every single step but here is my recent crash dump files (2 so far) for anybody who may help me. Thanks again.
Try a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.
BSOD BUGCHECK SUMMARYAlso, delete the dmps in your minidump folder, and turn on Verifier again. Please upload any new dmps.Code:Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed May 12 11:58:23.967 2010 (GMT-4) System Uptime: 0 days 0:31:45.777 BugCheck 4E, {99, 771d1, 3, 10a0a7} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) BUGCHECK_STR: 0x4E_99 PROCESS_NAME: Wow.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Wed May 12 12:18:21.794 2010 (GMT-4) System Uptime: 0 days 0:19:22.604 BugCheck 24, {1904fb, fffff880096fc718, fffff880096fbf80, fffff880012c615b} Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+736 ) PROCESS_NAME: MsMpEng.exe BUGCHECK_STR: 0x24 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ
After running Memtest86 with 5 Passes, with no errors reported, and running driver verifier, BSOD happened with a certain driver. This is the most recent minidump from the driver verifier. So it must be a driver issue, not a memory.
Thanks for all the help so far. It is appreciated.
I'll post anymore dumps I get when and if I crash again. If anybody can help pinpoint which driver it is, I think thats the real culprit here.
Go here and search for your motherboard model: ASUSTeK Computer Inc.-Support-
Select your OS, and download the ASUS AI Suite, found in the utilities section.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_Recent Crash After Driver Verifier.zip\Recent Crash After Driver Verifier\051210-20280-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 Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a12000 PsLoadedModuleList = 0xfffff800`02c4fe50 Debug session time: Wed May 12 23:06:47.963 2010 (GMT-4) System Uptime: 0 days 0:00:32.789 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {f6, e0, fffffa80085eab30, fffff8800482a257} Unable to load image ASACPI.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ASACPI.sys *** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys Probably caused by : ASACPI.sys ( ASACPI+1257 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00000000000000f6, Referencing user handle as KernelMode. Arg2: 00000000000000e0, Handle value being referenced. Arg3: fffffa80085eab30, Address of the current process. Arg4: fffff8800482a257, Address inside the driver that is performing the incorrect reference. Debugging Details: ------------------ BUGCHECK_STR: 0xc4_f6 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: FourEngine.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002f0c3dc to fffff80002a82600 STACK_TEXT: fffff880`077c4648 fffff800`02f0c3dc : 00000000`000000c4 00000000`000000f6 00000000`000000e0 fffffa80`085eab30 : nt!KeBugCheckEx fffff880`077c4650 fffff800`02f21ae4 : 00000000`000000e0 fffffa80`085eab30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`077c4690 fffff800`02cde580 : 00000000`00000000 fffff880`077c48c0 00000000`00000000 fffffa80`07421100 : nt!VfCheckUserHandle+0x1b4 fffff880`077c4770 fffff800`02d5a425 : 00000000`00000000 00000000`000f0001 00000000`00000000 fffff800`02d5a400 : nt! ?? ::NNGAKEGL::`string'+0x20e1e fffff880`077c4840 fffff800`02f21878 : 00000000`00060001 fffff800`02c0f440 00000000`00000000 00000000`00000110 : nt!ObReferenceObjectByHandle+0x25 fffff880`077c4890 fffff880`0482a257 : fffffa80`08436a60 00000000`00000002 fffffa80`074211b0 fffff800`02bfce80 : nt!VerifierObReferenceObjectByHandle+0x48 fffff880`077c48e0 fffffa80`08436a60 : 00000000`00000002 fffffa80`074211b0 fffff800`02bfce80 fffffa80`074211d8 : ASACPI+0x1257 fffff880`077c48e8 00000000`00000002 : fffffa80`074211b0 fffff800`02bfce80 fffffa80`074211d8 00000000`00000000 : 0xfffffa80`08436a60 fffff880`077c48f0 fffffa80`074211b0 : fffff800`02bfce80 fffffa80`074211d8 00000000`00000000 00000000`00000001 : 0x2 fffff880`077c48f8 fffff800`02bfce80 : fffffa80`074211d8 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`074211b0 fffff880`077c4900 fffffa80`074211d8 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`08436a60 : nt!KiInitialPCR+0x180 fffff880`077c4908 00000000`00000000 : 00000000`00000001 00000000`00000000 fffffa80`08436a60 fffffa80`07421060 : 0xfffffa80`074211d8 STACK_COMMAND: kb FOLLOWUP_IP: ASACPI+1257 fffff880`0482a257 83462001 add dword ptr [rsi+20h],1 SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: ASACPI+1257 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ASACPI IMAGE_NAME: ASACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a0b72fd FAILURE_BUCKET_ID: X64_0xc4_f6_ASACPI+1257 BUCKET_ID: X64_0xc4_f6_ASACPI+1257 Followup: MachineOwner ---------
So after I downloaded the Asus AI Suite, my PC BSOD before I could even install it. Now, When I turn on my PC to re-boot, I get "Reboot and Select proper Boot Device or Insert Boot Media in selected Boot device and press a key"
This seriously raised an alarm because when it BSOD'd, it sated "Memory_Management" . Though I checked my BIOS settings, and I have my hard drive as my boot device, I repeatability get this message. Just a day before, I ran a full hard drive error scan and nothing came up.
I could really use some help with this issue seeing how I can't even use my PC anymore. (posting from my laptop)
Once again to all of you that have helped me, I am sincerely greatfull for your assistance to this point and if anyone can help me resolve this issue, I'll do my best to get out of your guy's hair
Well Im running memtest86 (previously ran this test before) right now since I dont have anymore blank CD's. Ill post results as soon as I get them.
No errors were found during the memory test. I put in the Windows 7 OS disc and tried doing a repair. I saw an error saying its a corrupt partition. Im currently trying to recover/fix this but any guidance would be a great help.
Last edited by Bonto; 13 May 2010 at 23:46.
Quote