Windows 7: BSOD CCode A

Furman · 05 Mar 2011

- Windows 7 x64
- the original installed OS on the system? I installed it.
- an OEM or full retail version? RTM

- What is the age of system (hardware)? 2 years or less
- What is the age of OS installation? This install is only couple months old.

Performance monitor
performance monitor.html

zip file
Windows_NT6_BSOD_jcgriff2.zip

Also I'll note that sometimes (not all the time) when I plug into the front USB port it seems it shorts out and goes into a infinite reboot and for the life of me I can't figure out why it does that. I think it's the motherboard because I've changed cases 2 times now and it still does it. So it could be the USB front port on the motherboard causing issues. Either way I'm tired of this motherboard and going with Asus... one right now is a Gigabyte MA-790FXT-UD5P I believe.

usasma · 06 Mar 2011

You have 1 Windows Update installed.
Without SP1 there are over 60 updates for most systems.
Please visit Windows Update and get all available updates.
Then reboot and go back to Windows Update. Select the Important Updates and get SP1

MSINFO32 shows BSOD's with your ATI video drivers. Please do the following:
- download the Display Drivers ONLY from the ATI website: ATI Radeon
- uninstall all ATI software (to include the Catalyst Control Center) from your system
- install the freshly downloaded drivers and monitor for further BSOD's
If this doesn't fix the BSOD's then we'll have to look at the video card for issues.

The sptd.sys driver in Daemon Tools is known to cause BSOD's
Please uninstall Daemon Tools, then use this free tool to remove the troublesome sptd.sys driver: DuplexSecure - FAQ - Remove 64 bit sptd.sys

Some Internet Security/Security Center apps have BSOD issues that aren't easily discovered. I'd suggest the following:

Quote:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the McAfee from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of McAfee using this free tool: How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Quote:

Code:


