Disappeared desktop/metro

[Dave76]

Good advice given so far, very good.
Just read through the entire thread, was thinking hardware problem from the beginning.
Would like to 'agree' with a few things mentioned already;
1. New hardware can fail.
2. Just because hardware passes a test doesn't mean it's good. Just the way electronics are.
3. At some point you need to test hardware by removing/replacing it.
4. Assuming you have two RAM cards, remove one and see if your system is stable, if not stable then change out the RAM card for the other one in a different slot.
5. Remove the OS HDD, install your OS on another HDD.
6. Remove all devices that are not absolutely required to run your system, ie run bare bones.

The two biggest hardware failures are RAM and PSU.
What PSU do you have?

If you haven't already, check your motherboard for a ground fault, this may require removing the motherboard from the case.
What version of EasyUS did you use? Older versions are not compatible with W8. When re-sizing a partition the program will make a copy, re-size the partition, re-store the copy. If it's not compatible it can result in errors.

Another thought, strange issues like this have been solved by changing the mouse and/or keyboard, if either one is faulty they can and will throw a massive amount of errors, seemingly not possible from these devices. It's worth checking if the usual steps aren't working.


The files you uploaded in post#56 are not usable.
If you upload the BSoD crash report files, I'll analyze them and see if anything else is indicated.
Can you upload the entire BSOD Posting Instructions files, these will help us analyze your crash.

If you can't access through the above program, look in 'C: Windows > Minidump' for the dump files. Copy the files, zip all of them and attach them here.

If you have access to the OS make sure the dump settings are set to small memory dump (Minidump).
Dump Files - Configure Windows to Create on BSOD
Follow steps 1-4 then '6. To have Windows Create a small memory dump (Minidump) File on BSOD', then go to 9&10.

From your previous post:
General possible causes, this is a fairly generic stop code.

STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory 
0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation occurred.
PROCESS_NAME: csrss.exe
.

The Microsoft Client Server Runtime Server subsystem utilizes the process csrss.exe for managing the majority of the graphical instruction sets under the Microsoft Windows operating system. As such Csrss.exe provides the critical functions of the operating system, and its termination can result in the Blue Screen of Death being displayed.
Csrss.exe controls threading and Win32 console window features. Threading is where the application splits itself into multiple simultaneous running tasks. Threads supported by csrss.exe are different from processes in that threads are commonly contained within the process, with various threads sharing resources within the same process. The Win32 console is the plain text window in the Windows API system (programs can use the console without the need for image display).
In mobile devices such as notebooks and laptops, the process csrss.exe is closely dependent on power management schemes implemented by the system as defined under the Control Panel option.

csrss.exe is probably the result of the crash and not the cause, when Windows crashes it tries to find the cause, if it can't then it will list the last process that was running in the faulting string. This is very common in hardware faults.

The stack trace is showing faults from the beginning, this is usually due to hardware, in this case likely RAM or HDD.

How much free space do you have in your OS partition?

 

[easyq]

Thanks for all the help so far.
PSU = 550watt Sweex unit

Steps taken so far:
-i upgraded from windows 7 ulitmate to 8 pro, when on windows 7 it rans flawless. All this began when switched to windows 8
this is why i am not so confident about a hardware issue, however, ofcourse it can be.
-Keboard and mouse not changed
-The HDD containing windows is 1TB divided into 2 partitins (almost equal, so space should not be an issue)
-Last time i fixed windows 8 by a factory reset on an empty partition but i don't want to do this again as i would loose a lot of e-mail traffic.
-i cannot perform a clean install as i got my code via e-mail which is lost due to the failing os.
-i tried to retreive the code via keyfinders but all codes found are incorrect.
-i do have access to the os but it is very limited. Not all software will/can run, most give me the message interface not registered.
-i cannot upload dump files because i cannot zip them due to this same error
i ran the dumpfiles software but it cannot start due to unable to use activeX

Zie het einde van dit bericht voor meer informatie over het aanroepen
van JIT-foutopsporing (Just In Time) in plaats van dit dialoogvenster.

