Windows 7 Frequent BSODs and Flickering Screen: Help with Error Code 0x000000C4

Felipe Augusto de Godoy · Feb 8, 2014

Hi,
I got this really lengthy BSOD error code.
It all started when my computer randomly BSOD while I was playing League of Legends. Before I got my BSOD I experienced some flickering lines which randomly showed up every 10sec - 5min.
After a restart, I experienced another BSOD while I was browsing the web. After constant restarts and BSODs (about 2) the problem seemed to ease off.
ERROR CODE:
STOP: 0x000000C4

kemical · Feb 9, 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff70001607ee8, 0, fffff80002e6846e, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+ce )

Followup: MachineOwner

Hi,
not sure what happened with the bios update but try downloading the latest version (F5) save...

kemical · Feb 9, 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffffa80069ddb60, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4894 )

Followup: MachineOwner

Hi,
all your dump files had the same error and this can be caused by out of date drivers or bios:

BiosVersion = F3
BiosReleaseDate = 10/26/2012
Please update bios:
http://www.gigabyte.com/products/product-page.aspx?pid=4402#bios

The driver causing the C4 bugcheck is: RAVCpl64.exe. This is a Realtek audio driver but first your in need of a service pack. Please install SP1:
Link Removed
In case of issues try this readiness tool:
Link Removed

000.fcl Fri Sep 26 14:11:22 2008: CyberLink FCL Driver update if possible:
http://www.cyberlink.com/index_en_GB.html?r=1

aswMonFlt.sys Mon Dec 16 22:28:29 2013: Avast Anti-virus. Please remove and use MSE as it has been known to cause issues:
Link Removed

iusb3hcs.sys Mon May 21 08:23:42 2012: USB3 driver please update:
Link Removed

nvlddmkm.sys Fri Mar 15 01:37:00 2013: Nvidia gpu driver. Please uninstall using this application which will remove old bits of driver:
Link Removed
Re-install driver using latest version:
http://www.nvidia.com/Download/index.aspx?lang=en-us

Rt64win7.sys Tue Sep 27 15:50:33 2011: Realtek Network driver please update:
Link Removed

RTKVHD64.sys Tue Jun 19 09:50:56 2012: Realtek High Definition Audio Function Driver please update:
Link Removed

VMNetSrv.sys Wed Jan 24 12:05:46 2007: Microsoft Virtual Machine Network Services Driver update:
Link Removed

Please post any new dmp files.

Felipe Augusto de Godoy · Feb 9, 2014

I could not update my BIOS because when I opened the executable gave an error saying it was not compatible, and that I should look for a version compatible with Windows 64-bit.
I installed the W7 SP1. Uninstalled AVAST, now I'm using MSE. Updated Realtek Audio Driver. Now I'll update the drivers for the video card. Will edit the post when finished.

@EDIT:
Updated Graphics Driver.
Attached new Minidump

Felipe Augusto de Godoy · Feb 9, 2014

Wow, now I got BSoD two times in less than five minutes. "PFN_LIST_CORRUPT 0x0000004E" and "PAGE_FAULT_IN_NON_PAGED_AREA 0x00000050"

@EDIT:
And another one in five minutes "0x0000001A"

kemical · Feb 9, 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff70001607ee8, 0, fffff80002e6846e, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+ce )

Followup: MachineOwner

Hi,
not sure what happened with the bios update but try downloading the latest version (F5) save to a folder you'll remember or even desktop.
http://www.gigabyte.com/products/product-page.aspx?pid=4402#bios
Then download the application called @bios here:
http://www.gigabyte.com/products/product-page.aspx?pid=4402#utility
Install and run the application using the downloaded Bios file to upgrade. Make sure any overclocking has been removed.

If after updating the bios the bsod's still persist then download and run this app to test RAM (windows memory test just doesn't cut it)
http://www.memtest.org/

Felipe Augusto de Godoy · Feb 9, 2014

Ok, BIOS up-to-date. Thank you. I'll reply here if the BSOD's persists.

kemical · Feb 10, 2014

Thanks for updating your thread.

Felipe Augusto de Godoy · Feb 10, 2014

Well, got BSoD about 3 times today. The same error "memory_management" 0x0000001A. I will try use the mem.test. I will reply here any updates

@EDIT:
Mem.test result: 1 pass, 0 errors

kemical · Feb 11, 2014

Please post new dmp files.

Felipe Augusto de Godoy · Feb 11, 2014

Here it is.

kemical · Feb 12, 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {31, fffffa80039c1c10, fffff88002e6f000, fffff8a00c73c45c}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+71b1 )

Followup: MachineOwner

Hi,
this bugcheck 1A also has a subtype of 0x31 which means its probably a hardware error.
If your using an SSD check for firmware updates. If your just using a normal HDD then right click on your C drive, choose properties, Tools (along the top) and then error checking. Tick any boxes to repair sectors and click ok. You'll need to reboot to perform the chkdsk.

AppleCharger.sys Wed Nov 02 02:46:00 2011: GIGABYTE On/Off Charge driver. May cause BSOD on Win7/8 systems - uninstall to test

aql9t8b9.SYS Thu Aug 01 14:00:35 2013: I've absolutely no idea what this is neither does google. Please download and run this application:
https://www.malwarebytes.org/

Rt64win7.sys Tue Sep 27 15:50:33 2011: Realtek Network driver please update:
Link Removed

Windows 7 Frequent BSODs and Flickering Screen: Help with Error Code 0x000000C4

Felipe Augusto de Godoy

New Member

Attachments

kemical

kemical

Essential Member

Felipe Augusto de Godoy

New Member

Attachments

Felipe Augusto de Godoy

New Member

Attachments

kemical

Essential Member

Felipe Augusto de Godoy

New Member

kemical

Essential Member

Felipe Augusto de Godoy

New Member

kemical

Essential Member

Felipe Augusto de Godoy

New Member

Attachments

kemical

Essential Member

Similar threads