Help with BSOD on brand new computer...

[dahoover]

Hello all,
I just got my 4th BSOD in the last 3 days. The first 3 came while I was playing Mass Effect 2 and the last one came while I was browsing the internet and listening to music via Itunes.

I bought the computer parts 2 weeks ago and me and my friend assembled it. It ran fine for the first 1.5 weeks but now I am getting the BSOD and it really worries me.

I am attaching the last 3 minidumps and any help deciphering them would be greatly appreciated because I have never dealt with the BSOD before.

 

[zigzag3143]

Hello all,
I just got my 4th BSOD in the last 3 days. The first 3 came while I was playing Mass Effect 2 and the last one came while I was browsing the internet and listening to music via Itunes.

I bought the computer parts 2 weeks ago and me and my friend assembled it. It ran fine for the first 1.5 weeks but now I am getting the BSOD and it really worries me.

I am attaching the last 3 minidumps and any help deciphering them would be greatly appreciated because I have never dealt with the BSOD before.

These crashes were caused by hardware. use these instructions to find and fix. http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

let us know if we can help

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\032510-19640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Thu Mar 25 14:08:55.069 2010 (GMT-4)
System Uptime: 0 days 0:00:07.364
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004e1d8f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004e1d8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fbd6f0 fffff800`02cc1a89 : fffffa80`04e1d8d0 fffffa80`03a00680 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fbdc10 fffff800`02ba3547 : fffffa80`04e1d8d0 fffff800`02c1c5f8 fffffa80`03a00680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fbdc40 fffff800`02b0bb95 : fffff800`02c7e360 fffffa80`04929d18 fffffa80`04929d10 fffffa80`03a00680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fbdc80 fffff800`02a86161 : fffff880`00c30e00 fffff800`02b0bb70 fffffa80`03a00680 00000554`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fbdcb0 fffff800`02d1c166 : 00000554`00000000 fffffa80`03a00680 00000000`00000080 fffffa80`0396e990 : nt!ExpWorkerThread+0x111
fffff880`02fbdd40 fffff800`02a57486 : fffff880`02d63180 fffffa80`03a00680 fffff880`02d6dfc0 00000554`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fbdd80 00000000`00000000 : fffff880`02fbe000 fffff880`02fb8000 fffff880`035c4540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

 

[Capt.Jack Sparrow]

Hello all,
I just got my 4th BSOD in the last 3 days. The first 3 came while I was playing Mass Effect 2 and the last one came while I was browsing the internet and listening to music via Itunes.

I bought the computer parts 2 weeks ago and me and my friend assembled it. It ran fine for the first 1.5 weeks but now I am getting the BSOD and it really worries me.

I am attaching the last 3 minidumps and any help deciphering them would be greatly appreciated because I have never dealt with the BSOD before.

Hello Dahoover Welcome to SF,

I guess there are multiple issues going on. I would recommend to start with basics. If your Overclocking please stop. Make sure your BIOS have the latest firmware. If you using any Antivirus or Firewall uninstall it and see whether that makes any difference.

http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Hardware Diagnostic

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

Update the following Driver

 asusgsb.sys  Thu Sep 27 18:44:50 2007

Bugcheck Code

[B][FONT=Tahoma][COLOR=red]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR][/FONT][/B]
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004e1d8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`02fbd6f0 fffff800`02cc1a89 : fffffa80`04e1d8d0 fffffa80`03a00680 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fbdc10 fffff800`02ba3547 : fffffa80`04e1d8d0 fffff800`02c1c5f8 fffffa80`03a00680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fbdc40 fffff800`02b0bb95 : fffff800`02c7e360 fffffa80`04929d18 fffffa80`04929d10 fffffa80`03a00680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fbdc80 fffff800`02a86161 : fffff880`00c30e00 fffff800`02b0bb70 fffffa80`03a00680 00000554`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fbdcb0 fffff800`02d1c166 : 00000554`00000000 fffffa80`03a00680 00000000`00000080 fffffa80`0396e990 : nt!ExpWorkerThread+0x111
fffff880`02fbdd40 fffff800`02a57486 : fffff880`02d63180 fffffa80`03a00680 fffff880`02d6dfc0 00000554`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fbdd80 00000000`00000000 : fffff880`02fbe000 fffff880`02fb8000 fffff880`035c4540 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [B][FONT=Tahoma][COLOR=red]hardware[/COLOR][/FONT][/B]
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
 
[B][FONT=Tahoma][COLOR=red]SYSTEM_SERVICE_EXCEPTION (3b)[/COLOR][/FONT][/B]
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960001b44d3, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008ef5a30, 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: 
win32k!DEVLOCKOBJ::vDestructor+4f
fffff960`001b44d3 4c8b80f8090000  mov     r8,qword ptr [rax+9F8h]
CONTEXT:  fffff88008ef5a30 -- (.cxr 0xfffff88008ef5a30)
rax=0000000000000000 rbx=fffff88008ef65a8 rcx=fffff88008ef65a8
rdx=00ff000000000000 rsi=fffff900c2f58630 rdi=fffff900c00bf010
rip=fffff960001b44d3 rsp=fffff88008ef6410 rbp=fffff900c0155be0
 r8=fffff900c215dbe0  r9=0000000000000000 r10=fffffa8005a28f80
