Disappeared desktop/metro

[topgundcp]

@Jeffrys

Had once the exact same issue, meaning no Metro, no desktop (everything black).
But if you go into task manager you should be able to see explorer and you can activate this. If not your explorer is corrupted.

That exactly what happened. Explorer is responsible to create the file for the Start Screen and we did exactly that by opening command prompt to restart explorer but it did not work.

i am not so keen on MEMTEST. When i had hang-ups, computer went to the store and they did not find the problem. Running MEMTEST for 72 or so hours. After a week i got my pc back, same problem.

Windows 8 also has a built in Memory Diagnostic and it is worse than Memtest86+. Until we can find another tool for memory diagnostic, Memtest86+ is still one of the best, besides they recently updated to new version.

@EasyQ
Even though your PC is back to normal but I still suggest you to run memory diagnostic. Don't rely on what was good 2 months ago will be good today. As you probably know, processes or apps are loaded and run from RAM so if your RAM has some bad spots and are not used then everything is cool but if those spots get used then corruption might occur again.
Also, even you have a new hard disk, it does not mean it is all good. Just my 2 cents.
Cheers.

 

[easyq]

I ran men test last night to be sure but no errors

 

[easyq]

One last question guys, where the heck are all my local roaming files in e windows 8 located, unable to find them on the regular spot

 

[easyq]

Omg,.just wanted to start a movie and again the bloody windows crashes on me restarts and the who'll mess begon again, wtf is wrong here?????????????? Just got everything setup again, why why why.
Again kernel errors and countless restarts

 

[easyq]

I start searching for my windows 7 copy, can't take this any more

 

[easyq]

Ok now it booted correctly but after starting any program it crashes, reboots, repairs and the circle stats again. Does anybody know a good checking program out verifier or anything like that to check this?
OK i downloaded sdk and wdk hoping to solve this issue.
After 10 reboots (could be more, lost count) and installing even more updates i managed to finally boor from the CD and ran chkdsk /f /r which repaired a lot of things. After that and 2 reboots it now seems to be working, but i'm carefull saying that because i said it before and it seems like saying that makes it crash.
Anyway, i will see how it will go from here and keep you guys updated on this ongoing drama called windows 8

 

[topgundcp]

run sfc /scannow to make sure everything is clean then make an image backup right away.

 

[easyq]

Update, still running.......

 

[jeffrys]

Easy,

did you remove a memory stick?

Jeff

 

[topgundcp]

Easy,

did you remove a memory stick?

Jeff

Jeffreys,
His problem might be geared toward his HDD. All of his problem started when he shrink the HDD and everything went Kaput which shouldn't happen in the first place. Last thing he did was running chkdsk /r /f.
/f fixed any errors on HDD
/r marked all the bad spots in the master file table so windows will avoid using them.

 

[easyq]

No memory sticks removed and everything seems to work fine so far.
Only 1 issue remaining, no sound. according to windows there are no speakers attached or connected while the lime minijack is connected as it has always been, no changes made. Before everything crashed there was sound.
To be sure updated drivers, everything indicates the soundcard is installed correctly.

 

[easyq]

Jeffreys,
His problem might be geared toward his HDD. All of his problem started when he shrink the HDD and everything went Kaput which shouldn't happen in the first place. Last thing he did was running chkdsk /r /f.
/f fixed any errors on HDD
/r marked all the bad spots in the master file table so windows will avoid using them.

I think this might be good point, i now make regular backups.

 

[easyq]

I an losing my mind on the PC, again a gazillion restarts. It worked fine since the last post until today. Nothing changed on hardware. No possibility to get anywhere, just restarts, gathering data because something went wrong and it restarts again. Booting from CD is possible but unable to get into anything due to ntoskrnl.exe error. I'm losing my mind guys, please help me..........

 

[jeffrys]

Well Topgun,

you are right this should not happen, BUT.... i had the same experience.....using a third party disk shrinker.

This should not happen when using MS to do so.

One time in disk management MS refused to shrink the disk, so i used another program. After that nothing but problems.

So now i never ever use another program to shrink the disk.

So Easy, dit you use a 3d party program?

Jeff

 

[easyq]

I used easeus partition, never had problems with that before windows 8

 

[easyq]

OK attached last minidump file i could retrace.
again the metro is completely disappeared, tries all options found but again nothing seems to work.
Renamed the last 2 .dmp files to .txt and uploaded them, hopefully you can help me out here what is wrong.

lso managed to open the memory.dmp file:


Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available


Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Windows 8 Kernel Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16461.x86fre.win8_gdr.121119-1606
Machine Name:
Kernel base = 0x81609000 PsLoadedModuleList = 0x817f4e68
Debug session time: Fri Feb 8 21:09:19.630 2013 (UTC + 1:00)
System Uptime: 0 days 0:00:28.356
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
..........
Loading unloaded module list
.......*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 8E, {c0000005, 97aed507, 97767bc4, 0}


