Jump to content

shark103

Member
  • Posts

    88
  • Joined

  • Last visited

Everything posted by shark103

  1. Make sure what the RAM is set to as auto can be unpredictable. Any other scenario where your PC is unstable/crashes ? Maybe stress test it (use prime95 for CPU, MemTest for ram and Furmark for GPU) so that we could know if there is any issue with hardware, bios settings.
  2. Pull all ram out. Install only 1 stick of new ram into the slot DIMMA2 and power on (try both new ram sticks this way) Did bios load (accessible) ? After power cycling from bios did system load ? If only on one bios and system loaded and on the other nothing = defective ram. If both worked separately then for the time being only idea is that you inserted them in wrong slots. If both worked try plugging them both at the same time (make sure you're using DIMMA2 and DIMMB2) and note what happens. If none worked then faulty ram ps did you update the bios ? You wrote that you tried resetting cmos battery, did you just took it out and put back in ? Maybe clear bios using the button on mobo (manual on msi webpage shows location and tells what to do)
  3. Hi, Few things to narrow down possible problem: Do you monitor CPU/GPU temps in any way ? Any other load crashes the PC or only CS:GO ? Any OC on anything ? RAM set to XMP or auto ?
  4. Your welcome, hope that you will be able to install it soon (if anything comes up again - ping me here) A small path for testing that 64gb if you will go with it, test with linux live distro pass (linux distro launches) - redownload windows iso (use microsoft tool for creating bootable drive, for both creation and booting use usb 2.0 port) and test that Same thing again - disconnect m.2 drive and relaunch installer installer launches normally = m.2 drive faulty or some weird bios setting like bandwidth installer not launches = usb stick damaged Installer launches , installed OS , success and end of topic not passed (live distro not bootable) - usb stick on it's last legs probably and new one will be needed (would use this one for any not backed up data. If on new usb stick same thing happens please check above points also.
  5. One more thing do you need/want a fresh install of windows ? Maybe migration to new drive ?
  6. Using different usb stick for lubuntu is pointless to be honest. While suggesting live linux distro i did it so that you would test that 64gb stick. If that test will pass then in my opinion your windows iso image is at fault.
  7. Looks like a problem with drive or bios problem (maybe something like bandwidth setting). Newest bios or some old version ? Does you mobo manual have any annotations about m.2 <> sata collisions (like if you use m.2 those sata ports will be disabled etc). Stuck iso burning might be burner fault, dvd disk fault but if we add that to usb stick installer not working this could be a faulty iso image.
  8. btw Is the new drive visible on the old win10 install ? ps. did you check that usb stick with any tool for errors ?
  9. What CPU are you running ? With new ram only black screen and no reaction at all while on old ram it works ? No power cycling, no post beeps ?
  10. You could try xubuntu / lubuntu / Puppy Linux Additional things: 1. Is the new drive correctly identified in bios ? 2. Is win10 installer launching without new drive connected or the same issue is present ?
  11. Hi, First thing did you disconnect old drive with win10 before attempting to install new OS on new drive ? Have you tried: 1. Using USB 2.0, sometimes 3.0/3.1 can cause issues with bootable usb drives 2. any linux live distro to check if anything starts from that usb stick / port
  12. Could be RAM related. Try to set you memory timings manually using "DRAM Calculator for Ryzen"
  13. From your post I see that you tried almost everything software side - any conflict on fan control software like having afterburner and precision x installed at the same time ? "Fans do not kick in ever." not even during boot ? Looking at this picture of evga 780 the fan header (white plastic right of power cables) it dangerously close to fins. Maybe during moving the card or during plugging power cord you press a bit to hard in that place at the fins to smashed into fan header. To check this you would have to take the cooler off and look at the header and fan cables if not damaged.
  14. @Khoomn OC won't damage "dp/hdmi port" it could damage core,traces etc but that would be a rare case for it to damage a part of functionality. It is either damaged or we're missing something here.
  15. @Khoomn List of question suggesting what to check basicly : . Did you try a different DP cable on that GPU ? 2.Did you try this DP cable on a different device ? 3. Do you have a known good cable from another device that could be used to check this gpu ? 4.Did you try different monitor on this gpu+dp cable ? 5. Nothing weird in Nvidia panel? 6. Did you try a clean install of nvidia drivers ? 7. Is it working normally on dp/hdmi without OC?
  16. @Khoomn Did you make sure that monitor is not set to auto or hdmi instead of DP ? Some monitors when set to auto can pick signal source at random(predefined order) if multiple cables are attached.
  17. @Ship1617 even without ssd/hdd you should be able to get into bios without gpu ? it depends if you have a cpu with inbuild graphic and monitor is connected to mobo output auto-reboot usually is not due to lack of disk/os as it would just wait for a drive/command etc Maybe start with listing your parts
  18. You mean you got partitions that use only a part of disks ? Your post is kind of all over the place When not sure of what was done etc and having a copy of data a wipe is a good thing because you start with clean slate and setup everything from scratch as it should be.
  19. Use manual for your mobo - they can be found on mobo manufacture website
  20. That can have a lot of underlying causes so it doesn't say much. I'm of out ideas sorry, it's either RAM or PSU. edit: last one tiny thing. You tested RAM module individually but did you try to run the system with only one for a bit to see if it crashes - then switch modules and try the second one this way. You could call it battle testing not with synthetic loads/tests.
  21. Did you try putting only one stick of ram at the time ? Make sure you put the ram in correct slot when putting only one stick. Did you try min setup to check if you get into bios at least - min setup I mean mobo+cpu+one ram+psu ofc but no gpu, no drive etc. Did you try to reset bios (i know you got new mobo but we need to make sure that's it in default setting.
  22. Simplest things first : are all the power cables plugged all the way in (especially 8pin for CPU)? How frequently is this happening ? When did it start ? Only under load or even on desktop/web browsing ?
  23. Hi, With what did you test ram to get such an info ? For RAM testing always use MemTest. Is the RAM still under warranty ? Is this a new, store bought PC ? How long after building/buying this system crashes started?
  24. Hi, First things first- are you getting into bios / monitor gets the signal but stays black or nothing at all (only fans)?
  25. Hey, Kinda looks like either a psu problem with powering the mobo or mobo itself. Is the system working at all (os, bios anything?) when put altogether or is it only powering on prebios and stuck ? You wrote that all parts were tested individually ? All of them even mobo with different cpu/psu/ram/gpu ?
×