Window 7 BSOD BCCODE: C4

Zong Hong

Reputable
Apr 11, 2015
1
0
4,510
Hi everyone, I am now in window 7 safe mode with networking.

When I turn on my computer today, it wont startup in normal mode instead it goes to BSOD with the BCCode : C4.

This is what happen when I just turn on my computer in safe mode:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 18441

Additional information about the problem:
BCCode: c4
BCP1: 0000000000000091
BCP2: 0000000000000002
BCP3: FFFFF80003617CC0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\041115-31808-01.dmp
C:\Users\user\AppData\Local\Temp\WER-56565-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

This is my minidump information:

https://onedrive.live.com/redir?resid=3F625F84DEEDA9A7%21118

I tried solving this problem by:

Running Startup Repair, it does not work.

When i run startup repair, all it does is restart my computer and goes back to 2 option: run startup repair or run windows normally.

If i tried to run window normally, the BSOD appears and restart my computer and back to the 2 option.

Running System restore, it also does not work.

I tried to run system restore and it will does not work also. There an error occur when i run system restore.

Please help.

Thanks in advance!
 
Solution
looking at the second bugcheck: verifier claims to have caught the nvida driver doing something it should not do. looks like you have old nvidia driver installed (2011) so it could be correct and you would just update the drivers. if you can boot and run cmd.exe as an admin then run
verifier.exe /reset
it might turn off the checking so you can update the drivers. Otherwise you would have to go into safe mode to fix the problem.

looking at the first bugcheck, 0x116 the video driver did not respond within its timeout (2 seconds i think by default)

looks like a older machine, so check for overheating, blow out the dust, update the drivers below, disable your unused high definition sound drivers in windows control panel device...
looking at the second bugcheck: verifier claims to have caught the nvida driver doing something it should not do. looks like you have old nvidia driver installed (2011) so it could be correct and you would just update the drivers. if you can boot and run cmd.exe as an admin then run
verifier.exe /reset
it might turn off the checking so you can update the drivers. Otherwise you would have to go into safe mode to fix the problem.

looking at the first bugcheck, 0x116 the video driver did not respond within its timeout (2 seconds i think by default)

looks like a older machine, so check for overheating, blow out the dust, update the drivers below, disable your unused high definition sound drivers in windows control panel device manager. if you don't get sound via your video cable to your monitor speakers you can disable the grapic card sound support.


when you are done, boot into BIOS and update the BIOS or reset it to defaults and reboot. This will make the BIOS reassign various hardware setting and rebuild the database of settings it sends to windows. it can resolve some pesky little conflicts between sound cards and sound soupport on GPUs.
-----------

your sound driver are too old and can conflict with the sound support in your graphics card.
Realtek High Definition Audio Function Driver
\SystemRoot\system32\drivers\RTKVHD64.sys Tue Nov 30 01:03:19 2010


your network drivers are too old and will mess up the nvidia streaming drivers.
Atheros NIC driver update here or from motherboard vendor: https://www.atheros.cz/ (pick L1C driver)
\SystemRoot\system32\DRIVERS\L1C62x64.sys Tue Aug 24 02:14:01 2010

you might want to update this driver:
\SystemRoot\system32\drivers\GM3305Fltr.sys Wed Mar 28 10:46:15 2012
i think it a gaming mouse but I am not sure.
 
Solution