*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware ( win32k!EngCTGetCurrentGamma+1a2d )


Followup: MachineOwner
---------

 

[easyq]

Result of !analyze -V:
!analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 97aed507, The address that the exception occurred at
Arg3: 97767bc4, Trap Frame
Arg4: 00000000


Debugging Details:
------------------




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
(english translation: The instruction at 0x%08lx refers to memory at 0x%08lx. A read or write error on memory occured)
FAULTING_IP:
win32k!ProcessDeviceChanges+a3
97aed507 0000 add byte ptr [eax],al


TRAP_FRAME: 97767bc4 -- (.trap 0xffffffff97767bc4)
ErrCode = 00000002
eax=00000000 ebx=9ba51510 ecx=ed4d904e edx=8457c8fc esi=00000000 edi=00000000
eip=97aed507 esp=97767c38 ebp=97767c84 iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
win32k!ProcessDeviceChanges+0xa3:
97aed507 0000 add byte ptr [eax],al ds:0023:00000000=??
Resetting default scope


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


BUGCHECK_STR: AV


PROCESS_NAME: csrss.exe


CURRENT_IRQL: 0


MISALIGNED_IP:
win32k!ProcessDeviceChanges+a3
97aed507 0000 add byte ptr [eax],al


LAST_CONTROL_TRANSFER: from 8177d5ed to 816eb76c


STACK_TEXT:
97767724 8177d5ed 0000008e c0000005 97aed507 nt!KeBugCheckEx
97767b54 8176106a 97767b70 00000000 97767bc4 nt! ?? ::FNODOBFM::`string'+0x15174
97767bbc 8176101f 97767c84 97aed507 badb0d00 nt!CommonDispatchException+0x4a
97767bd8 816441d9 00000000 00000002 969c8500 nt!Kei386EoiHelper+0x153
97767c84 97af75b1 00000000 7a3bec8a 97d0eaf4 nt!ExAcquireResourceExclusiveLite+0xfb
97767cc4 97ba9ca3 00000002 869561b8 97aed464 win32k!xxxDesktopThreadWaiter+0x125
97767d10 97bab1b0 00000004 969c8500 97d0eaf4 win32k!xxxDesktopThread+0x17d
97767d28 97b75afd 00000004 0086f988 97b75952 win32k!xxxCreateSystemThreads+0x55
97767d48 8176033c 00000004 0086f9cc 77036954 win32k!NtUserCallNoParam+0x1ab
97767d48 77036954 00000004 0086f9cc 77036954 nt!KiFastCallEntry+0x12c
0086f978 74691935 74691f83 00000004 00000000 ntdll!KiFastSystemCallRet
0086f97c 74691f83 00000004 00000000 770a810c winsrv!NtUserCallNoParam+0xa
0086f988 770a810c 00000000 9dc43524 00000000 winsrv!StartCreateSystemThreads+0x12
0086f9cc 7705689d ffffffff 770e5aea 00000000 ntdll!__RtlUserThreadStart+0x51
0086f9dc 00000000 74691f71 00000000 00000000 ntdll!_RtlUserThreadStart+0x1c




STACK_COMMAND: kb


FOLLOWUP_IP:
win32k!ProcessDeviceChanges+a3
97aed507 0000 add byte ptr [eax],al


SYMBOL_STACK_INDEX: 0


SYMBOL_NAME: win32k!ProcessDeviceChanges+a3


FOLLOWUP_NAME: MachineOwner


IMAGE_NAME: hardware


DEBUG_FLR_IMAGE_TIMESTAMP: 0


MODULE_NAME: hardware


FAILURE_BUCKET_ID: IP_MISALIGNED


BUCKET_ID: IP_MISALIGNED


Followup: MachineOwner
---------

 

[sl2222]

my money is on a hardware problem. If u have a spare hdd around try a clean install on it with no other drive installed and test that out for a day or 2. if u have the same problems then i'd look at the MB.
U said the memory has tested out well right?

 

[easyq]

Mem test gave no errors but I do start to suspect the DDR by now. I have 3 data hdd of which 2 are less than 1 year old. I also have some extra DDR modules but they don't work at all. I think I will buy some new modules and as you suggested disconnect the extra drives.

To be on the safe side I will simply rebuilt and clean the case as well

 

[sl2222]

if u have more than 1 memory chip u can test it out without buying any. just use 1 chip at a time and see if it fixes it.
oh, and i had a gigabyte mb one time that had 1 bad memory slot. I was getting intermittent errors and it took me a long time to figure that one out. The chip was fine but the slot was bad.