Community Question: CPU Processor type?

Started by erdrik, January 11, 2017, 11:18:13 PM

Previous topic - Next topic

mcal9909

I have the same CPU as op, along with a 750ti (2gb)  and 8gb dd3. Audio handled by the gfx card via hdmi and some cheep motherboard i cant remember. I have no crash or audio issues.

Seeker89

I'm going to ask a simple question. have you checked to see if you need to update your bois? you should check your drives and see what needs to be updated.

erdrik

#17
First sorry for the delay in response, Ive been focused on other work.
Secondly, Ill start by saying I never really thought Rimworld was the culprit.
Just that up until the last freeze it had happened twice in Rimworld and was wondering if maybe there was something about Rimworld that might trigger it more often.

That said the last freeze happened while watching youtube, so ... like I said, I doubt Rimworld is the culprit.

@dv
I checked the System Logs, because that is what milon suggested.
If it happens again Ill check Application and Forwarded Events, I doubt Security or Setup is going to be related.

@loc978
Aside from Overwatch, I haven't been playing many games. If any others at all.
I don't know which games I own that are built by Unity. Id have to check, but I have only been running Rimworld, Overwatch and:
Mostly been editing in the StarCraft2 Editor, and learning the UE4 Editor/C++ Visual Studio via project development.

The SC2 editor is usually active for 2 or 3 days straight, and can get a bit unstable after too long. And testing that involves constantly hopping into and out of SC2.

But for the UE4, Ive had the UE4 Editor and Visual Studio Community running simultaneously for months at a time(mostly non stop).
During which I would hop into and out of anywhere between 1 to 3 instances of the project when needing to test things.
That setup has RAM usage between 6 to 11~ gigs. (I have 16)

I have stress tested the system when it was first built with the evaluation version of Passmark's PerformanceTest software. I was unable to save the results due to it being an expired evaluation copy, but I recall it passed fine.

