Would appreciate help with this

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#81
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?
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#82
yes this issue ive been having has been since i bought the PC.
Its barely 3 months old
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.
 


Zalthoria

Well-Known Member
#83
I actually already did talk to the supplier. But they kept saying stuff like its the driver and asked me to reinstall it from the MSI site. even after me repeating that ive reinstalled the drivers umpteen times. And when i finally got through to them, they said that because its such an unusual issue that they have never encountered before, they would have to send the board back to MSI for testing and that would take 8 weeks or more> and i wasnt really willing to let my motherboard go for 2 months this close to fallout 4's release :/

Anyways, yea i just tried the standard drivers, and it still BSODed
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#84
Code:
*******************************************************************************
*                                                                             *
*                        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
Now it's blaming the nvidia audio driver. If you don't use it then remove it and try again.

Regarding your conversation to the supplier it would have been nice if you had shared this information with me from the get go.

So basically I've been trying to repair something you know may well be faulty. Ultimately i'm not sure what you think we can do? If the board is faulty then it's faulty and no amount of driver changing is going to effect that.

As you know computers should not be blue screening when brand new and this should have been dealt with as soon as you suspected their was an issue.

It sounds like the supplier is trying to get out of doing any repairs I'd learn what your rights are and go back.
 


Zalthoria

Well-Known Member
#85
i wasnt absolutely sure that it was faulty i was just hopiing the supplier could do something about it.

i will speak to my supplier again and see if we can't work something out.

I appreciate all the effort and time helping me with this. it is really greatly appreciated
 


Zalthoria

Well-Known Member
#86
Erm this is awkward but the problem i had with the non paged pool seems to be fixed?
Which is weird cus i've done all these steps before.
Sidenote: its okay that my cached memory is like 12.5gb right?
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#87
Best thing to do Zalthoria is monitor the situation and see. Sometimes changes you make regarding RAM can take a while to filter through so keep an eye on things. Let's hope we can get this fixed for you so don't even have to bother with the supplier. What did you do regarding the nvidia audio driver?
 


Zalthoria

Well-Known Member
#88
i just removed it cus i wasnt really using it i think.
it was fixed before i removed it though. Gonna do driver verifier now.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#90
Code:
*******************************************************************************
*                                                                             *
*                        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
Same again. Try re-installing the Nvidia drivers making sure you use the DDU to remove the original driver. When you re-install the nvidia driver use the 'custom' method and untick audio as well as anything else. When i install them i only tick the actual driver and physx. The gfe will slow your machine down so don't install it.
 


Zalthoria

Well-Known Member
#91
yea i did that but i didnt remove DDU to remove i just did uninstall from my uninstall programs.
Will try the DDU asap. Thanks man!
 


Zalthoria

Well-Known Member
#92
Nope :(
I did DDU which rebooted into Safe mode before removing.
after that i reinstalled the driver and only Phyx
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#93
Code:
*******************************************************************************
*                                                                             *
*                        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
Same again would you believe it... I wonder if the nvidia folder is tripping it. When you install the nvidia driver it places like a recovery folder on the c drive. Try deleting that and see if it makes a difference failing that do a search.
Right, I'm going back to playing fallout 4. I'll check back in a while.
 


Zalthoria

Well-Known Member
#94
For some reason that particular driver would keep showing up on the verifier list till i went to device manager and removed it. hahas and now it shows a diff driver.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#95
Code:
*******************************************************************************
*                                                                             *
*                        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
Hi,
This relates to a audio driver.
MBfilt64.sys Fri Jul 31 04:40:32 2009: Realtek HiDefinition Audio driver. Please update using the driver available from the MSI support site. This driver may look like a Creative driver and I think it actually relates to the 'Sound Blaster Cinema 2' found in the utility section.
Motherboard - The world leader in motherboard design
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#96
Any news?
 


Zalthoria

Well-Known Member
#97
Sorry got a little caught up in fallout 4.
Okay so i uninstalled soundblaster and realtek, and redownloaded and installed only realtek.
And there was still error
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#98
Code:
*******************************************************************************
*                                                                             *
*                        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
Same again but this is probably going to keep happening as the board is probably faulty. You really need to get going with that supplier as this is just going round in circles really. Also try turning the verifer off and seeing the bsod continues. Sometimes the verifier can stress drivers to bsod when they normally wouldn't.
 


Zalthoria

Well-Known Member
#99
Alright i will monitor awhile longer and take it up with the supplier. thanks so much for your time!
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
Ok I really think thats your best option but if you do get another bsod then post it and we'll take a look. It may help if we could at least track down where the issue may lie with the board. In any case please let me know how you get on.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.