BSOD code c5

[phil128]

Hi all. I've had my i7 860 overclocked for a few days now. Its been fine until I booted into windows just, and I got this:

BCCode: c5
BCP1: 0000E1F0
BCP2: 00000002
BCP3: 00000000
BCP4: 82F58795
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

I'm currently running memtest ATM.

Does anyone know what this error code might be? Ram or CPU?

Thanks.

 

[Stop It Rawr]

From a bit of trawling around, I finally got this useful bit of info:

BC Code c5 is DRIVER_CORRUPTED_EXPOOL
"This indicates that the system attempted to access invalid memory ... "

So, either the memory is having a bad time of things, or you have a dodgy driver causing this. Did you recently install new drivers for anything? If memtest passes but the issues occurs again, try to note down the driver referenced in the BSOD as it may darrow down the issue if it isn't a hardware fault.

If you haven't already, turn off the auto reboot when you BSOD, it'll help identify the root cause of the crashes.

http://pcsupport.about.com/od/windows7/ht/automatic-restart-windows-7.htm

 

[phil128]

Cheers for the reply. I haven't installed any drivers recently. I'm trying to get windbg and see if I can look at the crash dump.

I'll keep ya posted

 

[phil128]

I'm not too sure if this helps, but I've had my windows 7 installed for 3/4 months now. Since then I've had various BSOD's due to overclocking etc. So atm my system (I though) is stable....

Could a reinstall of windows 7 help, with my current OC settings.

Thanks

 

[phil128]

Here's what windbg has shown me:

MODULE_NAME: CI

FAULTING_MODULE: 82e38000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bdac8

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 0

FAULTING_IP: <--------- Memory instruction pointer.
nt+120795
82f58795 8b10 mov edx,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 82f58795 to 82e7e82b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80785f1c 82f58795 badb0d00 82f6da48 8b21b5a6 nt+0x4682b
80785fc8 82f578aa 82f6d8c0 00000000 00000042 nt+0x120795
80786030 82ec6e55 863caaf8 00000000 00000042 nt+0x11f8aa
8078604c 82ea0c9a 863caaf8 863caaf8 863cacd0 nt+0x8ee55
8078608c 8b215a7b 00000000 863caaf8 00001c20 nt+0x68c9a
807860a4 8b21e626 80786180 863caaf8 00000000 Ntfs+0xca7b
80786170 8b221bae 80786180 863caaf8 00c8070a Ntfs+0x15626
807862ac 82e744bc 862fd020 863caaf8 863caaf8 Ntfs+0x18bae
807862c4 8afc320c 862f0890 863caaf8 00000000 nt+0x3c4bc
807862e8 8afc33cb 80786308 862f0890 00000000 fltmgr+0x620c
80786320 82e744bc 862f0890 863caaf8 863caaf8 fltmgr+0x63cb
80786338 82edd010 863cad00 00000000 00001000 nt+0x3c4bc
80786354 8af193e9 863cfa78 853386c8 80786398 nt+0xa5010
807863c8 8af18880 863cfa78 000011a0 00001a80 CI+0x73e9
807863f0 8af189ae 863cfa78 8ff40000 80786420 CI+0x6880
807864c4 8af18ecf 863cfa78 8ff40000 00000fa0 CI+0x69ae
8078653c 83012d8e 863cfa78 8ff40000 00001000 CI+0x6ecf
80786558 83012bf9 863cfa78 8ff40000 00001000 nt+0x1dad8e
807865cc 8305b918 863cfa78 863ca008 00000001 nt+0x1dabf9
807866f4 83068ed1 80786748 00000008 80786860 nt+0x223918
80786768 82e7b44a 80786890 00000008 80786860 nt+0x230ed1
8078678c 82e79055 badb0d00 80786804 00000000 nt+0x4344a
807868bc 82ffc62b 80000120 82f80810 853386c8 nt+0x41055
80786904 82ffc435 80786b30 00000000 80786928 nt+0x1c462b
8078692c 82ffbe0a 80786998 80786b30 00000000 nt+0x1c4435
807869a8 82fdb2d8 80786b30 00000000 00000000 nt+0x1c3e0a
80786b9c 831e9853 00000001 00000000 80786bd4 nt+0x1a32d8
80786be8 831e587b 8080fb58 8080a7c0 00000000 nt+0x3b1853
80786c6c 831eae78 0080a7c0 85338a38 853386c8 nt+0x3ad87b
80786d48 82fc3494 80786d90 830466d3 8080a7c0 nt+0x3b2e78
80786d50 830466d3 8080a7c0 afd096d9 00000000 nt+0x18b494
80786d90 82ef80f9 82fc3487 8080a7c0 00000000 nt+0x20e6d3
00000000 00000000 00000000 00000000 00000000 nt+0xc00f9


STACK_COMMAND: kb

FOLLOWUP_IP:
CI+73e9
8af193e9 ?? ???

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: CI+73e9

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: CI.dll <------- Dll file!!!!

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


I'm trying to think if my overclock doesn't have anything to do with this at all.
sorry about not putting the above in tags (Dunno how to do them).

 

[Stop It Rawr]

Yep, that doesn't sound like OC related issues to me, more like a corrupted file going by what I can find. Try the following:

Cause:

The above STOP error message appears when Ci.dll file is corrupted.

Resolution:

To resolve the above error message and to access the hard drive data, you will need to:

* Use “Startup Repair” option to resolve the booting problems.

HTH.

 

[phil128]

I've just reinstalled windows 7 after I had another BSOD. It was due to some .exe file.

I've also decided to throw away my wireless usb device (Cheap no branded one), as I remembered the other month my PC BSOD'ed on me when I inserted o) my wireless device in my computer.

Using an alfa network one now rtl8187. Had it for years, only I decided to buy another one due to my alfa is only a wireless b/g not n.

I'll keep you guys posted too.

Thanks for your help.