Last try before I throw this whole rig into the bin and buy a prebuild

Toggle sidebar Toggle sidebar
V

VioDes

Prominent
Jun 19, 2017
38
0
530
Hallo people,
as you can see in the title, this is my very last attempt to get my new self built system to run.
I've been working on it for several months already, but as soon as one issue is resolved, a new one comes up.

I listed this as a "Windows 10 Subject" but really it is pretty much everything.

So lets start with the system:

CPU: Ryzen 5 1600
GPU: Zotac Gtx 1080 Amp Edition
MB: B350 Tomahawk MSI
PSU: 550 W Seasonic Semimodular
Ram: 4x 8GB Corsair Vengeance 3000 MHz LPX CMK16GX4M2B300C15B
SSD: ~500GB Sandisc Ultra II (OS is installed here)
HDD: 3TB-I don't even know the brand-Datagrave

The problems occur even though no other program is installed on the system. The OS is Windows 10 pro.

The issue(s):
1. When I try to run a heavily taxing program, like Furmark or games like Witcher 3 and/or GtA 5, it crashes to Desktop. Sometimes it simply freezes without even giving a crashreport. Sometimes it crashes and gives some sort of report (I don't remember right now what kind of reports I get in those cases). Sometimes it even works for an hour or so, but usually only for a couple of moments.
The windows event logger (I don't know the exact name in english, since I'm translating on the fly) tells me, that either xyz.exe has had some sort of error, yet it doesn't tell me what kind of error (these error messages appear when the game crashes with a notification onscreen) or it tells me that the nvlddmkm program was not found or stopped working or is not installed or corrupted (these error messages appear when the game freezes and simply goes to Desktop without further notice).
The eventlogger additionally gives me a metric F*ckton of other error messages, but after looong research in the web those seem to be non critical, so let's ignore them for now. Just wanted to have it mentioned.

Talking about research in the web, the nvlddmdkmkmkmkmkm error seems to be quite old already. I found threads dating back to 2010 where people complained about the issue. However not a single one could offer a solution. All those threads simply ended with people giving up and waiting for patches.
I found one article on the nvidia page, that linked the issue to a whole butt load of possibilities. Most of those didn't apply to me, however one thing proposed were problematic ramsticks.
[In this very moment my pc froze, not to be recovered. Had to force choke it off. Eventlogger said it was nvldmschmeckldnmdvbdsam again. It hadn't happened to me when only browsing until now. However Firefox somehow saved what I am texting here, so at least that didn't hurt.]

2. When building the system the first time, I already checked with memtest for faulty ramsticks. All came out working.
I tried it again, today. However this time I only tested one stick at a time. All passed, after that I took one stick and reseated it into each slot, to find out if anyone of those are broken. Nope, all working.
After that I put them all back in, but suddenly the system refused to post. It did that "try to boot 5 times, if it doesn't work by then, just stop trying"-cycle. After experimenting for a while, I found out, that while all slots are fine and all ramsticks are fine, I cant boot the system with all four installed. It doesn't matter which of the sticks I don't install, as soon as three or less sticks are in there, it boots. It also doesn't matter which slot remains free, tried 'em all. As long as one is free, it works.
Right now I have three installed and one stick is sitting on the table laughing at me. I literally changed nothing about the system, no damned idea why it suddenly refuses to eat all four sticks. They worked yesterday.

3. On a similar matter, that means ram again; I can't oc it. Or XMF/R or whatever it is called. They are rated for 3000 MHz, but as soon as I increase the frequency from the 2133 default, the system refuses to boot and goes cycling again until it reverts the change and boots again with 2133 Mhz. That however hasn't changed from the beginning. I thought I matched up a noncompatible stick-mobo combo and left it that way. However I doublechecked it and the vengeance lpx is supported. Again, I have no damned clue where the problem is.


what I already did:
install all drivers, reinstall them, downgrade them, even tried it without drivers at all (lel)
updated bios
cleared cmos
ram check up as mentioned above
i gave up
"repaired" windows with that repair function
formatted C:
reinstalled windows from scratch (same errors)
found a little hope again
all sorts of stresstests (memtest, furmark, some weird-ass cpu test)
gave up hope for good

tl;dr

-nvdlddlflklmsdlknsldkasdmdlksmdlsllknjdsdbsldblsbdd has some sort of issues and there is apparently no solution for it.
-my ramsticks had a sexchange last night and now only operate when in the right mood (#nosexism)
-can't oc my ram

I'd like to think the non-working nvldldldldlixlasidllxlixliaxjdliasdjasdapxoclkasdxalxkashdlamadbskdujasxölxkahsdöliasdasdax program might have a connection to the newly introduced femininity of my rig, however the nvldldldlasldlxxlasdilaisdxlxalsdahliwdhlakxldhalisdhwlmasbdkajwdgkausdhkjxkhuxlasidxlkaxlixhlmgg has had problems even when all four rams were working. So its just as likely, that there is no connection between the two at all.

I hope I made the matter clear-ish. Maybe some of you can help me out, even if only with one of the issues. If there is anything I forgot to mention, I will edit the post. The "what I already did"-section seems awfully short for such a long struggle so I must have forgotten halv. I'll update as soon as i remember.
Thanks for reading guys.

Cheers

Edit the 1st: All temps are always in normal range. During Furmark the Gpu hits 83 °C.
Edit the 2nd: Neither CPU nor GPU have been OC'ed. The gpu has a factory oc though. Used Afterburner to reduce the frequency by 500 Mhz, didn't change a thing.
 
Sort by date Sort by votes
Can you try and set the speed and timing on the ram manually? but ONLY one stick at the time. See if you get errors on every stick. If that is the case you should RMA the motherboard since getting a batch with all 4 ram sticks being broken is not very likely.

Do you have a second computer you can test the ram in? or maybe take them to a friends computer and plug them in there to see if you can set them at the rated speed?
Just to make sure it is not the ram that is messing with you.


I really cant see this being a software problem at the moment.
 
Upvote 1 Downvote
@luminez ty for answering
can you link me a video or so where manually setting the speed etc is explained? i found a couple of them but none really explained it well enough for me.
My confusion is coming from the following: there are four numbers on my sticks (on a lable), 15 17 17 35 and 1.35 V
however the bios wants 5 numbers from me.
Also in the xfr-mode, which my mobo provides, it auto detects the timings. the timings it comes up with are said four numbers.

also i bought the sticks not in a 4-stick-batch but in two 2-stick batches, dunno if that matters.
And they work, all of them. i even stresstested them, its just the combination of four sticks that causes issues. Is that really mobo related?

So you are assuming that this nvmvlkvccvcmvckissmyasswhatanameasd is also hardware related?
 
Upvote 0 Downvote
@luminez
tried that right now
pc refuses to boot at all. Not even goes into cycling mode.
inserted a 2nd stick in there and now it booted into bios. the frequency had been increased to 2933 succesfully. however whenever i try to boot into windows, it tells me "windows repair failed, whatcha gonna do?" basically sending me to restart the system. happened several times in a row.
turned xfr off and everything to auto, and could boot with 2 sticks no problem.

Any clues?
 
Upvote 0 Downvote
@luminez, here we go

used cpu-z cause i have no clue.
some interesting things happened:
first of all: the dram frequency cpu-z shows me is halved, i think i read somewhere, that that is normal cause DDR means double data rate, is that correct?

also i manually typed in those values in the bios while only one stick was installed. Even though all numbers were basically not changed, some changes happened.
i could suddenly boot into windows, so thats a new.
cpu-z now shows dram speed of something 1465-ish, which looks like the oc worked out.
i also thought i should give memtest another quick run.
and now we got several errors. it basically told me "jo dude, there is an error, wanna know more? then go here..."
i'l link the page where it brought me, but it doesn't tell me too much.

Im assuming i should rinse and repeat with all other sticks, or are those errors normal with an oc ram?

http://hcidesign.com/memtest/copyError.html/ver:5.1%20flag:4
 
Upvote 0 Downvote
You are correct about that in CPU-Z the speed is shown in half since DDR (as you stated) means double data rate, so 1500ish means 3000MHz. Give or take a few MHz ofc.

And you are correct, rinse and repeat. Take screenshot of memtest and keep them for a RMA down the line. Hope you still got the shopping receipt for the memory modules 😀
Atleast we have found one problem so far.

But when you do this "rinse and repeat" with every ram module, and if you come across 1 module that works flawless. STOP. Use your computer as normal with that ram stick installed and see if you can make the system crash or freeze.
If it does, no need to panic since the ram module can still be faulty even if it does not show in memtest.

But now I will watch a movie and eat some food, I will check in later today to see how things have progressed for you.

good luck.


EDIT: No if the RAM is fine you shall get 0 errors when the ram is OCed, unless if you push it beyond the rated MHz and timings, then errors can start to happen.
So for you: 3000MHz with the correct timings = 0 errors
 
Upvote 1 Downvote
Soo spent the last 2 and a halve hours or so on this.
holy crap, this was an ordeal.
The first single stick that I tried (and mentioned in my last comment) worked as described. in 2133 mhz, it didnt error at all in memtest btw.
the second one booted and got some errors in memtest at 2800 Mhz. restarted the system -> bluescreen in windows log in screen
played around several times and ways, swapped the dimmslot etc but always ended up bluescreening. Didnt allow me to boot with 2133 either.
the first and second one in combination allowed me to boot to windows, but didnt boot with oc (started cycling again, but with no outcome).

the third and fourth both refused to start in single channel mode and in dualchannel mode.

after all that i thought i might want to check out the first one again; only bluescreens, even at 2133.
Now, in order to tell you what on earth just happened here, i had to put all timings again back to auto, now it at least allows me to boot to windows (on one stick btw).

soooo yea..what is going on?

have a nice evening btw:)

Edit: After a couple of hours of having the pc not turned on, i decided to clean up my desk a little bit and installed the remaining sticks. actually booted into windows (2133 Mhz) but occasionally bluescreens appear.

do you think the ram or the mb is causing the issues?
 
Upvote 0 Downvote
Thats the tricky part, could be the motherboard.... could be the memory... or it could be both.

Is there some way you can try the ram sticks you have in a friends computer? A computer that you know is working correct ofc. Or if a buddy of your could lend you his memory just to do a quick check on your motherboard.

Thats the only way to rule out if there is only the memory or not.
But so far I am holding a button on that your memory is faulty atleast. Question is... How about the motherboard.
 
Upvote 1 Downvote
hmm that sucks :/

sadly no, I dont have anyone with compatible systems around :/

can a faulty mb cause errors at memtest?
I really dont know what to think anymore

the problem is, that i only have the receipt of two of the four ram sticks :/
but then again, what are the chances that four out of four sticks are faulty?
 
Upvote 0 Downvote
If the DIMM slots on the motherboard or something else is faulty on it. It can cause all sorts of problems.

4 sticks, 2 different batches... All 4 faulty... meeeeeh... Not very likely that they all will be faulty, if that is the case then you are just unlucky.
I would atleast RMA 2 of the RAM sticks and get 2 new ones and test then. If you still get the faults. Return the motherboard.
 
Upvote 1 Downvote
That might actually be the one single way to determine what the issue is.
I already contacted the supports of both mb and ram manufacturers. Maybe they have some sort of experience with all this.
 
Upvote 0 Downvote
I would consider buying another B350 motherboard (different make and model as well). Fortunately you can get one for less than $100. If the system behaves, you have your answer. You can RMA the original board or simply deposit it in the nearest ewaste receptacle. If it turns out that the original board is fine, you can put the second board on craigslist or ebay and get half of your money back.
 
Upvote 1 Downvote
@neiler0847 I'd like to prevent additional spending, since the PC already ate all my budged.
@scottfree1_1 As I mentioned, I already tried that to the extend that I underclocked the card by 500 Mhz. Didn't solve the issue though. Additionally, ever since this weekend, my pc started crashing even when only browsing. I consider it to be highly unlikely, that the GPU causes the issues.
 
Upvote 0 Downvote
Can you return the MoBo as faulty. and try a replacement. I am wondering if there is a cracked track that is thermal ( makeing and breaking due to heat.
You appear to have tried everything else.
Good luck
 
Upvote 1 Downvote
@grumpy275 that is most likely what I am going to do. I'm just waiting to get a reply from the customersupports before that. Maybe they are familiar with the issue/know that certain production batches are likely to get this error. MSI already responded and told me to update my bios (duh)...so much for a good customersupport, that actually reads the emails they are being sent... -.-
The explanation you provided/suggested actually seems to be quite reasonable. I'm really having a hard time trying to believe that all four ramsticks are faulty.
Thank you :)
 
Upvote 0 Downvote


 
Upvote 0 Downvote
In the past I did some work on Memory chips. We found that if they are subjected to Static they can do all sorts of strange things. Sometimes not even predictable. I guess its not beyond the chances for a static discharge to have hit the stickes even in their Antistatic packaging. Unlikley perhaps but nothing is impossible.
You said you had not got anyone nearby who could help test. are you able to indicate your area so someone on here may be in striking distance to help. Dont give exact details perhaps state and county may be good enough. I am afraid I am in the UK
 
Upvote 1 Downvote
@grumpy275 things are turning more and more spacey with the minute. If said case would turn out to be true, would such a static fry the internals of the stick or is there a way to discharge it?
Well I'm from Munich/Germany, highly doubt someone here is from the area, but its worth a try:)
 
Upvote 0 Downvote


 
Upvote 0 Downvote
Once a static discharge has hit a "Chip " there is nothing you can do. The chip can be totally killed or it can be "stressed" and still appear to work then do peculiar things at different temperatures sometimes at higher or sometimes at lower temperatures. sometimes chips madse by one manufacturer will exhibit different characteristice to anothe manufacturer. This is I guess caused bydifferent masks used in the production. Surfice to say it can be very strange.
As a matter of interest I always buy from Amazon. they are not always the cheapest but their returns police is worth every extra penny or euro you may spend.
You are in Germany I am in the UK so I would say there is a fair chance there are others in Germany on this site.
 
Upvote 1 Downvote


I haven't read all the replies, but I'm wondering - what power supply are you using? I had all kinds of bizarre issues with a computer a few years ago get solved by buying a decent power supply. It was the one thing I had cheaped out on. NEVER AGAIN. Clean, reliable power is essential.

Just a thought if you haven't hit that one already. Cheers.

UPDATE: Yes, I have also had weird issues with memory that ONLY showed up when I tried use PAR repair. It kept retrying and retrying, and that was the only indication that anything was wrong with my RAM.

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom