Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Potential mobo issue but not sure, questions inside


  • Please log in to reply
11 replies to this topic

#1 enkay85

enkay85

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:49 PM

Posted 13 July 2017 - 03:52 PM

Hi everyone - bit of background for you below.  Really hoping someone can point me in the right direction :)
 
PC specs:
 
PC is from 2012
Intel i5-7350k (3570k? Not at home it's one of the two) 3.6ghz
GeForce 1080 6gb (purchased 2016, replaced old card)
16 gb DDR3 ram (purchased 2016)
750W power supply
ASROCK z77 Extreme4 motherboard
Running Windows 10 (issues were not on Win7, but perhaps unrelated since I updated 9 months ago)
 
About 8 weeks ago or so I have been noticing strange issues with my PC that a friend told me sounded like Motherboard issues since they were all over the place but I was hoping to potentially narrow down the problem. I did run some tests on the CPU from Intel and they all came back OK, and ran some freeware tests on the memory and CPU which also came back ok but not sure how accurate those are outside of the Intel test.
 
Essentially a few things are happening randomly and can only be fixed with a FORCED reboot:
 
-First off, I have to force reboot because when I begin to notice an issue and I go to Start -> Restart and while my monitor will turn off the PC never reboots (fan keeps running)
 
-Randomly Chrome or any other browser will begin locking up and I'll get plugin crashes.  A sure fire way for me to test if my PC is acting up and needs a force reboot is if I goto youtube and the videos don't load but I get a permanent video loading icon (although when I mouse over the bar to fast forward I can see thumbnails)
 
-Microphone on my headset won't work, but the sound does
 
-I do play video games, and none have really caused much of an issue but I get most issues when playing WoW (perhaps because it's a larger memory sink?).  For instance, when running WoW and Discord I can play fine but after a few hours - or a few days the problem sometimes comes frequently or disappears for days on end - I'll be unable to chat on Discord/voice comms and Chrome won't work, but all in-game sound and graphics work and the game runs fine.
 
-Reboots, forced or otherwise, are taking longer than usual (probably 3-4 minutes which seems long to me)
 
Again, the problems can come as soon as 30 minutes into my PC being on or as long as a few days. Seems to occur faster when gaming but that isn't always the case. Any guidance would be much appreciated.
 
 


BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 24,312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:49 PM

Posted 13 July 2017 - 04:10 PM

The first thing I would do is turn off fast startup and reboot. 

 

Look in Event Viewer for any possible clues on the freezeups. 

 

You mentioned testing the RAM and CPU. Have you tested your hard drive? If not run Seatools for Windows doing the short and long generic tests. If your drive is WD then use the WD datalifeguard diagnostic.

 

If everything passes look at running sfc /scannow at a command prompt and DISM.

 

If you still have problems consider resetting Windows 10 with the option to keep your files or do a complete clean install using the Media Creation Tool to create a bootable USB or DVD. A clean reinstall is always the best option after upgrading from a previous OS. Because you have already activated Windows 10 the license is on Microsoft servers. When it asks for a key click next without entering anything.



#3 MrSippi

MrSippi

  • Members
  • 83 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:05:49 PM

Posted 13 July 2017 - 06:51 PM

This suggested one of two things to me, heat or voltage. Either you're running hot or you're losing voltage on one of the rails.


_________________

Looking for Mrs Sippi


#4 enkay85

enkay85
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:49 PM

Posted 13 July 2017 - 11:32 PM

The first thing I would do is turn off fast startup and reboot. 

 

Look in Event Viewer for any possible clues on the freezeups. 

 

You mentioned testing the RAM and CPU. Have you tested your hard drive? If not run Seatools for Windows doing the short and long generic tests. If your drive is WD then use the WD datalifeguard diagnostic.

 

If everything passes look at running sfc /scannow at a command prompt and DISM.

 

If you still have problems consider resetting Windows 10 with the option to keep your files or do a complete clean install using the Media Creation Tool to create a bootable USB or DVD. A clean reinstall is always the best option after upgrading from a previous OS. Because you have already activated Windows 10 the license is on Microsoft servers. When it asks for a key click next without entering anything.

 

Thanks for the suggestions. Tried them all (minus the clean reinstall) to no avail. HDD appears to be fine per WD diagnostic. 



#5 enkay85

enkay85
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:49 PM

Posted 13 July 2017 - 11:33 PM

This suggested one of two things to me, heat or voltage. Either you're running hot or you're losing voltage on one of the rails.

 

Temperature appears fine at 33-35C.  Any idea how to check voltage?



#6 enkay85

enkay85
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:49 PM

Posted 13 July 2017 - 11:40 PM

Just another quick update, may or may not be related but may be helpful.  I went to reboot just now, and while my PC did, I got this error in a window.

 

explorer.exe - Application Error

 

Instruction at 0x00007FF79743888F referenced memory at 0x000000000000038. Memory could not be read.

 

A poster above also mentioned checking the Event Viewer.  When I did there were several references to several programs as ! Error - but not sure what to make of any of it.



#7 MrSippi

MrSippi

  • Members
  • 83 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:05:49 PM

Posted 14 July 2017 - 06:09 AM

Run the Windows system file checker. You may want to check that the memory modules are seated fully in the slots. It seems to be memory problems which makes more sense now.


_________________

Looking for Mrs Sippi


#8 JohnC_21

JohnC_21

  • Members
  • 24,312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:49 PM

Posted 14 July 2017 - 07:13 AM

You said you ran a memory check. Use the free version of Memtest86 but let it run overnight.



#9 enkay85

enkay85
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:49 PM

Posted 14 July 2017 - 04:04 PM

You said you ran a memory check. Use the free version of Memtest86 but let it run overnight.

 

The memory check I ran was the one that came with  Windows 10 and came up clean. Do you recommend I still run Memtest86?



#10 enkay85

enkay85
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:49 PM

Posted 14 July 2017 - 04:09 PM

Interesting development - sfc /scannow found corrupt files but couldn't fix all of them.  The log file is very lengthy so I won't copy and paste it all here.



#11 MrSippi

MrSippi

  • Members
  • 83 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:05:49 PM

Posted 14 July 2017 - 04:11 PM

Then your system files got corrupted by memory problems. You may have to replace the memory and reinstall your OS.


_________________

Looking for Mrs Sippi


#12 JohnC_21

JohnC_21

  • Members
  • 24,312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:49 PM

Posted 14 July 2017 - 04:23 PM

In my post #2 check the DISM link and run it. Then run sfc /scannow again. I don't have enough experience checking sfc logs but after running DISM and then sfc scannow type the following in a command prompt to reduce the size of the log. 

 

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users