arcsas.sys      Mon Nov 22 22:22:06 2010 (4CEB335E)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
mfehidk.sys     Wed Oct 06 15:55:49 2010 (4CACD445)
PxHlpa64.sys    Tue Jun 23 19:16:35 2009 (4A416253)
xusb21.sys      Thu Aug 13 18:10:17 2009 (4A848F49)
speedfan.sys    Sat Dec 18 06:03:51 2010 (4D0C9517)
mfewfpk.sys     Wed Oct 06 15:56:04 2010 (4CACD454)
mfenlfk.sys     Wed Oct 06 15:56:13 2010 (4CACD45D)
Rt64win7.sys    Thu Nov 11 01:35:36 2010 (4CDB8EB8)
AtihdW76.sys    Wed Nov 17 07:02:04 2010 (4CE3C43C)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
Lachesis.sys    Fri Oct 16 09:09:12 2009 (4AD87078)
RTKVHD64.sys    Fri Sep 03 04:02:27 2010 (4C80AB93)
mfeavfk.sys     Wed Oct 06 15:56:49 2010 (4CACD481)
mfefirek.sys    Wed Oct 06 15:59:47 2010 (4CACD533)
dump_arcsas.sys Mon Nov 22 22:22:06 2010 (4CEB335E)
nx6000.sys      Thu Dec 02 17:23:39 2010 (4CF81C6B)
cfwids.sys      Wed Oct 06 16:00:36 2010 (4CACD564)
mfeapfk.sys     Wed Oct 06 15:56:26 2010 (4CACD46A)
umpass.sys      Mon Jul 13 20:06:52 2009 (4A5BCC1C)
atikmdag.sys    Wed Jan 26 17:48:28 2011 (4D40A4BC)
TotRec8.sys     Tue Nov 23 05:17:10 2010 (4CEB94A6)
atikmpag.sys    Thu Nov 25 21:16:47 2010 (4CEF188F)
atikmdag.sys    Thu Nov 25 21:46:44 2010 (4CEF1F94)
AtihdW76.sys    Fri Sep 24 01:44:48 2010 (4C9C3AD0)
arcsas.sys      Wed Jan 14 14:27:37 2009 (496E3CA9)
dump_arcsas.sys Wed Jan 14 14:27:37 2009 (496E3CA9)
mfeapfk01.sys   Wed Oct 06 15:56:26 2010 (4CACD46A)

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar  5 06:09:47.053 2011 (UTC - 5:00)
System Uptime: 0 days 11:29:27.692
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  ffmpeg.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+100
Bugcheck code 0000000A
Arguments fffffa80`0cec44f0 00000000`00000002 00000000`00000001 fffff800`032f935f
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar  4 03:31:26.390 2011 (UTC - 5:00)
System Uptime: 0 days 3:50:23.013
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  mcshield.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+1ca
Bugcheck code 0000000A
Arguments fffffa80`125e4d08 00000000`00000002 00000000`00000001 fffff800`032ecb74
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Feb 27 07:33:08.597 2011 (UTC - 5:00)
System Uptime: 0 days 5:58:49.235
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  sidebar.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+1ca
Bugcheck code 0000000A
Arguments fffffa80`0f20cd08 00000000`00000002 00000000`00000001 fffff800`03293b74
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 28 09:08:44.982 2011 (UTC - 5:00)
System Uptime: 5 days 21:59:44.254
Probably caused by : atikmdag.sys ( atikmdag+90817 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`04952817 fffff880`08baa8e0 00000000`00000000
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 22 07:58:42.764 2011 (UTC - 5:00)
System Uptime: 3 days 10:30:33.403
Probably caused by : atikmdag.sys ( atikmdag+90817 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0491f817 fffff880`0893b8e0 00000000`00000000
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 11 10:29:32.183 2011 (UTC - 5:00)
System Uptime: 0 days 22:51:51.822
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+2a2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+2a2
Bugcheck code 0000000A
Arguments fffffa80`0d93e4e8 00000000`00000002 00000000`00000001 fffff800`02efc4f8
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan  9 00:39:56.026 2011 (UTC - 5:00)
System Uptime: 0 days 11:00:11.665
Probably caused by : atikmdag.sys ( atikmdag+90817 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`04890817 fffff880`0a26b8e0 00000000`00000000
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Furman · 06 Mar 2011

Well I updated my Windows 7 and the BSOD's are happening more often now. Just now I've had 2 in a row within say 5 to 10 minutes of logging on. I'm going to try and uninstall drivers and just do an install of the drivers by themselves. I hope my card isn't messed up and don't have to RMA it. I'm looking at updating my motherboard as I think it's the one thing that's messed up.

Actually I was looking at the dump files you have posted there and the last two which are March related are not even directly related to ATI. I mean the ffmpeg.exe could be but idk why that would cause issues. It seems I'm having memory errors or is that a wrong thought?

usasma · 07 Mar 2011

The majority of BSOD errors are related to 3rd party drivers.
The majority of BSOD errors are a result of improper memory operations
If program A does an improper memory operation in the memory space owned by program B, and then it exits - There won't be any evidence of program A when program B gets around to accessing (and crashing) that bad memory space.
The process name generally isn't significant when analyzing BSOD's. Then only time that I consider it is when there's a long string of BSOD's and all of them mention the same process name.

Please post back with the rest of the memory dumps that have happened. That'll give us more info to (hopefully) establish a pattern.

Have you uninstall Daemon Tools? Have you run the sptd.sys removal tool?
Have you updated your ATI video drivers?
Have you tried another antivirus (after removing the McAfee)?

Furman · 07 Mar 2011

Here is the new dumpfile I just had.
030711-65926-01.zip

Let me know what it says. I'm betting it's ATI related. I uninstalled the catalyst software and just left the driver but I'm going to uninstall the driver too and reinstall just it.

I don't know if it's McAfee because I've always used it with no issues even before this card. And I love it haha. Don't want to move to something else haha.

usasma · 07 Mar 2011

It won't cause any harm to remove the ATI stuff and then install the drivers only (I often recommend that in BSOD scenarios with ATI cards).

I experience problems with McAfee/Norton on a regular basis at work. Unfortunately the programs are so complicated that it's often impossible to tell what the cause is unless you uninstall it. If you like the McAfee - feel free to reinstall it after we're finished testing.

FWIW - you've lost the bet. This one points to McAfee as the cause. Stack text is read from the bottom up. I stripped out the memory references to make it easier to read.

Quote:

STACK_TEXT:
nt!KeBugCheckEx
nt!KiBugCheckDispatch+0x69
nt!KiPageFault+0x260
nt!ExDeferredFreePool+0x100
nt!ExFreePoolWithTag+0x411
mfefirek+0x23681
0xfffffa80`076d8d90
0xfffffa80`076d8d90
0xfffffa80`4365666d
0xfffffa80`0cd74010
0xfffffa80`0a820000
mfefirek+0xb22c
0xfffffa80`0a820000
0xfffffa80`076d8d90
0xfffffa80`0a820000
0xfffffa80`0cd74010
afd!AfdSetInLineMode+0x16f
0xfffff800`00b96080

Uninstall the McAfee:

Quote:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the McAfee from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of McAfee using this free tool: How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Feel free to install a fresh copy once we're finished troublshooting.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Mar  7 17:53:12.328 2011 (UTC - 5:00)
System Uptime: 0 days 20:10:26.967
*** WARNING: Unable to verify timestamp for mfefirek.sys
*** ERROR: Module load completed but symbols could not be loaded for mfefirek.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xC5_2_nt!ExDeferredFreePool+100
Bugcheck code 000000C5
Arguments 00000000`00000001 00000000`00000002 00000000`00000000 fffff800`03409f8c
BiosVersion = F7
BiosReleaseDate = 09/16/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA790FXT-UD5P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Furman · 07 Mar 2011

Wow really? Fricking McAfee is causing this? Gah. Well I'll uninstall and see if that helps then find another anti-virus. You got any recommendations?

usasma · 07 Mar 2011

Try Microsoft Security Essentials (it's on the list in the link above).

Furman · 12 Mar 2011

Ok here's another one. Check to see if it's my anti-virus

031211-60325-01.zip

usasma · 13 Mar 2011

This one points to the file system on your hard drive - a very generic error, but there's a lot that we can to with it.
But first -
- McAfee is still installed and can cause this error
- Razer drivers are still from 2009 - and they can cause this error
- have you updated to Service Pack 1? It's not shown in the memory dump

First:

Quote:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Copy/paste the results into your next post.

Then this:

Quote:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

Quote:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Quote:

Code:


arcsas.sys      Mon Nov 22 22:22:06 2010 (4CEB335E)
mfehidk.sys     Wed Oct 06 15:55:49 2010 (4CACD445)
PxHlpa64.sys    Tue Jun 23 19:16:35 2009 (4A416253)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
mfewfpk.sys     Wed Oct 06 15:56:04 2010 (4CACD454)
speedfan.sys    Sat Dec 18 06:03:51 2010 (4D0C9517)
mfenlfk.sys     Wed Oct 06 15:56:13 2010 (4CACD45D)
atikmpag.sys    Wed Jan 26 17:13:33 2011 (4D409C8D)
Rt64win7.sys    Thu Nov 11 01:35:36 2010 (4CDB8EB8)
AtihdW76.sys    Fri Sep 24 01:44:48 2010 (4C9C3AD0)
mfeapfk.sys     Wed Oct 06 15:56:26 2010 (4CACD46A)
cfwids.sys      Wed Oct 06 16:00:36 2010 (4CACD564)
nx6000.sys      Thu Dec 02 17:23:39 2010 (4CF81C6B)
Lachesis.sys    Fri Oct 16 09:09:12 2009 (4AD87078)
RTKVHD64.sys    Fri Sep 03 04:02:27 2010 (4C80AB93)
mfeavfk.sys     Wed Oct 06 15:56:49 2010 (4CACD481)
mfefirek.sys    Wed Oct 06 15:59:47 2010 (4CACD533)
dump_arcsas.sys Mon Nov 22 22:22:06 2010 (4CEB335E)
mferkdet.sys    Wed Oct 06 15:57:05 2010 (4CACD491)

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 12 03:57:53.020 2011 (UTC - 4:00)
System Uptime: 0 days 5:59:45.659
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+179 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFcb+179
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0318c688 fffff880`0318bef0 fffff800`032ed61b
BiosVersion = F7
BiosReleaseDate = 09/16/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Windows 7: BSOD CCode A

BSOD CCode A problems?