Windows 8 not working right, at all

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815
Basically from day 1 it's been having issues. It keeps saying it never shut down properly. I use Settings > Power > Shut down. Well, if that's causing it to think it lost power how else are you supposed to shut down!!!?

Got 16 cases of Kernel-Power error even though I shut down correctly

Got BSOD (Memory_Management) when waking from sleep. No errors found by memory diagnostic (Although it never told me because the little window that's supposed to come up never came)

Got shadow copy failures

I know my hardware works fine, because all the problems starting when I installed 8 (except for when it emergency shutdown during a mobo update, because the CPU overheated, that was genuine), but Windows 8.1 is ruining my beast of a build!

How do I fix this, tired of it already, 3 weeks in
 
overheating issues? number one rule of any computer - it should run at any given time with any given task without hesitation or issue, if it does not ITS FAULTY

fix your heating issue
if its overclocked reset the overclock
test your hardware (ALL of it -- memtest furmark prime95 hdtune)

dont blame Windows 8 because of issues with your faulty/poorly built/configured rig
 

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815
I fixed the heating issue as soon as I found it, the CPU cooling fan was not plugged in fully or something and now temps are way down at 30 degrees and Windows 8 is still broken

In fact it's widely accepted that 8 sucks (question my choice of it now), but I was kind of liking it, but it's been broken since day 1

And if you're not going to help dude, stay out the thread
 

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815
Just thinking, could it be the Power adaptor it's plugged in to causing stability issues. Other devices have been plugged in to it and never had a problem, it's an 8 way

I did some more digging and found that it could be the hybrid shutdown causing the Event 41's. A number of times after shutdown I intend to work on my PC so I turn off at the PSU as well, but because 8 never fully shuts down, but is instead in hibernation then wouldn't that register as it lost power? There are some days where Event 41 does not occur.

Still stumped on the Memory Management error though
 

cyborgcity

Honorable
Jan 16, 2013
178
0
10,690
I keep getting the "sorry there was a problem needs to restart" page with the frown face. Windows won't let me install some updates now either. I have played with my RAM a little bit down volting it. I don't even think thats the problem though.
 
power cuts/overheating = file system corruptions = windows wont load

original windows disk in and boot from it, select the repair option (to run chkdsk etc)

again TEST YOUR HARDWARE it doesnt matter that you found one issue keep looking and check everything else
 

james_44

Honorable
Oct 9, 2012
49
0
10,540
Which RAM are you using? I was using a third party RAM for the longest time and it was getting memory related issues for the longest time. I replaced one of the two and it was back to working normally.

Try running WIN7 and see if you face the same issues. I moved back to win7 from win8.
 

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815
Corsair CML16GX3M2A1600C10 Vengeance Low Profile 16GB (2x8GB) DDR3 1600 Mhz CL10 XMP Performance Desktop Memory Kit Black

I nuked my drives and formatted everything to do a clean install of 8 (sfc/scannow found a corrupt file). Interestingly PowerDVD 12 reported one when I tried to install it after, but I put PowerDVD 19 back.

Could the error 41's be caused by Windows 8.1's hybrid shutdown. A lot of the time I want to work on the inside of the rig after shutdown so I switch the PSU off after shutdown, but because 8 I'd never truly off does that cause it to register as an error 41?
 

cyborgcity

Honorable
Jan 16, 2013
178
0
10,690


What sort of protection do or did you have running before you reformatted? Did you scan your system?
 


Third party ram? What are you talking about?

Nothing wrong with Windows 8, your suggesting something for no reason.
 

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815
Avast and Malware Bytes. They came back clean in scans and if Malware Bytes did find something I'd get it to clear it out.

I will say now though, during first boot when I put it together it emergency shutdown during a motherboard software update because the CPU got too hot (I thought the cooling fan was fully connected, but evidently it wasn't, my fault). And I do some registry editing to get rid of remnants of an uninstalled program (I only removed things related to that program), don't know if that could have caused the memory management error but the two events were several hours apart.

After formatting and reinstalling (after making this thread) just Windows, scannow came back with no integrity problems. PowerDVD 12 came later 10 was already installed and was on the motherboard disc) did it say corrupted file.

My computer was working fine over the three weeks but there was something not quite right. Reliability monitor was throwing up a tonne of errors and then you've got this memory management error which led to the formatting and reinstall
 

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


Were you able to get anywhere with this?

I don't want to tempt fate, but since the clean install everything is working properly, except that corrupt file (most likely created by PowerDVD) which I haven't scanned for again yet, but I assume it's there. No Google Chrome didn't shut down correctly, no Error 41, no BSODs, faster operation, so something had gone screwy somewhere in the software

I've figured PowerDVD 10 is in the Add/Remove programs thing. As it installed as part of a CyberLink Media Suite all the programs appear under one name. I have had one tiny issue though with my Xbox 360 adaptor malfunctioning, but that's minor

EDIT: sfc/scannow came back and no corrupted files!!! :D
EDIT: Spoke too soon, got another Windows was not properly shutdown :(
 

cyborgcity

Honorable
Jan 16, 2013
178
0
10,690


I deleted some download programs and removed some spyware from malware and some other infected files with avast etc. But I left the OS running all night with sleep/display turned off and woke up and it had restarted again taking me to the black boot screen... Did you play with the sleep/display settings much? Does it still do it if you lock it or put it to sleep etc.?

I just payed $150 for windows 8.1 from windows 7 and I really dont see why I should pay more money for an OS. Id like to fix it without reinstalling windows 8.1 again as well. Ive only had mine running for 3 days.

 

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


No, unless you're talking about the RAM test thing, but that seems kind of long to do_Other sources suggest is could be the fast boot feature causing an Event 41 to register. If my hardware was faulty would it not crash first, then cause an Event 41 rather than work 100% fine and trigger event 41 with no visual symptoms at all

I will look into testing my RAM though
 

cyborgcity

Honorable
Jan 16, 2013
178
0
10,690
Unplanned bacon are you still getting the crashes? I though I might of been progressing then yesterday I went to fire up BF4 to show my housemate my rig and being the best time of course boom, it crashed again :(
 

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815
A clean install and turning off fast start seems to have fixed all the issues (no error 41s, bugs, slow starts or blue screens, time will tell if the blue screen thing stays true). I've had no errors at all, no corrupted files apart from 1 out 2 buggy programs. Seems the crash during that motherboard update on day one may have been the root of the issue along with when acronis copied everything. If that memory management thing he queens again I will probably test my RAM.

As for the battlefield problem, maybe try reinstalling the game?
 

USAFRet

Titan
Moderator


So you built a new system, and cloned the OS from the old system? Presumably you have a new motherboard and CPU?
And a clean install fixed it?

Yes, this is very often what happens with the cloning process. You're lucky it even started the first time!