************** Tekst van uitzondering **************
System.Exception: Kan ActiveX-onderdeel niet maken.
bij Microsoft.VisualBasic.Interaction.CreateObject(String ProgId, String ServerName)
bij SF_Diagnostic_Tool.Form1.Button1_Click(Object sender, EventArgs e)
bij System.Windows.Forms.Control.OnClick(EventArgs e)
bij System.Windows.Forms.Button.OnClick(EventArgs e)
bij System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bij System.Windows.Forms.Control.WndProc(Message& m)
bij System.Windows.Forms.ButtonBase.WndProc(Message& m)
bij System.Windows.Forms.Button.WndProc(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladen assembly's **************
mscorlib
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.6400 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SF Diagnostic Tool
Assembly-versie: 5.0.0.6
Win32-versie: 5.0.0.6
CodeBase: file:///C:/Users/Ed/Downloads/SF_Diagnostic_Tool.exe
----------------------------------------
Microsoft.VisualBasic
Assembly-versie: 8.0.0.0
Win32-versie: 8.0.50727.6387 (Win8RTM.050727-6300)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.6401 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.6401 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.6401 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.6387 (Win8RTM.050727-6300)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
mscorlib.resources
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.6400 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Microsoft.VisualBasic.resources
Assembly-versie: 8.0.0.0
Win32-versie: 8.0.50727.6387 (Win8RTM.050727-6300)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/8.0.0.0_nl_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll
----------------------------------------
System.Windows.Forms.resources
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.6400 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_nl_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------

************** JIT-foutopsporing **************
Als u JIT-foutopsporing wilt inschakelen, moet in het configuratiebestand voor deze
toepassing of computer (machine.config) de waarde
jitDebugging in het gedeelte system.windows.forms zijn ingesteld.
De toepassing moet ook zijn gecompileerd terwijl foutopsporing
was ingeschakeld.




Bijvoorbeeld:


<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>


Wanneer JIT-foutopsporing is ingeschakeld, worden onverwerkte uitzonderingen
naar het JIT-foutopsporingsprogramma gestuurd dat op de computer is geregistreerd
en worden niet door dit dialoogvenster verwerkt.


-if i boot from the CD and run auto-repair it seems to work but after going to 100% it tells me it failed.
- i ran over 20 sessions scf /offbootdir=c:\ /offwindir=c:\windows from the elevated dos when booted from the cd, each time it finds errors but is unable to fix all.
-it makes no difference if i login with a MS account or local account
- i have disconnected all other HDD and besides the graphics card and a networkcard there nothing else built in
Windows 8 did run smooth for about 2 weeks before it did this again. no changes were made to the pc, no new software was installed.

 

[easyq]

And while trying to set windows to a minidump i get the error message:
Volume Shadow Copy Service used by system recovery is not working, code 0x81000202
So i tried to start it manually via services .msc but i got this error: -2147212542.
No wonder it cannot auto-restore if that service never started up ( i guess)
Only thing is why is this all happening?
now running on only 2GB of RAM as meanwhile i removed 1 ddr module but no effect yet.

 

[Dave76]

Can you get the dump files off of the problem computer, like copy to a USB memory stick, then post them here with another computer?

This will work for W8 also: How to Create a Live Peppermint3 CD/DVD/USB to Backup Data When Windows 7 Will Not Boot

When you get the OS working again and then in a short time it fails again leads me to think it's a hardware error.
Another possibility is a corrupt download/burn of the W8 ISO file, unless you got a DVD from MS.

Never heard of a Sweex PSU, search didn't come up with much either. Their website doesn't have a 550w listed for current models or end of life models.
How old is it?
After reading just a couple references to Sweex, I would replace the PSU with a quality unit weather it fixes your issues or not.

 

[easyq]

I could be mistaken in the Watts, I thought it was 550 but it could be 450 too. DVD is official download from Ms. I will try to see if I can get a dump file to USB to upload it.

 

[easyq]

OK, i managed to get dump files on a usb and zip them. attached all dumps i could find but all are dated 08-02-2013, the date before the sh!t happened. No logs were made since unfortunately but hopefully this will help to find the solution to this sick error.

 

[Dave76]

No files attached.

How to Upload and Post a Screenshot and File in Eight Forums

Use OPTION TWO: To Upload and Attach ANY File into a Post

 

[easyq]

Ok I'll give it a go later on, don't know what went wrong

 

[easyq]

attached the dumps found, last post i was too fast in posting and they weren't uploaded yet, sorry
Memory.dmp itself is zipped still too big to upload.

 

[Dave76]

There are a lot of failed Windows updates in the CBS log, this may be caused by virus or memory issue.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
Probably caused by : CI.dll ( CI!MFKeyIsTrustedRootKey+2e6ae )
WARNING: Unable to verify timestamp for peauth.sys - Windows driver - Protected Environment Authentication and Authorization Export Driver. Probably the result and not the cause of the crash.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
Unable to read MiSystemVaType memory at 82040080

With CI.dll indicated you need to run TDSSKiller.
How to remove malware belonging to the family Rootkit.Win32.TDSS

When this has completed run a SFC scan again, minimum three times if it finds errors.

Then test the hard drive.
Run Seagate SeaTools for DOS, you can run this without your OS working. Seatools for DOS tutorial
SeaTools for DOS is a comprehensive, easy-to-use diagnostic tool that helps you quickly determine what is preventing you from accessing data on your desktop or notebook computer.
SeaTools for DOS

If your still having issues, remove all but one RAM card, test for stability. If not stable then take the RAM card out and put in another one, test.

Still a possible PSU issue, if you have one or can borrow one to test with, you can rule this out.
You should consider this weather it's the cause or not.

 

[easyq]

Wauw, thanks, always used windows defender and uninstalled avast since i upgraded to windows 8 because it's known for giving problems. Too bad apparently i still somethign dirty somehow. Anyway, with just the OS HDD attached the kapersky found nothing, the Seagate tool is going to run a bit later but i have to do it from dos as windows 8 doesnot install it due to compatibility issues and the compatibility doesnot work. Will post the results later and will reconsider updating the PSU.
Will also connect all HDD's to be scanned by both programs, hopefully a solution will appear.

 

[easyq]

The tdsskiller didn't find anything, ran 6 scans with, the Seagate checker doesn't function under windows nor under DOS. I reconnected an old hdd which contained windows 7 installed and will try again. Also I will make a image p of this hdd to my newer one to see what will happen. PC has been on 1 ram stick for sometime now but now I can check properly if the ram is the issue. I am so lost on this that is my last resort to try.

 

[Dave76]

Good news about the virus scans.
Anti Virus programs are always a subjective discussion, I use Avast on W8 with no problems, have seen very few problems caused by it. Some members, including me, recommend to remove non-native AVs and install MSE or Defender while troubleshooting.

When you did a factory reset and it ran stable for a while, then started having issues again leads me to think it's a hardware issue. Slight possibility that one of the programs you install may be causing problems.

If Seatools won't run, that is indicating a problem.
Does the CD/DVD/USB stick run Seatools on a different computer?
Need to confirm the download is not corrupt or the burn/install on CD/DVD/USB stick is not corrupt.
If it works on another computer but won't even run on yours, indicates a hardware problem. Could be faulty HDD, RAM issue (it uses RAM to run), even PSU issue.

If you can't get anywhere with this type of testing, you may want to consider testing with new or known good components or a complete bench test.
Bench test is extreme in the fact that you remove everything from the computer case, with the motherboard on the bench attach the PSU, start system and note the beep codes. Then attach one component at a time noting the beep codes until the connected component doesn't produce the correct beep code sequence. This is extreme hardware testing but, usually will find the failing component.
The component that will still prove to be the hardest to isolate and confirm is, of coarse, the PSU.
Best way to test for a faulty PSU is to connect a known good PSU.
The one issue that may come up with this test, is if the faulty PSU has already damaged some of the other components. This is known to happen.

 

[easyq]

Today I bought a new psu , 460watt cooler master elite power. I also bought 8 GB of new ddr 3 modules, will built it in tonight.

 

[Dave76]

Good news, let us know how the upgrades are doing.

The only CoolerMaster Elite Power unit I can find in the PSU Review Database I use is a 450w.
RS-500-PSAP-J3, original manufacturer FSP, max 12v load 360w, Not Certified.
From other sources?
Efficiency > 70% Typical

I'm sure this one is better than the one you were using, but it's not very good specs.
I would get 450-500w deliverable power for your system.

 

[easyq]

Ok I have the box here, but its only suitable for EU, maybe that's the reason? Left the PC on all night doing several checks, cloned the old hdd and still running like a charm. But on windows 7. Tried to get windows 8, but the issue remains the same.

 

[easyq]

The box of the psu

 

[caperjack]

i read the whole thread ,and don't think i read once about making sure you install win8 device drivers from the manufacturers web site, after you installed win8 ,i know it doesn't sound like a driver issue but one never knows

 

[easyq]

Although it was indeed not mentioned, I did that in the efforts to solve all this. One thing is for sure, I will not switch to windows 8 for a while, this costed to much time and headaches. Now back on windows 7 and everything works like a charm. This feeds my doubts about a hardware failure but to be on the safe side I did by a psu and new memory. No hdd errors were found in windows 7.

 

[caperjack]

what ever the reason for you problem it is strange ,i have installed win8 on a few older systems now ,,including older laptops ,and except for driver issues i have never had anything close to the problems you have experienced ,currently running it on a 5 year old Dell ,with out any issues ,weird i think