Not sure I understand.. Did you try the Killer 'standard' drivers?i've tried it before but from a diff site. I'll test it again and get post here
Not sure I understand.. Did you try the Killer 'standard' drivers?i've tried it before but from a diff site. I'll test it again and get post here
To be honest I would strongly consider talking to the supplier. If you have had this bsod from the get go then chances are something is wrong hardware wise perhaps a faulty motherboard.yes this issue ive been having has been since i bought the PC.
Its barely 3 months old
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff801c55b74c2, 0, 72436350}
*** WARNING: Unable to verify timestamp for nvvad64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
Probably caused by : nvvad64v.sys ( nvvad64v+74c2 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff80094d774c2, 0, 72436350}
*** WARNING: Unable to verify timestamp for nvvad64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
Probably caused by : nvvad64v.sys ( nvvad64v+74c2 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff8002b4c74c2, 0, 72436350}
*** WARNING: Unable to verify timestamp for nvvad64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
Probably caused by : nvvad64v.sys ( nvvad64v+74c2 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff800fde94b94, 0, 774e6350}
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by : MBfilt64.sys ( MBfilt64+4b94 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff8007be64b94, 0, 774e6350}
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by : MBfilt64.sys ( MBfilt64+4b94 )
Followup: MachineOwner