Jump to content

So, several weeks ago a friend and me started a threadripper build, that from the beginning started giving us trouble. First time trying to put everything together outside of the box, like everyone always recommends, didn't work, and we kept on getting post error code 00. We thought it was the RAM or the processor, but it ended-up being a faulty motherboard. Got a replacement and everything, and we were able to get a post, install operating system and drivers. But now OS keeps on crashing.

These are the errors that keep on popping-up:

  • Windows failed to start. A recent hardware of software change... (Black screen)
  • Recovery: Your PC/Device needs to be repaired (file: \Windows\system32\drivers\Wdf010000.sys) (Error code: 0xc0000221)
  • Stop code: DPC WATCHDOG VIOLATION

This is getting frustrating and we have tried everything that we can, also given that the Ryzen platform is fairly new there is not a lot of information out there of what could be happening.

Any help will be appreciated, thank you all on advance.

Link to comment
https://linustechtips.com/topic/845122-consistent-error-on-threadripper-build/
Share on other sites

Link to post
Share on other sites

1 minute ago, ItsTheDuckAgain said:

my guts tell me this sounds like bad ram and/or motherboard...

 

MSI by any chance?

It's all Asus, but i think we just figured it out. Redid all partitions on the SSD, it's now running, hopefully it stays like that. I'll keep updating if anything goes wrong.

Link to post
Share on other sites

3 minutes ago, ItsTheDuckAgain said:

my guts tell me this sounds like bad ram and/or motherboard...

 

MSI by any chance?

MSI makes some of the best MOBOs around so dont blame the MOBO ( as i was writing this he said it was ausus anyway but my point still stands) try a different RAM config, boot without a graphics card, try a linux installation a usb.

 

messege me when your done

Link to post
Share on other sites

Just now, TheCODclown25 said:

MSI makes some of the best MOBOs around so dont blame the MOBO ( as i was writing this he said it was ausus anyway but my point still stands) try a different RAM config, boot without a graphics card, try a linux installation a usb.

 

messege me when your done

oh boy, sorry that I asked about the board beeing MSI and me ranting on about it for literally thousands of words where I broke all hell loose about MSI and never said a good word a bout them as you can clearly see in my posting above... Didn't mean to offend you. Please forgive me!?!

Link to post
Share on other sites

1 minute ago, ItsTheDuckAgain said:

oh boy, sorry that I asked about the board beeing MSI and me ranting on about it for literally thousands of words where I broke all hell loose about MSI and never said a good word a bout them as you can clearly see in my posting above... Didn't mean to offend you. Please forgive me!?!

you can clearly see in your message that you were implying that MSI makes bad boards, if you didn't i apolgise 

Link to post
Share on other sites

4 minutes ago, TheCODclown25 said:

MSI makes some of the best MOBOs around so dont blame the MOBO ( as i was writing this he said it was ausus anyway but my point still stands) try a different RAM config, boot without a graphics card, try a linux installation a usb.

 

messege me when your done

I think it's done, we redid the partitions on the SSD and apparently it's working for now, hopefully it stays like that.

Link to post
Share on other sites

1 minute ago, TheCODclown25 said:

you can clearly see in your message that you were implying that MSI makes bad boards, if you didn't i apolgise 

well you thought I did. Actually MSI makes great stuff including boards. i just asked because I got a similar problem just four week ago when building a ryzen system with an MSI board for my neighbor. Turned out the board was faulty, twice. so...

but yeha, no bad feelings :-)

Link to post
Share on other sites

Just now, ItsTheDuckAgain said:

well you thought I did. Actually MSI makes great stuff including boards. i just asked because I got a similar problem just four week ago when building a ryzen system with an MSI board for my neighbor. Turned out the board was faulty, twice. so...

but yeha, no bad feelings :-)

ah my mistake, sorry but yeah no bad feelings. seeya

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×