Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffffac0160ce108, 2, 0, fffff88002c5ce65}
*** WARNING: Unable to verify timestamp for e22w7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
Probably caused by : e22w7x64.sys ( e22w7x64+6e65 )
Followup: MachineOwner
the...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
Zalthoria
Well-Known Member
- Joined
- Sep 26, 2015
- Messages
- 71
- Thread Author
-
- #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
Anyways, yea i just tried the standard drivers, and it still BSODed
Attachments
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
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
- Joined
- Sep 26, 2015
- Messages
- 71
- Thread Author
-
- #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
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
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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?
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
Right, I'm going back to playing fallout 4. I'll check back in a while.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
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
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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.
Similar threads
- Solved
- Replies
- 16
- Views
- 4K
- Solved
- Replies
- 12
- Views
- 3K
- Solved
- Replies
- 1
- Views
- 2K
- Replies
- 1
- Views
- 1K
- Replies
- 2
- Views
- 3K