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.
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.