Jump to content

Mjolkspam

Member
  • Posts

    23
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About Mjolkspam

  • Birthday Jun 15, 1989

Contact Methods

  • Twitter
    Mjolkspam

Profile Information

  • Gender
    Male
  • Location
    Sweden

System

  • CPU
    Intel i5 4670k 3.4Ghz
  • Motherboard
    MSI Z87-G45 Gaming
  • RAM
    Corsair Vengeance LP 1600MHz CL9 2x4GB
  • GPU
    MSI GeForce GTX 970 Gaming 4GB
  • Case
    NZXT H440 Black/Red
  • Storage
    Samsung 840 EVO 250GB SSD, 3x 1TB
  • PSU
    EVGA SuperNOVA G2 750W
  • Display(s)
    AsusAsus VG248QE 144hz + BenQ G2420HDBL
  • Cooling
    Antec Kühler H2O 920
  • Keyboard
    CM Storm Ultimate Quick Fire
  • Mouse
    Mionix Naos 8200 @ 1400 dpi
  • Sound
    Realtek ALC1150 + Asus Xonar DX
  • Operating System
    Windows 8.1 64-bit

Mjolkspam's Achievements

  1. Everything is at stock for the moment and have been since I got the new GPU / PSU. When searched on @Droidbot it does not indicate dying hardware!? The ansers you get is that an driver is failing. I'm going to wait until I get an more "serious" answer. Not to be an ass right now, but the answers I get right now seems like you're guessing about the issue. Thanks anyways, allways appreciated
  2. I might sound stupid now.. but doesnt the motherboard need to be "grounded" (It's getting grounded when mounting with screws on the chassi). This was an issue on older, never tried now a days tho
  3. Hello. As the title says, I could need some help with some random BSOD I get. driver_irql_not_less_or_equal ( bugcheck code: 0x000000d1 ) Thats the one I get, more info in the files. It can happen at random, but I think it's happend the most times when gaming. When I got the BSOD at the 15th of March I started to uninstall programs thats not needed. So I have cleaned some stuff away. But obviously it didnt help.. So I'm kind of stuck at this. About 2 month ago I got a new GPU and PSU because my old GPU died when playing World of Warcraft. I had this issue before the GPU died, so I thought this was the problem, faulty gpu or psu and so on. I got the PSU aswell because I had 2 or 3 shuttdowns that was caused by my motherboards built-in powersurge protection. Wasnt going to risk a new GPU to the old PSU if that was the cause of the old one dying. If you need more info about the issue, just tell me. I probably missed something. Any help to solve this problem would be awesome. It's driving me crazy. OS: Windows 10 x64, Retail. (I have not yet re-installed the OS). (Only this OS have been installed on this setup). Age of the system: 2-3 years (GPU and PSU is only 2 month old). It's an Desktop CPU: Intel Core i7 6700K (I get the BSOD with or without my 4.6Ghz O.C) Mobo: Asus Z170 Pro Gaming GPU: MSI Armor GTX 1070 PSU: EVGA SuperNOVA G3 750w This is the link to the .zip files. https://drive.google.com/open?id=0ByR72onbr_8ScFJNT04wbXNMRFk
  4. Could be, but that sound linked in that post is way worse than I have ever heard. That would scare the hell out of me. So I don't know, feels wrong. I will try with mumble closed while downloading using Origin again. I'll be back EDIT** It has nothing to do with mumble and download speed with Origin does not matter either. Just a few minutes ago I got the sound again, did not download or use mumble. So I'm lost again.. this is just so weird. Never experinced anything like this before.
  5. I would say it's not part of windows sounds. I have never heard it before. Atleast what I can tell now. So if it's a windows sound, I sure have missed that. Some random noise then I guess.
  6. PC 363D sure is good. I would go for Sennheiser G4ME ZERO instead tho. I'm using those now and used PC 350 before that. I have not used anything better than those.
  7. Hello. As the title says, I'm getting a werid sound only when downloading. I can't realy say when it started as I download most of the time when not at the computer. But noticed it yesterday when installing/downloading BF4 from Origin. This video explains it all. The sound is just before my friend talks. https://www.youtube.com/watch?v=DPeER0XwSDo Keeps happening once in a while. I not realy sure, 5-10min maybe. So it's not very often. I use two soundcards, Realtek ALC1150(MSI Z87 G45 Gaming Mothertboard soundcard) and my Asus Xonar DX for everything else. Using Killer NIC E2200 (OnBoard network). Lastest drivers for everything aswell. Rest of my setup should be in my signature. If you need more info about anything, just ask please. I can't come up with more that needed right now as my setup is in my sign etc. Thanks for all the help in advance. / Mjolkspam
  8. Mjolkspam

    OC Screens

  9. Okey, I did not start with 43x now though. Stupid as I am.. (1) (2) edit** I have been running 42x 1.27V, Ring @ Auto(34x) with Auto voltage, VCCIN 2.0V for 12-14h gaming all day long.. No BSOD at all! Just running like smooth butter. To me, this is awesome news. But what do I know Sending this might BSOD me.. (This is the one I'm using on a normal day as of now. Until I get a better one.) edit**(2) I had XTU running the other night for 8h+, with above settings. Works like a charm. Still running without restart, played BF4 like a crazy man. http://linustechtips.com/main/gallery/image/16115-34ghz-127v-stable-xtu-oc/ Going for 43x tonight, lets hope I don't get x124.. Where to start if I get x124 BSOD again? Increasing vcore to 1.28V or ring voltage to something? edit**(3) 43x did 8h+ without crash. Now I'm up against using it all day and playing some. + Crashed during the day while playing BF4. x124 bsod again. I'm not realy sure where to continue now. Thinking of trying 43x but with 1.28V instead of 1.27V (Ring 34x(auto voltage), vccin 2.0, 1333Mhz 1.5V. edit**(4) This has been game stable for 12-14h + 10h XTU stable.
  10. @ProKoN Hello again, long time no see. Now I'm back to OC my CPU. Had a break from everything. This time though, I have a new PSU, and even newer bios update for my MSI Z87 G45 Gaming (Version 1.9). When I started yesterday everything looked awesome, I tested where I left off, which is at 4.4Ghz 1.32V, Ring was at 3.4Ghz and Auto voltage, VCCIN 2.1. Ran a test for 10h+, just started to do my stuff as a normal day as it looked good. Then everything crashed with WoW and a movie on second screen. BSOD was x124 which is ring voltage if I remember correct. So I started everything over by updating everything, thats where I got my 1.9 bios. Started at the top of the guide with a cmos clear and everything. 4.4Ghz 1.25V, VCCIN 1.9V, 1333Mhz 1.5V memory. Funny thing with this is before when I did this, It didnt even boot. Now it does though. Without failure past 8 Cinebench tests and 1 hour of XTU. Then I got my BSOD with x124. So I change ring to 3.4Ghz manual with 1.27V, but nope! Crashed ever faster this time. So what the hell, increased VCCIN to 2.0 and ring to 3.4Ghz with 1.3V. Not even this time I manage to run it for long, a few Cinebench + few minutes into XTU. x124 error. Lowered the ring to 3.0 with the same settings, same old. I don't know, in my eyes it should not be x124 crash when I have 4.4Ghz 1.25V witht he ring at a low 3.0Ghz 1.3V, VCCIN 2.0V? Shouldnt it be more x101 (correct me if I'm wrong) which is for an low vcore voltage? At this point I'm confused what I should do yet again. x124 at that low of an ring is weird. Some help?
  11. I'm on the latest bios. I have never reflashed or rolled back a bios before, not on UEFI atleast. Reflashing the same, just download and install again i guess? And same goes for if i roll back? Just install it.
  12. @ProKoN, please check my post above this one as well. Need answers for both. **EDIT** We can scratch pretty much the things inside the spoiler.. I know why I couldn't press F1 to begin with, I had my CM Storm Ultimate keyboard on "N" mode, so I can press more than 6 keys at the same time, that will do so it doesn't work before the UEFI had loaded So that is fixed. But the other problem was still there. I did a test to see if it happened again, so i turned the PC off. Waited about the same time as before, started it up and the same thing happened. It says the previous OC failed or something like that (A fail safe I guess). The weird thing is tho, I ran that OC the whole day yesterday and today, but when started up again after a shutdown, all of a sudden it fails? And if I load that profile with those OC settings I have no problem what so ever booting into windows? All this seems weird to me! My thinking off this is that my PSU is failing me? As I have performance issues in games even on stock (mentioned this before). What if my PSU can't deliver anymore? What if that's the reason i'm having such a hard time getting stable OC's even tho it was stable for 12+ hours before. Like it can't deliver whats needed when it's really needed or something. Please say that i'm wrong.. That it has to be somethings else. Any ideas? Well off to sleep for now, soon 6 in the morning here in Swe
  13. Page 25, so a new post inc. **EDIT** One **EDIT** Two Okey.. I'm starting to get pissed on my cpu now I increased the uncore voltage to 1.33V, I didn't have the chance to do a stress test tho. I'm watching NHL (Pittsburgh vs. NY Rangers), got X124 BSOD! So for now, I left ring bus ratio at Auto (3800Mhz). uncore at 1.32V tho. As it looks now, i'm having a hard time getting it stable with: CPU 4.4Ghz, vcore 1.32V "The Ring", 4000Mhz, uncore 1.32V (tested 1.33V) vccin @ 2.2V Memory, 1333Mhz 1.5V In my eyes, this is just bad.. I'm starting to think I have a bad chip more and more =/ You got any ideas for me ProKon? Mini Edit! I know i asked this on page 23, but i need to ask again. Now when i'm finding my OC not stable anymore for some reason, should i change CPU Ratio Mode from 'Dynamic' to 'Fixed'? (Noticed you used 'fixed' in your video). Same goes for voltages, while finding an stable OC, should i use Adaptive or Override?
  14. I'm using spoilers to minimize the post I edit this post instead of doing a new one. I'll do a new one sooner or later, just felt like spam doing a new with only one post under me Part 1: Edit 1: Edit 2: Edit 3: Edit 4: Oh, i thought i wasn't gonna touch the uncore volt until i was starting with the ring bus So i left that at auto and set the ratio for the ring at 34 (3400Mhz). Anyways, I increased the "The Ring" this time. 4000Mhz with 1.32V (Everything same as the edit above). Before I cancelled the stress test, it was active 10+ hours. Temps where the "same", 78 this time at it's peak. https://hostr.co/file/QBS9a86BJp4M/4.4Ghz-vcore-1.32V-vccin-2.2V---ring-4000Mhz-1.32V.jpg I didn't go for 4400Mhz on the ring as I actually tried that before. Crashed after 1 hour or so if i'm not wrong. I'm going to try it again, but it's a long shot for me at these voltages I think. It's either that or 4200Mhz tonight. I even think i'm gonna try to lower the vcore to 1.3 or 1.31. I havn't tried 1.31V i think, have been much to do a few days now. So i can't remember if I missed that. But what the heck, I got good temps at 1.32V, maybe I should just stay there One thing tho, If i'm not able to get 1:1 ratio at 4.4Ghz with 1.32V, should I be happy with 4000-4200Mhz on the ring? Or should I try increased the uncore voltage and see if i can manage the temps to maybe get a stable 1:1 ratio? What do you think ProKon?
  15. So true. I lowered my ring ratio to 4200Mhz with 1.29V, vccin @ 2.0. Crashed after 5 hours or so. I got a BSOD 0x0000009c. I even got an Bug Check String (MACHINE_CHECK_EXCEPTION) this time. I'll try with vccin back at 2.1V again at 4200Mhz. If that doesn't work, i'll lower it to 4.1 or 4.0. Because as i understand it, i shouldn't go higher than 1.29V on the ring bus? As I use 1.29V on the vcore.
×