Win10 issues...

[Fuzz_Ball]

I put my system to sleep, before I go to bed. When I wake it up, I check the Event viewer. I keep seeing a Event ID: 137 "the system firmware has changed the processor's memory type range registers (MTRRs) across the sleep state transition (s4) This can result in reduce resume performance." Around the time I put it in sleep. I thought it was Windows being weird. Now after four hours of waking my system up, I installed minesweaper. 20 mintues after the installation was done, programs starting to crash with out reason (Skype, Adobe, AVG, Steam, ect...) I restarted Skype and that only lasted about 20 seconds. (Event Id( 7031 and 7034). I did a restart and everything seem to be working, but kind of worried and scared it might do it again.. The program dying part that is..

[Fuzz_Ball]

Or was it AVG since a program called: "wtusystemsupport" was the first program to crap out, before others did...

[Fuzz_Ball]

Or is there an issue with my memory? Wouldn't mind some idea or some solution to make sure either or both of these errors won't happen again...

[Lotte]

I suppose you can run an anti-virus scan and an anti-malware scan. If nothing turns up, then I suppose you can turn off CPU sleep states.

Sorry I can't be much help.

[Fuzz_Ball]

47 minutes ago, Lotte said:

I suppose you can run an anti-virus scan and an anti-malware scan. If nothing turns up, then I suppose you can turn off CPU sleep states.

Sorry I can't be much help.

I kno there is no virus on there, since it is more or less a clean install (Win 10 was installed on 1/26)... The Event ID 137, seems to be normal... It is what I'm gathering.

 

(for the programs crashing randomly) My only two guesses: either windows or AVG spazzed out and started to kill some programs with out any reason, or a RAM/Memory issue... I really hope it is the first one, since this is the first time over the three weeks I been using Win10 on my machine (the programs randomly crashing with out a Windows's message box.)

[Lotte]

So you're telling me, that you know without a doubt, that there is no need to scan for any kind of malware. Also saying that Event ID 137, in which a computer may fail to wake up from sleep, seems 'normal'. With the latter Event ID's being put on by being either a Windows issue or an Anti-Virus issue...

 

I'll assume you upgraded to Windows 10, just be a brute about it and do a fresh install.

[Fuzz_Ball]

12 hours ago, Lotte said:

So you're telling me, that you know without a doubt, that there is no need to scan for any kind of malware. Also saying that Event ID 137, in which a computer may fail to wake up from sleep, seems 'normal'. With the latter Event ID's being put on by being either a Windows issue or an Anti-Virus issue...

 

I'll assume you upgraded to Windows 10, just be a brute about it and do a fresh install.

 

I'm just saying what I read on that ID 137. I looked it up and saw many other people had that ID, from all the way back to Win7 and Win8.. (2013 ish). I looked though and there was no real answers to fix the error...

 

I just did a clean install since I also upgraded from a five year old HDD to an SSD, since I don't want to do the clone.

[Fuzz_Ball]

I tried different things to fix that Event ID 137, but found another thing that started back on the Feb: 4. Event ID: 1001, regarding memory. Windows Memory Test came up with nothing, as I'm posting this... MemTest shows over 1000 errors with an Addr that starts of 6 and 7.

[alex_read]

If you're getting even more than just 1 memory error on memtest, I'd look at re-seating, possibly then even replacing the RAM. Try a single stick at a time in order to weed out the dodgy stick(s).

 

Overclocking and BIOS came to my mind initially too, though I'm not sure if it'll make a difference another thing you might try is to boot into the BIOS/UEFI and see if there's any reset default setting options perhaps?