• 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.
Correct me if I am wrong but you mean the logs from sfc and dism in %win%/Logs. So I reran the commands and piped their output to txt files. Attached now you have the logs from %win%/Logs and the command output. I could not upload a file named "CbsPersist_20200630164451.log" since it was to large.
 

Attachments

  • logs2.zip
    92.2 KB · Views: 2
Dism shows that there were issues with java which were corrected and likewise SFC was able to repair Windows corruption.

That is Windows ruled out now so the only two things left are the CPU and the MB, we can test the CPU but there is no way of testing the MB i`m afraid.

For testing the CPU use Prime95

If the CPU passes the tests it means that either the MB is bad or that the same GPU was returned without any repair having been carried out.
 
Let's say that during the Prime95 test the process crashes. Can we then conclude that the CPU has a fault. I do not see that since other processes crash without the test running. But that would be true for when we replace the test on the system. Memtest ran from a usb stick and did not crash.
 
so today I started the test and was around for about 10min to check on early crashes. There were none and I left the pc to do other things planning to test for 6hrs or sth like that since the FAQ gave those ranges. I came back after about 1 hr and checked. I had a bluescreen somewhere there and copied it over to the usb and checked the results which mostly said no errors found up until that if I am reading them right. Before I could copy the results I had another bluescreen. So the results and the bluescreens are attached. The timestamps are in UTC + 0 since I did not set a timezone.
 

Attachments

  • 070220-7890-01.zip
    286.7 KB · Views: 2
  • results.txt
    1.5 KB · Views: 3
CPU looks to be ok.

Unless overclocking you do not need to run Prime95 for anything more than sixty minutes, when troubleshooting you should at no time leave the computer unattended during the testing as you need to be there in case something goes wrong and things begin to smoke, OCers who have special cooling arrangements set up are not bound by this as there tests can run for up to forty eight hours.

Both dmps mention PspCatchCriticalBreak+ again so storage device or MB again.

Know it is a different drive but test it with Seatools for Windows which you can get from here

Make sure that you have the latest BIOS available and that your storage drivers are up to date.
 
I ran Seatools on the connected ssd.
I did not any advanced tests.
it passed:
SMART check
short generic
short drive self test

Trying to drag and drop the installer from the usb gave me 2 more crashes attached
 

Attachments

  • new dumps.zip
    280.2 KB · Views: 4
Sorry for the delay getting back to you, wasn't aware that you had replied as I did not receive any notification for some reason.

Same cause of both crashes again.

Trying to drag and drop the installer from the usb gave me 2 more crashes attached
Can I ask why you are dragging and dropping the installer in the first place and not just downloading and saving straight to the drive, this could be what is causing the crashes, from my reply #70;

Make sure that you have the latest BIOS available and that your storage drivers are up to date.
Did you do both of the above, worth mentioning is that you should also include the USB port drivers among the storage device drivers being that one of their functions is to be able to transfer data via a USB device.

NB: Another thing to check is that Power Suspend for the USB ports is disabled.
 
Can I ask why you are dragging and dropping the installer in the first place and not just downloading and saving straight to the drive, this could be what is causing the crashes, from my reply #70;
Having the crashing experience from the last thread I opted to download to a usb on a stable machine. And after the problem with the tool crashing only if I run on usb I opted to copy the file from the usb to the drive.

As far as I know I have the lastest bios having it flashed in January and the timestamp from the manufacturer has not changed. I can try to go over all the storage drivers in the devmgt and also test whether the front ports do crash the same as the ports on the BIOS.
 
See where you are coming from but doing it that way introduces another possible cause, not too bad a thing though as it did prompt me to suggest checking the USB drivers and Power Suspend for the USB ports, do make sure that for now you use the black USB 2.0 ports as the blue 3.0 type can be problematic at times.
 
See where you are coming from but doing it that way introduces another possible cause, not too bad a thing though as it did prompt me to suggest checking the USB drivers and Power Suspend for the USB ports, do make sure that for now you use the black USB 2.0 ports as the blue 3.0 type can be problematic at times.

I checked all the usb drivers and they seem ok. I also turned off Power Suspend for USB. I only have 2 USB 2.0 ports. And I have a usb-mouse and usb-keyboard. I normally plug them booth in 3.0. How should I then configure that?
 
Sorry should have included that the keyboard and mouse are ok in USB 3.0 ports but not devices that you are using to transfer data to or from, the most common problem that people have for example is when they try and install Windows via a USB 3.0 port, it doesn't seem to go too well a lot of the time.
 
Other than the GPU anything that can be tested has been properly tested and come back as being ok, the two things that we cannot test are the MB and the PSU, the PSU you have replaced so makes it 99.99% less likely as the cause which only leaves the MB itself and with the continuous errors that you keep getting all being the same it looks like the problem is with the SATA ports which in turn is what your storage devices are connected to.
 
same it looks like the problem is with the SATA ports which in turn is what your storage devices are connected to.
Just that I am on your side of thought. I have errors using a drive with SATA connection and I have errors using a drive with M.2 connection. We can not test the GPU nor MB. So we have a choice. Am I reading that right or can you provide some clarification?
 
Sorry but did not say that we could not test the GPU but rather "Other than the GPU anything that can be tested has been properly tested and come back as being ok"

For clarity, never mentioned the M2 device in my reply #78 as it was not in the board at the time but like the SATA ports the M2 card is a storage device so is in the same category as SATA storage devices.

Condensed version, other than the PSU the only two items that have to be present throughout are the GPU ** and the MB, the GPU has been sent away and supposedly repaired so if you were asked out of the two which one would you suspect as the cause.

** The GPU and M2 card sharing bandwidth could be what is causing the M2 device problems.

Best course of action if you can would be to borrow a friends GPU and try it in your computer, you have nothing else left to test I`m afraid.
 
Status
Not open for further replies.