As for how windows was installed and what drivers, Id have to ask the builder.
I decided to go with a friend for the build this time(because they own a computer store, and they're an enthusiast) so Im not 100% on that. I do know, one of the hardrives, the CPU, the Motherboard, the Power Supply, and the Graphics card are all new. The other hardrive, and the RAM are not.

@RolanDecoy
Admit-ably I did not check all the drivers as I had figured that was done by the builder.
I did, however, do so for the graphics card, mostly out of habit because my experience with old or too new Graphics card drivers is that they can be "finicky".

@skullywag
The graphics card has 4GB.
Infact, Im going to post the system as listed by Performance Test.

Motherboard: ASUSTek, M5A97 LE R2.0
BIOS: ASUS UEFI BIOS UTILITY (vrs: 2601, Date: 2015-03-24)
CPU: AMD FX-6350 Six-Core
RAM: 16GB (4 cards, DDR3 SDRAM PC3 12800 Corsair)
Drives:
PQI 128GB SSD SATA (OS drive)
WDC 1863GB SATA
Graphic Card: ASUS Radeon RX 480 (Driver vrs:16.200.1028)


Im going to go ahead and run the performance tests again.
And I'll check the bios version, then post that info.

EDIT:
Passmark actually gave me the bios version and "release date", but was vague about anything else.
American Megatrends, Inc - vrs: 2601, Date: 2015-03-24

Here is a link to the uploaded baseline

Im going to take a closer look at the bios now.

EDIT2:
Well Aside from the BIOS name rebooting into the BIOS didn't tell me anything PerformanceTest didn't already tell me. lol
ASUS UEFI BIOS UTILITY.
vrs: 2601, Date: 2015-03-24

erdrik

Just finished MemTest86, after a 20+hour run:
4 passes no errors. Im pretty sure its not my ram, but I might run it again without the Hammer Tests.
After reading around it seems DDR3 isnt so great at those, and after watching the first two passes it looked like the VAST majority of the time spent during testing was on the Hammer Tests.(Hence why there are only 4 passes)

Alenerel

I emphasize the drivers thing since it seems that you havent checked them and leaving it do the builder isnt the best idea. You can check Driver Booster, which works pretty good and its free, will isntall all your drivers.

Also I recommend always manually checking the graphics card drivers, even with Driver Booster, so go there and download them first, the run Driver Booster.

Radeon drivers:
http://support.amd.com/en-us/download

Driver Booster:
http://www.iobit.com/en/driver-booster.php

erdrik

#20
Quote from: Alenerel on January 23, 2017, 07:27:03 PM
Driver Booster:
http://www.iobit.com/en/driver-booster.php

How does Driver Booster determine if a driver is outdated?
I ask because it is saying my audio driver is out of date because it claims it is 4 months older that what it found as "available", but the driver version numbers are exactly the same.

EDIT:
Happened again while I slept.

I went to bed at around 6:00 AM 1/24/2017
The reboot I initiated after discovering the froze system started at 12:21 PM 1/24/2017

Application logs stop before the reboot at 6:02 AM 1/24/2017

  • VSS 1/24/2017 6:02:29 AM 8224 The VSS service is shutting down due to idle timeout.
  • SideBySide 1/24/2017 5:52:48 AM 33 Activation context generation failed for "C:\Program Files\AMD\CIM\Bin64\SetACL64.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

There are 2 Security logs before the reboot at 9:54 AM 1/24/2017,
Before that Security logs stop at 5:59 AM 1/24/2017
All the same two logs.


  • Microsoft-Windows-Security-Auditing 1/24/2017 4672 Special privileges assigned to new logon. x4
  • Microsoft-Windows-Security-Auditing 1/24/2017 4624 An account was successfully logged on. x4

Last Setup log is 11/21/2016

System logs stop before the reboot at 10:10 AM 1/24/2017

  • Service Control Manager 1/24/2017 10:10:01 AM 7036 The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped state.
  • Service Control Manager 1/24/2017 10:04:47 AM 7036 The Windows Modules Installer service entered the stopped state.
  • Service Control Manager 1/24/2017 10:04:47 AM 7040 The start type of the Windows Modules Installer service was changed from auto start to demand start.
  • Service Control Manager 1/24/2017 10:04:46 AM 7040 The start type of the Windows Modules Installer service was changed from demand start to auto start.
  • Service Control Manager 1/24/2017 9:54:28 AM 7036 The Windows Modules Installer service entered the running state.
  • Service Control Manager 1/24/2017 9:38:42 AM 7036 The Google Update Service (gupdate) service entered the stopped state.
  • Service Control Manager 1/24/2017 9:38:31 AM 7036 The WinHTTP Web Proxy Auto-Discovery Service service entered the running state.
  • Service Control Manager 1/24/2017 9:38:31 AM 7036 The Google Update Service (gupdate) service entered the running state.

There are no Forwarded Events

Before going to bed I had installed updated drivers for my graphics card.
The install process was started around 5:00 AM.

loc978

#21
I'm hardly on the level of someone who builds systems for a living (I build maybe 3-4 a year, mostly for friends), but this does sound a bit like one of those cases of trying to leave an old Windows installation intact with new hardware. Old drivers for major system components rarely uninstall cleanly (and they change things in all sorts of deeply tiered file systems from the registry to hidden Windows and User directories), so a good rule of thumb is "new motherboard, new operating system". May want to find out if there was a clean OS install involved and if not, perform one.

Aside from that... The random and low-usage nature of the crashes seems to rule out heat issues. Have you tested your old hard drive for possible failures? Even something as simple as HWinfo can tell you if a drive is self-reporting, where base operating systems will almost never inform you. Usually if that's the case, you'll also notice odd, temporary unexplainable performance lag and long load/boot times.

Hope you can get this sorted out. Unreliable performance with new hardware really sucks.

erdrik

HWInfo says "no" for both warning and failure for the old drive.
New drive is reporting "yes" for warning "no" for failure.
Warnings are:
Reallocate Sector Count - 57
Current Pending Sector Count - 119
Off-line Uncorrectable Sector Count - 41

The last self monitoring Message for that drive is a "Raw Read Error Rate: 200/51, worst 200".
Its got a green check mark instead of a caution icon, so Im assuming its not too bad.

But I don't know what any of that means, or if those numbers are considered too high.  :-\

Unfortunately I won't be able to talk with the builder about the OS for a while.
Ill ask when he gets back.



Alenerel

It sounds like it might be your HDD. As loc978 said I recommend you to format Windows if you didnt after getting the new parts, tho this wont directly solve the problem it might prevent other headaches.

To check the HDD open a command prompt: windows key + R > type "cmd" > type "chkdsk c: /f"
I also recommend you to run additional chkdsk for each partition in your HDD. If you have for example a partition D: run also "chkdsk d: /f"

It will ask you if you want to check the disk after restart. Say yes and restart manually.

Tell us how did it go, Im curious.

Grax

Quote from: erdrik on January 29, 2017, 04:49:44 AM
Reallocate Sector Count - 57
Current Pending Sector Count - 119
Off-line Uncorrectable Sector Count - 41
\\\
But I don't know what any of that means, or if those numbers are considered too high.  :-\
Reallocated sector count must be zero on a healthy drive. If it's increasing - you've got a problem and your HDD soon be dead.

erdrik

@Alenerel:
I ran chkdsk, but it just immediately started up windows after it was done.
Does it drop a log file with the results somewhere?

@Grax
It hasn't increased so far.
Ill keep an eye on it.

harpo99999

erdik, chkdsk does NOT reallocate or alter the pending sector counts from the drive firmware, it only checks(and if told to in the command line, fixes) errors in the folder and file locations and flags,
the ONLY way to clear those two values is to do a LOW LEVEL FORMAT of the drive (but this will destroy ALL information on the drive), the best 'fix' for the problem IS to obtain a NEW hdd of the same or larger capacity in the same form factor, then use a hdd cloning tool to copy all the information from the old(sick) drive to the new drive OR do a fresh install of the os and all drivers/programs that are wanted

erdrik

Quote from: harpo99999 on January 30, 2017, 03:30:00 PM
erdik, chkdsk does NOT reallocate or alter the pending sector counts from the drive firmware, it only checks(and if told to in the command line, fixes) errors in the folder and file locations and flags,
the ONLY way to clear those two values is to do a LOW LEVEL FORMAT of the drive (but this will destroy ALL information on the drive), the best 'fix' for the problem IS to obtain a NEW hdd of the same or larger capacity in the same form factor, then use a hdd cloning tool to copy all the information from the old(sick) drive to the new drive OR do a fresh install of the os and all drivers/programs that are wanted

I wasn't trying to reallocate or alter anything yet.
I just did the chkdsk to get a report or log on the situation as was suggested to me.

But it just flashed that info on the screen and then immediately booted up windows.
Does it drop a log file with the results somewhere?

harpo99999

the only ways that I have seen a report from chkdsk is
1 boot to dos mode, then  run chkdsk or
2 run chkdsk in drive properties without the fix
but chkdsk does NOT do the lower level testing on the drive, it is only the higher(within the formatted partition) checking (and fixing) of the folder and file allocation spaces and flags on them

Thirite

Like someone said on the first page, this is caused by a memory leak. It's not a hardware issue. I've had it happen three times and if I catch it and kill the rimworld process before it eats all my ram I can restart rimworld without even logging out and back in.