• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Solved Unstable System - Process crashing on Win and Linux

Status
Not open for further replies.

DrunkBlood

PCHF Member
Mar 2, 2020
117
0
23
Hello,
earlier this year I started this thread (link). At the end we thought that my GPU is broken and RMAed it. Yesterday I got it back with the message that the GPU was repaired by the distributor. Installing it again I booted my PC up and had the same issues described in my old thread. Which are that the Desktop Manager crashes every 5 min(Blackscreen) and many programs I start crash after some time. Then I shutdown the PC and created with the Media Creation tool a Win 2004 iso and installed win again. Whilst configuring(setup account) I had the same issues and trying to install chipset drivers after it the automatic installer crashed. So I hooked up the Device Manager selecting for every yellow mark the driver manually from my USB(install dir of Chipset; mostly PCI driver). Trying to shutdown after that threw me a bluescreen with the error I know from my previous step CRITIAL_PROCESS_DIED. After that I messaged the admin who handled my previous thread. He gave me the tip to open a thread in this subforum. So I am here :). I am thinking this problem has to do with memory.
I can post a speccy link for my specs if requested.
 
Hello DrunkBlood,

Be happy to try and help but only as long as we both sing from the same hymn sheet as in you only follow any steps that are suggested here, provide any feedback then wait for us to get back to you before doing anything else.

I shutdown the PC and created with the Media Creation tool a Win 2004 iso
First two suggestions, the 2004 ISO is causing many folk problems so download an earlier 1909 ISO, save to a thumbdrive all drivers that will be required.

Yesterday I got it back with the message that the GPU was repaired by the distributor. I
Did they explain what any repair was and/or what tests were carried out, seeing it happen so many times over the years has made me cynical but just so you know it is not unknown for merchants to send out the same broken item saying that it has been repaired of replaced, you were previously using a 500W PSU with a GPU that required a 750W PSU and if that is what caused the damage there is no repair for it.
 
Sry for the late reply. I might have not subscribed the thread or deleted/overlooked the e-mail.

Second suggestion:
So in the document with the GPU it says that they will charge me the repair when they found out that it was my fault or mechanical destruction. Then it says : "The Article was repaired by the Distributor. We sent it back to our relief". There is also a table with a Kd-RG-Nr, technician = 0, status = done, type = accommodating arrangement. The date is 04.06.

first suggestion:
can I download the iso with the exe of the MediaCreationTool1909 I still have laying around?

my thoughts:
I think there are 2 cases
1. GPU was repaired
2. GPU was not repaired
if 1 then I would memtest my 4 Slots with my 2 Sticks such that I test each slot with each stick for 4-5 passes ( I have not done that yet; waiting for your input / "sing from the same hymn")
if 2 then I would try the same spiel with a new GPU like the PSU in the old thread (Again I have not done that yet; waiting for your input / "sing from the same hymn")
 
Testing the RAM properly will take many hours but if that is what you want to do first let us know and the steps will be provided.

For the 1909 ISO see info here

Sorry for the confusion but the second suggestion was to save to a thumbdrive all drivers that will be required.

If me I would first of all do a clean install of version 190 and the MB drivers and then try giving the computer a good long test before starting to install any third party software.
 
Trying to get the Iso from your tutorial the page showed me even on iphone or ipad the download for the 2004 iso.
pic1.png
 
I found an old backup iso from the time of the old thread and installing the iso right now vi Rufus. Then I will install win again and tell back after MB driver are on. Okay?
 
Excuse me butting in but you can download Windows 10 1909 by using this downloader from HERE

It is an updated one from this guide
 
Today I installed the 1909 iso I had backed up. Instaling was fine until it rebooted at the end to start the process of setting up a user and co(configuration). Before anything was shown to me I got an bluescreen CRITICAL_PROCESS_DIED. After that I got a window saying that I needed to connect to the internet to fix some stuff. Before I could read everything I got a short blackscreen. After that I saw a loginscreen with defaultuser_0 and the screen refreshed every few seconds presumable the login process crash. Then I shutdown before doing anything else to report. Keep in mind this was the iso I had from the time of the last thread and not the one I could get from the downloader via gus.
 
Being that it does the same in Linux your suspicions that it is hardware related look to be correct.

Before testing the RAM using Memtest, can you try booting with one stick of RAM at a time to see if that changes anything.
 
Did the same thing happen when you tried booting with just the second stick.

NB: Try booting with one tick at a time in each slot.

Edit to add: sorry was a bit pushed for time so rushed my reply and should have mentioned that the pic above suggests a Windows problem.
 
and should have mentioned that the pic above suggests a Windows problem.

Would it help to reinstall Windows again since the crash I reported (Bluescreen) was in the setup phase and Windows said that something has gone wrong and wanted me to update via the internet.

Did the same thing happen when you tried booting with just the second stick.

When I booted first with the 2 sticks I got the loginscreen with defaultuser0 and I did not get the error message I posted a photo of.
Then I removed 1 stick and booted up. There I got to the overlay where you have to click to get to the loginscreen. After I clicked the screen froze with it shading blue. After some time it unfroze and I got to the loginscreen with defaultuser0. Seeing that I had the same blackscreens I tried to shutdown. After clicking the icon I got the error. Then I took the photo and clicked ok multiple times. Soon I saw that I could not shutdown the PC with the icon/GUI so I held the power button like I do when a pc gets stuck in an infinite loop.

I am waiting for your thoughts before I do anything.
 
Before reinstalling Windows I would try testing the system using one stick of RAM at a time but running Linux, if the system is stable with both sticks when running Linux that really only leaves Windows or the storage device.
 
For the time I had today I did 3 configs with the bionicpuppy64 distr of Puppy Linux

1. Stick 1 | Slot 1
2. Stick 2 | Slot 2
3. Stick 1 & 2 | Slot 1 & 2

Over all configs I looked through syslog and kernel log
In common:
Overall the system is more stable that Windows. I do no have frequent blackscreens and can operate basic programms. Only the browser breaks down and I can not use it.
In the logs I found many segfaults and after some time it logs some machine check exceptions from the CPU ie. Hardware failure. Some segfault are from dynamicly linked libs and I have not checked what programm crashes. I could play some games and run paint.
From the system I can copy the minidump from the crash of windows(setup phase) if you need it.

Other:
In config 3, booth sticks, my Display Server(Xorg) crashed because of a segfault.

All in all it seems more like an Hardware Error from memory. I checked once the Taskmgr and it said that the system uses about 300MB of RAM.

To note: I have 2 other RAM sticks who were replaced by my current ones when the issue first surfaced.
 
Sorry but you need to test each stick individually in each of the four slots as it is the only way that you can obtain conclusive results, a stick of RAM can work fine in three out of four slots but for some reason it causes problems when the same stick of RAM is inserted into a particular slot, this is why testing RAM with Memtest takes so long.

All in all it seems more like an Hardware Error from memory. I checked once the Taskmgr and it said that the system uses about 300MB of RAM.
RAM or one or more of the DIMM slots.

Test each stick individually in each of the four slots and see what happens, from there we can move onto Memtest if needs be, don`t want to put up a wall of text so will hold off posting the Memtest info for now.
 
Status
Not open for further replies.