-
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
- Thread starter DrunkBlood
- Start date
- Status
Progress report:
Done all configurations for booth sticks ie:
1 in 1 2 3 4
2 in 1 2 3 4
I had no crashed and let the system run for about a min
Now I will do the 2 out of 4 configs ie:
1 2 done
TODO
13,14,21,23,24,31,32,32,41,42,43
Before I start and waste maybe time. Is 1 min wait enough for a config after a succes. boot? Or do I need to wait like 5min?
Done all configurations for booth sticks ie:
1 in 1 2 3 4
2 in 1 2 3 4
I had no crashed and let the system run for about a min
Now I will do the 2 out of 4 configs ie:
1 2 done
TODO
13,14,21,23,24,31,32,32,41,42,43
Before I start and waste maybe time. Is 1 min wait enough for a config after a succes. boot? Or do I need to wait like 5min?
Today I had enough time to test all 2 out of 4 configurations.
In total I have tested 1 and 2 in all 4 slots (previous post)
And now I got the 2 out of 4 tests (boot up ram only ie no install and wait ~3min)
Stick1 Stick2
1|2 good
1|3 good
1|4 good
2|1 good
2|3 good
2|4 good
3|1 good
3|2 good
3|4 good
4|1 display server X-org crashed twice but I had no system crash
4|2 good
4|3 good
In total I have tested 1 and 2 in all 4 slots (previous post)
And now I got the 2 out of 4 tests (boot up ram only ie no install and wait ~3min)
Stick1 Stick2
1|2 good
1|3 good
1|4 good
2|1 good
2|3 good
2|4 good
3|1 good
3|2 good
3|4 good
4|1 display server X-org crashed twice but I had no system crash
4|2 good
4|3 good
Can I ask that you only post back when you have finished all testing and so have all of the test results, I never got any notification of your replies #22 and #23 as you were replying to your own reply #21 
One minute is nowhere near long enough I`m afraid and what you ideally should have been doing was to use the computer as you normally would albeit with only the one stick of RAM inserted, below is my canned info for properly testing the RAM;
How to physically test your RAM.
The following checks require the computer case to be opened so take the following safety precautions 1st, disconnect the power cord from the wall socket, press the case power button for twenty seconds or so to get rid of any residual charge in the system, take anti static precautions before touching anything inside, you can do this by touching a bare metal part of the case or PSU or if a notebook by touching a household radiator or associated copper feed pipe.
Have a pencil and notepad to hand.
Remove each stick of RAM and blow out the memory slots.
Insert the first stick of RAM in memory slot one, reconnect the power and in the case of a desktop computer the video to screen cable.
Power up the computer and see how it goes.
Make a note of the results.
Repeat the procedure until the first stick of RAM has been tested in each memory slot and the results written down.
Remove the first stick of RAM and put it to one side on top of a piece of paper with the number one on it for identification purposes.
Repeat the procedure with all RAM until each stick has been tested in all slots, the results written down and the sticks identified numerically.
Now the really long winded part;
If no individual stick of memory or slot on the MB has an obvious problem all of the above needs to be repeated but this time by running Memtest 86 for each stick of RAM and in each slot on the MB and for at least 4/5 passes, for some reason that many of us cannot explain a stick of RAM may work in one slot on a MB but not in another.
One minute is nowhere near long enough I`m afraid and what you ideally should have been doing was to use the computer as you normally would albeit with only the one stick of RAM inserted, below is my canned info for properly testing the RAM;
How to physically test your RAM.
The following checks require the computer case to be opened so take the following safety precautions 1st, disconnect the power cord from the wall socket, press the case power button for twenty seconds or so to get rid of any residual charge in the system, take anti static precautions before touching anything inside, you can do this by touching a bare metal part of the case or PSU or if a notebook by touching a household radiator or associated copper feed pipe.
Have a pencil and notepad to hand.
Remove each stick of RAM and blow out the memory slots.
Insert the first stick of RAM in memory slot one, reconnect the power and in the case of a desktop computer the video to screen cable.
Power up the computer and see how it goes.
Make a note of the results.
Repeat the procedure until the first stick of RAM has been tested in each memory slot and the results written down.
Remove the first stick of RAM and put it to one side on top of a piece of paper with the number one on it for identification purposes.
Repeat the procedure with all RAM until each stick has been tested in all slots, the results written down and the sticks identified numerically.
Now the really long winded part;
If no individual stick of memory or slot on the MB has an obvious problem all of the above needs to be repeated but this time by running Memtest 86 for each stick of RAM and in each slot on the MB and for at least 4/5 passes, for some reason that many of us cannot explain a stick of RAM may work in one slot on a MB but not in another.
As you can see in the pdf I followed the steps you gave me. In the first part of the test I ran the system for 30 min at a minimum and had mostly process crashes and could not use the browser. Only when stick 1 was in slot 2 had I a kernel panic booting up.
In the second part I did the standard settings for memtest86 for each config taking about 2:30h with 4 passes. Overall I had 0 errors.
In the second part I did the standard settings for memtest86 for each config taking about 2:30h with 4 passes. Overall I had 0 errors.
Do you have a crash dmp for the above.
Did you have any problems when not connected to the internet.
Can you post a new MTB log for us.
Don`t know about you but I would consider four passes of Memtest to pretty much prove that the RAM and memory slots are ok.
I think I do not have a dump for that since it is a live distro.
Yes I still got process crashes without my LAN connection.
I would like to provide a MTB log. But I can only provide that if I reinstall win since I do not have a user set up atm and so on (described in my earlier post).
So I would download an iso (gus link) and burn it on an usb with rufus and try to install again hoping that it won't corrupt win again, try to install chipset drivers and then run MTB if that is ok by you.
Checklist:
RAM : ok
MB RAM-slots: ok
PSU : (new) ok
GPU: ?
drives : ?
MB other : ?
something I might have forgotten: ?
Yes I still got process crashes without my LAN connection.
I would like to provide a MTB log. But I can only provide that if I reinstall win since I do not have a user set up atm and so on (described in my earlier post).
So I would download an iso (gus link) and burn it on an usb with rufus and try to install again hoping that it won't corrupt win again, try to install chipset drivers and then run MTB if that is ok by you.
Checklist:
RAM : ok
MB RAM-slots: ok
PSU : (new) ok
GPU: ?
drives : ?
MB other : ?
something I might have forgotten: ?
Wasn`t aware that Windows was not installed tbh.
Clean install of Windows, the chipset drivers and nothing else to begin with sounds like the way to go, no rush here as I have an early start so calling it a day now.
Clean install of Windows, the chipset drivers and nothing else to begin with sounds like the way to go, no rush here as I have an early start so calling it a day now.
Today I burned the iso as I said and started the install process. All files were copied and then it needed to restart. After the restart it showed me the setup ( which location I am from). Before I could enter anything it crashed and rebooted.Then it promted me to connect to the internet. Until that was the same as the previous install I mentioned here. But with this one I connected via cable and clicked next. Soon after that it crashed again. After some crashes I got an bluescreen CRITICAL_PROCESS_DIED. After some more reboots windows ran the recovery part. I got into troubleshoot and tried to get a cmd. But I was prompted by and passoword request of Administrator. After testing admin and root I got in with nothing as pwd. After getting in the cmd I tried to cd C:\ but the keyboard-layout was US and I do not know anything about that. So I shutdown and changed the boot order to the live linux. In that I was able to copy the 2 crash dumps which I attached here.
So now I have on the SSD the files of Windows 10 1909 but I can not get an MTB log.
So now I have on the SSD the files of Windows 10 1909 but I can not get an MTB log.
Both crashes list PspCatchCriticalBreak+115 and ntkernel but no drivers involved, we have been focusing on the RAM when perhaps we should have looked at the storage devices.
Being honest I did not know what PspCatchCriticalBreak+115 was so used Google, fast boot and a flaky storage device was all that I found.
If fast boot is enabled, disable it please and see if that helps.
Pain in the proverbial I know but do you have another drive that you could install Windows to just for testing purposes, the SSD would need to be removed from the MB when you do this.
Being honest I did not know what PspCatchCriticalBreak+115 was so used Google, fast boot and a flaky storage device was all that I found.
If fast boot is enabled, disable it please and see if that helps.
Pain in the proverbial I know but do you have another drive that you could install Windows to just for testing purposes, the SSD would need to be removed from the MB when you do this.
I do not have fast boot set.
I do have another drive where I have Windows already on another spec installed. Can I just connect the drive via a sata cable or do I need to reinstall Windows on it?
I do have another drive where I have Windows already on another spec installed. Can I just connect the drive via a sata cable or do I need to reinstall Windows on it?
Fast boot info acknowledged.
Not sure what you mean by on another spec, can you get back to us on this.
Not sure what you mean by on another spec, can you get back to us on this.
I have an old laptop with the specs you can see here.(CPU:i5-3210M|GPU:Nvidia Geforce GT 645M| RAM: 2x4GB) The 1TB has Linux on it and a 256GB SSD with Windows I needed for a program. It is quite old and my question is wether I can "hotswap" the drive or wether the driver installed on it might cause a problem
You could try uninstalling any Medion and any other third party drivers that are on the drive while it is still in the notebook and just leave Windows on the device, your desktop will then hopefully just see things as if it were a first time install.
NB: been so long that I cannot recall if the present SSD is the SATA or M2 type so will mention both scenarios, if a SATA device disconnect it and if possible use a new SATA cable with the replacement device and make sure that you do not use the same SATA port that the present device is connected to, if your SSD is the M2 type just remove it from the MB.
Good luck
NB: been so long that I cannot recall if the present SSD is the SATA or M2 type so will mention both scenarios, if a SATA device disconnect it and if possible use a new SATA cable with the replacement device and make sure that you do not use the same SATA port that the present device is connected to, if your SSD is the M2 type just remove it from the MB.
Good luck
So I had an m2 ssd and and removed it connecting with the other windows install on the ssd working in another spec.
Starting up it gave me the message starting automatic repair and throw me into the troubleshoot screen. Normally I would have clicked startup repair but I wanted your input. I am thinking that the windows install expects something from the other setup and the startup repair might fix that. I did not uninstall any drives as I looked at the device manager seeing only basic drivers and the chipset + GPU drivers from windows update.
NB: On Tuesday and Thursday next week I need to use windows on the other spec.So I am going to install it back on Monday I think
Starting up it gave me the message starting automatic repair and throw me into the troubleshoot screen. Normally I would have clicked startup repair but I wanted your input. I am thinking that the windows install expects something from the other setup and the startup repair might fix that. I did not uninstall any drives as I looked at the device manager seeing only basic drivers and the chipset + GPU drivers from windows update.
NB: On Tuesday and Thursday next week I need to use windows on the other spec.So I am going to install it back on Monday I think
Any drivers from the other computer have to be uninstalled or Windows will try and load them and it was most likely the incompatible chipset drivers that tripped Windows up when it tried to load them.
So I should uninstall drivers while the system is running. So with DDU we used earlier I would uninstall the GPU driver and Intel HD Graphics. Do I need to uninstall any driver not named Windows Basic X?
Yes as you cannot uninstall them any other way.
Only drivers that need to be removed are the chipset, any add on GPU drivers+ the Intel HD drivers, the latter only because your other comp is an AMD platform.
Use DDU for any add on video card drivers the others can be done in Device Manager.
Only drivers that need to be removed are the chipset, any add on GPU drivers+ the Intel HD drivers, the latter only because your other comp is an AMD platform.
Use DDU for any add on video card drivers the others can be done in Device Manager.
Ok I found the Intel Drivers and the GPU drivers. But I have no clue about the chipset drivers. Are they the drivers listed under Processors?
I have marked the drivers I think I need to uninstall
I have marked the drivers I think I need to uninstall
We are looking for Intel Chipset drivers, info on Medion computers is hard to find and any support even more difficult to find so we will have identify the drivers ourselves.
Download and run DriverView which you can get from here
Save the results to text and attach to your next reply for us if you will.
Download and run DriverView which you can get from here
Save the results to text and attach to your next reply for us if you will.
- Status