MarcSupilami

Sorry, I noticed that the link to the second Bug Check URL in my previous message was incorrect and I have corrected it. Have you had a chance to try the steps recommenced in that article (Sorry, I do not believe it exist in German). How is your memory configured? More than one module? Any chance to try running it with just 8GB and then with the other memory modules? Hardware issues often are a P.I.T.A and diagnostic software does not detect it every time. Switching components can often be the only way to figure out the faulty component.

Hmm, I would be cautious about suggesting disabling an Anti-Virus, even if I am not a fan of it. :( However, it is indeed likely a false positive: If you look at Norton's article on it, the alert was raised because of the component's behavior (you failed to indicate which file cause the alert), in particular its access to cloud data. If the file in question downloads/uploads data from the Internet, that likely would have cause the alert. As suggested in the article, submit the file to Symantec for analysis. In the future, please provide more details, such as the OS version, update status, software version (both DCS and Norton), etc... :smartass:

Sorry, wrong language, but I don't speak German and I am reading an automatic translation of your posts :(. Could you give some more details on the bug check you are encountering? Is it a 0x1A: MEMORY_MANAGEMENT, or 0x50: PAGE_FAULT_IN_NONPAGED_AREA, or both? Are there any more details, for example the component that forced the bug check? Check the Event Viewer (in particular the System log and the Administrative Events filter) for details. The Blue Screen troubleshooter might help, but I would suggest trying out the steps suggested in the second bug check. Also, despite running the memory checker, I would still suggest trying it out with different memory (for example, if you have enough memory, remove half of it, then the other half...). If you are running a third party anti-virus (in particular if it is not a recent version or not from one of the primary vendors), try running with it deactivated. Make sure you have the latest version of your BIOS (UEFI, I presume) This is unlikely to be easy to resolve, and will probably require a fair amount of trial and error. Still at this point, I would think we are dealing with a hardware issue :joystick:

The WinSxS (Windows side by side) was a response of Microsoft to a number of compatibility and distribution files storage issues. However, it can grow to multiple dozens of GB over time if not cleaned up. While Disk Cleanup was improved to allow some cleanup of it on Windows 7, on more recent OSes, the DISM Command with the /Cleanup-Image /StartComponentCleanup switches will do a better job. Also, since you are unlikely to revert an update, you can delete their downloaded files in %SystemRoot%\SoftwareDistribution\Download (It is recommended that you stop the Windows Update before doing this and restart it afterwards). Finally, temporary files are typically stored in %UserProfile%\AppData\Local\Temp. However Disk Cleanup will delete those that are over a week old IF YOU SELECTED TO DO SO!

Really good to read, it is only now that I became aware of your location. The community is behind you (if I may be presumptuous enough to speak for others...), take whatever time you need to get back on your feet and help your friends and families

1 - C 2 - B 3 - A & C 4 - A

Boot from VHDX If you want to try Windows 10 (indeed, it is not Windows X: This is not a X-Rated product like the Mac, after all :music_whistling:...just kidding fanbois!), I wanted to make sure that you were aware of the "Boot from VHD" that exist in recent Windows OS. Neowin has en explanation about it, but I find the simplest way is to boot from your Windows 10 install media, press Shift-F10 when you get to the disk selection screen (so that the proper keyboard is already selected) to open up a console and then use DiskPart to create the VHD: Type DiskPart to get into the partitioning tool Type Create VDisk File="C:\Windows 10.VHDX" Maximum=20484 Type=Expandable Type Select VDisk File="C:\Windows 10.VHDX" Type Attach VDisk Then return to the setup program (Alt-Tab) and hit refresh.Your new 20GB drive appears, select it as the installation destination. I have two such Windows 10 installs, although Microsoft is recommending to install directly on the hard drive (because we all have too much unused PCs lying around, I guess)

Cobra for president! +1. My F5 key is worn out (on all my computers...) but I did enjoy the F-14 teasing we were subjected to for a few months. Created quite a buzz. Plus, Cobra has been pretty good about warning us when he was about to miss a proposed deadline. Not to mention his continuous support of these forum. If only more "Evil Corporate Overlords" could be like him!