Alright, after I updated my bios I tried to launch Mass Effect 2 so that I could see if that had solved the issue and when I got to the main menu it Blue Screened again except when it restarted I got the following message:
Checking file system on C:
The type of file system is NTFS
One of your disks needs to be checked for consistency
What does that mean? Does this help anyone figure out what is wrong with my computer?
Sounds like there are corrupted files in your OS, even though a BSOD should not hard crash your system it's possible it has hard crashed. You stated you reinstalled Windows 7 and got a BSOD you might try doing a Repair of Windows 7, boot from the DVD and choose Repair.
Do a chkdsk/r on the harddrive sound like the NTFS file system is corrupted.
If that doesn't correct then do a harddisk diagnostic from the manufacturers website.
No diagnostic is 100% foolproof. As a last resort swap the hard drive with a known good hard drive.
A stop 0x124 usually means a hardware problem. The dilemma is to determine which piece of hardware.
If it is happening during a game then usually the graphics card is suspect.
Upload any new minidumps in case anything has changed in the dump.
I am attaching the last minidump that was created. It is not the one from after updating the bios, for some reason that did not create a minidump.
Also, I went to western digitals website to try to download some software for the hard drive to check for any issues and non of their software for my hard drive supports windows 7. Is that normal?
I also don't know how to do a chkdsk/r. Do you have a link that would show me how?
Link for WD Support > Downloads > SATA & SAS. Whateever works for vista should work for 7.
Link for Windows Vista chkdsk. Same as 7.
The dump is showing Norton as a culprit. You may want to uninstall it and use windows firewall for the time being.
Also use Microsoft Security Essentials as your anti-virus with the absence of Norton http://www.microsoft.com/security_essentials/.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Nickle\AppData\Local\Temp\Rar$DI00.399\040110-28594-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\websymbols*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.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a0c000 PsLoadedModuleList = 0xfffff800`02c49e50 Debug session time: Thu Apr 1 14:30:46.276 2010 (GMT-4) System Uptime: 0 days 0:01:24.556 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88008e9473c, fffff88006f0c560, 0} Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\VirusDefs\20090713.024\EX64.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for EX64.SYS *** ERROR: Module load completed but symbols could not be loaded for EX64.SYS Probably caused by : EX64.SYS ( EX64+3973c ) Followup: MachineOwner --------- 0: 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: fffff88008e9473c, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88006f0c560, 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: EX64+3973c fffff880`08e9473c 39581c cmp dword ptr [rax+1Ch],ebx CONTEXT: fffff88006f0c560 -- (.cxr 0xfffff88006f0c560) rax=ff00f8a001cc0660 rbx=0000000000000000 rcx=fffff8a002345f1c rdx=0000000000000000 rsi=fffff8a0023a8180 rdi=fffff88006f0d430 rip=fffff88008e9473c rsp=fffff88006f0cf40 rbp=fffff8a0023a8198 r8=fffff8a0087e7218 r9=0000000000000000 r10=fffffa8003961148 r11=0000000000000001 r12=fffff88006f0d1a0 r13=fffff8a0087e7040 r14=fffff8a002169010 r15=fffff8a002169610 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 EX64+0x3973c: fffff880`08e9473c 39581c cmp dword ptr [rax+1Ch],ebx ds:002b:ff00f8a0`01cc067c=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 005c006c006c0065 to fffff88008e9473c STACK_TEXT: fffff880`06f0cf40 005c006c`006c0065 : 006d0072`006f004e 006f0043`006c0061 00000072`006f006c fffff8a0`023a8180 : EX64+0x3973c fffff880`06f0cf48 006d0072`006f004e : 006f0043`006c0061 00000072`006f006c fffff8a0`023a8180 00790074`0073006c : 0x5c006c`006c0065 fffff880`06f0cf50 006f0043`006c0061 : 00000072`006f006c fffff8a0`023a8180 00790074`0073006c 0064002e`0065006c : 0x6d0072`006f004e fffff880`06f0cf58 00000072`006f006c : fffff8a0`023a8180 00790074`0073006c 0064002e`0065006c 00000000`006c006c : 0x6f0043`006c0061 fffff880`06f0cf60 fffff8a0`023a8180 : 00790074`0073006c 0064002e`0065006c 00000000`006c006c 00000000`00000000 : 0x72`006f006c fffff880`06f0cf68 00790074`0073006c : 0064002e`0065006c 00000000`006c006c 00000000`00000000 fffff6fc`50044f58 : 0xfffff8a0`023a8180 fffff880`06f0cf70 0064002e`0065006c : 00000000`006c006c 00000000`00000000 fffff6fc`50044f58 fffff800`02c08b40 : 0x790074`0073006c fffff880`06f0cf78 00000000`006c006c : 00000000`00000000 fffff6fc`50044f58 fffff800`02c08b40 fffffa80`02375820 : 0x64002e`0065006c fffff880`06f0cf80 00000000`00000000 : fffff6fc`50044f58 fffff800`02c08b40 fffffa80`02375820 fffffa80`0221fa30 : 0x6c006c FOLLOWUP_IP: EX64+3973c fffff880`08e9473c 39581c cmp dword ptr [rax+1Ch],ebx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: EX64+3973c FOLLOWUP_NAME: MachineOwner MODULE_NAME: EX64 IMAGE_NAME: EX64.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4994b41b STACK_COMMAND: .cxr 0xfffff88006f0c560 ; kb FAILURE_BUCKET_ID: X64_0x3B_EX64+3973c BUCKET_ID: X64_0x3B_EX64+3973c Followup: MachineOwner ---------
Ok, I ran the Chkdsk and everything came out fine. I also downloaded and tried running the Data Lifeguard Diagnostic for Windows but my hard drive was only showing up in the logical spot and not the physical spot that it need too for me to run the test.
After that, however, everything hit the fan and I got 2 blue screens and now when I try to turn on my computer it boots fine but nothing comes up on my monitor.
Does this point to Video Card, RAM, Motherboard, or something else.
Also, a couple of times when I was on my computer it would freeze for a couple of seconds and then "Display Driver AMD stopped working" would pop up but then everything would go back to normal after that.
You need to be running the Data Lifeguard for DOS from a bootable cd/dvd. Download the iso version and burn it to cd/dvd using ImgBurn or any other cd burning software of choice. It runs from DOS and is independent of Windows. If the hard drive is bad then trying to run from Windows will not work.
Be sure to upload the minidumps for any new bsods.
Disable the video card and use the onboard video to see if it is indeed the video card causing the problem.
Edit: I have only partially read this thread. It would be a good idea to update all your drivers. Here is the link to the ASUS support site for your motherboard http://support.asus.com/download/dow...Language=en-us. Make sure all graphics, chipset, audio, lan drivers are updated. For equipment that you have added, go to the manufacturers website of that equipment for driver updates.
Last edited by nickle; 08 Apr 2010 at 08:07.
It didn't create the minidumps for the last 2 blue screens for some reason. Is there any other place to check for them besides the minidump folder, or is there something I maybe need to turn on?
How to get and read Minidumps
Article was written for XP but applies to Win 7.
Easiest way to configure minidumps is to type advanced system settings in the search area of start menu and then select it up top. Click startup and recovery settings. Untick automatically restart and select small memory dump. Dump directory should be %SystemRoot%\Minidump.
BTW did you uninstall Norton for the time being at least? It caused the last dump you posted. See post #15.
Thanks a lot nickle, and yes I did uninstall Norton. I installed the Microsoft Security Essentials that you recommended.
Quote