r11=fffff900c4c35be0 r12=0000000000000305 r13=0000000000000000
r14=fffff900c2a73cd0 r15=0000000000000305
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
win32k!DEVLOCKOBJ::vDestructor+0x4f:
fffff960`001b44d3 4c8b80f8090000  mov     r8,qword ptr [rax+9F8h] ds:002b:00000000`000009f8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  [FONT=Tahoma][B][COLOR=red]chrome.exe[/COLOR][/B][/FONT]
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001b44d3
STACK_TEXT:  
fffff880`08ef6410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DEVLOCKOBJ::vDestructor+0x4f
FOLLOWUP_IP: 
win32k!DEVLOCKOBJ::vDestructor+4f
fffff960`001b44d3 4c8b80f8090000  mov     r8,qword ptr [rax+9F8h]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  win32k!DEVLOCKOBJ::vDestructor+4f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: win32k
IMAGE_NAME:  win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0
STACK_COMMAND:  .cxr 0xfffff88008ef5a30 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_win32k!DEVLOCKOBJ::vDestructor+4f
BUCKET_ID:  X64_0x3B_win32k!DEVLOCKOBJ::vDestructor+4f
 
[FONT=Tahoma][COLOR=red][B]SYSTEM_SERVICE_EXCEPTION (3b)[/B][/COLOR][/FONT]
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002b87834, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007403eb0, 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: 
nt!PfFbLogEntryComplete+24
fffff800`02b87834 48634350        movsxd  rax,dword ptr [rbx+50h]
CONTEXT:  fffff88007403eb0 -- (.cxr 0xfffff88007403eb0)
rax=0000000000000030 rbx=ff43f80002c5c5e0 rcx=fffff8a0000a6020
rdx=0000000000003f80 rsi=fffff8a0000a6060 rdi=fffff8a0000a6060
rip=fffff80002b87834 rsp=fffff88007404890 rbp=0000000008000000
 r8=0000000000000030  r9=fffff8a0000a6020 r10=fffff80002c5c5f0
r11=fffff8a0000a6020 r12=0000000000000030 r13=fffff8a009b91de8
r14=fffff8a009b91da8 r15=fffffa8006afa560
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!PfFbLogEntryComplete+0x24:
fffff800`02b87834 48634350        movsxd  rax,dword ptr [rbx+50h] ds:002b:ff43f800`02c5c630=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  [B][FONT=Tahoma][COLOR=red]MassEffect2.exe[/COLOR][/FONT][/B]
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002b87834
STACK_TEXT:  
fffff880`07404890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`0000000000000000`00000000 : nt!PfFbLogEntryComplete+0x24
FOLLOWUP_IP: 
nt!PfFbLogEntryComplete+24
fffff800`02b87834 48634350        movsxd  rax,dword ptr [rbx+50h]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!PfFbLogEntryComplete+24
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
STACK_COMMAND:  .cxr 0xfffff88007403eb0 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_nt!PfFbLogEntryComplete+24
BUCKET_ID:  X64_0x3B_nt!PfFbLogEntryComplete+24

Hope this helps,
Captain

 

[dahoover]

Alright, thanks guys! I will try those things and see if they work.

 

[dahoover]

Ok guys, I tried almost everything that you mentioned and am still getting the BSOD.

I ran the Memory Diagnostic and System Integrity Checker and everything was fine. I also unistalled AVG and turned off Windows Firewall and I continued getting Blue Screens. The last thing I did was perform a clean install of Windows 7 and still got the BSOD.

I am beginning to panic because I invested so much money into this computer. I am attaching the last few minidumps for analysis. Please help me try to solve this problem and alleviate my stress.

 

[dahoover]

Is there anyone that can help?

 

[stormy13]

dahoover a couple of things for you to try. First grab this,

CPUID

and double cheek the specs for your ram and make sure it is running at the correct latencies and voltage. Compare the timings from the Memory tab to what it says on the SPD tab. If any of them are lower on the memory tab than the SPD tab, then it will require going into the bios and setting those values manually instead of the default Auto setting. Also for the voltage use the manufacturer's spec for it and set it to that value (and maybe on notch higher) in the bios as well.

If that doesn't sort it back in the bios look for the following settings under "JumperFree Configuration" (will require setting CPU Overclocking to Manual from Auto),

HT Over Voltage
Chipset Over Voltage

for the first one start with raising it one above default (1.25000V) and test to see if that fixes it. If not raise it up another and test, repeating till it gets to the max (1.38500V).

If that doesn't fix it for the second one start it at about 1.3V, the minimum setting of 1.1V is for when Cool and Quiet is enabled and the bios will lower it that as needed (and too low for a manual setting). Again test to see if that sorts it or not, and if not raise it 0.1V and test.

Hopefully one of those or a combination of the two will stop the crashes from happening. I was getting the same stop 124 errors on mine (and the same way, could be gaming or doing nothing; no rhyme or reason to it at all), and it took raising those and a couple of more (mine has a few more settings than yours does) to get mine to run stable. Been running with the raised settings for close to a month now and not seen a single stop 124, to the point that I can now run a program (Prime 95) that would cause it to happen almost instantly (one of the few that I could count on triggering it) to running it for hours at a time.

 

[nickle]

Since this is a new build make sure all chipset,network,graphics,etc. drivers and bios is current.

Your bios should be this one:
Description M4A785T-M BIOS 2002
Support new CPUs. Please refer to our website at: http://support.asus.com/cpusupport/cpusupport.aspx

File Size 759.68 (KBytes) 2010/03/30 update

Download from

Global (DLM)

Global

Do memory diagnostic for at least 3 passes:http://www.memtest.org/

Do harddrive diagnostic from manufacturer.

 

[dahoover]

dahoover a couple of things for you to try. First grab this,

CPUID

and double cheek the specs for your ram and make sure it is running at the correct latencies and voltage. Compare the timings from the Memory tab to what it says on the SPD tab. If any of them are lower on the memory tab than the SPD tab, then it will require going into the bios and setting those values manually instead of the default Auto setting. Also for the voltage use the manufacturer's spec for it and set it to that value (and maybe on notch higher) in the bios as well.

If that doesn't sort it back in the bios look for the following settings under "JumperFree Configuration" (will require setting CPU Overclocking to Manual from Auto),

HT Over Voltage
Chipset Over Voltage

for the first one start with raising it one above default (1.25000V) and test to see if that fixes it. If not raise it up another and test, repeating till it gets to the max (1.38500V).

If that doesn't fix it for the second one start it at about 1.3V, the minimum setting of 1.1V is for when Cool and Quiet is enabled and the bios will lower it that as needed (and too low for a manual setting). Again test to see if that sorts it or not, and if not raise it 0.1V and test.

Hopefully one of those or a combination of the two will stop the crashes from happening. I was getting the same stop 124 errors on mine (and the same way, could be gaming or doing nothing; no rhyme or reason to it at all), and it took raising those and a couple of more (mine has a few more settings than yours does) to get mine to run stable. Been running with the raised settings for close to a month now and not seen a single stop 124, to the point that I can now run a program (Prime 95) that would cause it to happen almost instantly (one of the few that I could count on triggering it) to running it for hours at a time.

Ok I am not that technical so I am attaching the saved txt file from the cpuid report. If you could tell me if anything looks like it needs to be changed that would be great.

 

[dahoover]

Since this is a new build make sure all chipset,network,graphics,etc. drivers and bios is current.

Your bios should be this one:
Description M4A785T-M BIOS 2002
Support new CPUs. Please refer to our website at: ASUSTeK Computer Inc.-Support-

File Size 759.68 (KBytes) 2010/03/30 update

Download from

Global (DLM)

Global

Do memory diagnostic for at least 3 passes:Memtest86+ - Advanced Memory Diagnostic Tool

Do harddrive diagnostic from manufacturer.

Thanks Nickle, I updated the BIOS using the file that you linked me too. Hopefully this works!

 

[dahoover]

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?

 

[fishnbanjo]

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.

 

[nickle]

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.

 

[dahoover]

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?

 

[nickle]

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/.

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}

[COLOR=Blue]Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\VirusDefs\20090713.024\EX64.SYS, Win32 error 0n2[/COLOR]
*** WARNING: Unable to verify timestamp for EX64.SYS
*** ERROR: Module load completed but symbols could not be loaded for EX64.SYS
[COLOR=Blue]Probably caused by : EX64.SYS ( EX64+3973c )[/COLOR]

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
---------

 

[dahoover]

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/.

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.

 

[nickle]

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.

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.

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.

Be sure to upload the minidumps for any new bsods.

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.
Does this point to Video Card, RAM, Motherboard, or something else.

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/download.aspx?model=M4A785T-M&SLanguage=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.

 

[dahoover]

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?

 

[nickle]

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.

 

[dahoover]

Thanks a lot nickle, and yes I did uninstall Norton. I installed the Microsoft Security Essentials that you recommended.