I recently switched out my AMD Ryzen 7 3800x for a Ryzen 9 5950x. I also purchase and M.2.
I got these today and installed them on my computer. I have an SSD, a hard Drive and now an M.2
I deleted Fortnite from my hard drive and then installed it on my M.2 the game started up fine it played okay no problems
Then I uninstalled Call of duty modern warfare. I reinstalled it along with its launcher on the new M.2
After installation I went to start the game and check out how it runs with the new stuff.
My problem is that every time I try to start the game it loads for 10 seconds then my computer reboots. I cannot even load into the game because the computer just reboots itself.
I have tried uninstalling and reinstalling again,
I tried running as Administrator,
I attempted to reset the M.2 and see is that was the issue,
I also uninstalled and reinstalled fortnite and it worked perfectly fine.
Does anyone have any tips on what to check or what to do? Everything is up to date. I also reset my bios just in case my old overclock settings for the old CPU had something to do with the crashing of this new one, but nothing happened it kept crashing.
I also attempted to install call of duty vanguard and call of duty cold war. Same thing happened with those as well. I then installed a free to play game and it also happened with that.
I am not sure where to go from here. If anyone has any tips on how to fix this I would be more than pleased. Thank you so much
Related
My first stack overflow question, here we go.
Last week the computer on which a prototype vision application written in C#/.net was running crashed due to an unreleated reason. this resulted in the need to fresh install windows (windows 10 IOT). after installing windows, halcon 20.11 progress and setting the licenses the application starts, but no output is shown on the smart window control, even tho this worked beforehand?
i have been trying to debug this problem for the last day, but have had no luck, what i have allready tried:
used the remote debugging toe verify that the image is captured and processed and "displayed".
checked the system logs for any warnings, there were none.
Tried one of the example programs the come with Halcon, which also does **not **work.
Ran the application on my development PC, which worked flawlessly as it always did.
Reinstalling Halcon.
does anyone have had any similar experiences and/or any clue how to solve this problem?
problem has been solved. in the end a reset of the bios settings to there default values did the trick. Don't know what they exact cooperative was, but at least it works once again.
I need help fixing my laptop. Yesterday I updated some drivers, rebooted my system , saw a black screen which appeared to be updating bios. I rebooted my laptop thinking I did something wrong.
Now my laptop gets stuck on the Legion screen everytime.I have a macrium backup image on my external but don't think that will work. At this point I just want to get into windows then I can restore my disk image from the external. All my data is backed up.
I have performed a system restore and it still gets stuck at the Legion screen. I've run a chkdsk and it doesn't find any issues. When I tried to run bootrec.exe \Rebuildbcd it doesn't locate a windows installation.
I tried going into safe mode and ultimately get a blue screen saying the following:
We've run into a problem and your device needs to be restarted.
Driver pnp watchdog error
I also got a log error for
srtTrail.txt
I'm going insane trying to figure this out. I've installed windows 10 on a WD Black SN850 Nvme. No issues here. I then have another nvme with a larger size I got after that I decided to use to install programs.
I seem to be able to install programs just fine on the secondary drive, but they start to error out trying to run them. I completely replaced the 2ndary nvme with a new one, reinstalled windows on the main nvme but get this same frustrating situation. Permissions on folders are set to full access, I can open simple text files on the 2ndary drive just fine. However, running exe or other program types returns an unable to access error.
Is there something I'm missing for the nvme set up? The fact I can partition the drives and use them as normal leads me to believe they are configured correctly. Not to mention I completely swapped out the 2nd nvme with a brand new one. I also ran bios tests for the drives and came back with no errors. I also checked the drivers/bios updates for the board and made sure it was up to date. Any programs installed on the main drive are also running just fine without issue.
I also popped in a few regular ssd, installed programs on them and also have no issues running them.
This is super frustrating and I can't figure out why the 2ndary nvmes I use are consistently getting errors running any programs installed on them.
Any advice on what else to check would be great appreciated.
A react native expo app run within WSL, is the cause of a very annoying bug.
A few minutes after starting the Expo project, the internet on the windows laptop stops working.
I found this command fixes it:
Restart-Service LxssManager - when run from Powershell
However, this happens many times a day and means I have to restart the Expo project every time.
Related to: https://askubuntu.com/questions/1203412/wsl-causing-my-internet-to-not-work
Equally crazily, the fingerprint sensor on my laptop stops working and works again after that command is run.
I suspect the issue is somehow related to a very short (2-5 minute) timeout related to the react native app.
If anyone is able to point in any direction, I would love any help.
Maybe it's Expo or maybe I have some kind of local app code error. But I wouldn't know where to even start or test a bug like that.
Here is a basic run-through of what happens.
Start Expo app in WSL
Work, for an indefinite time
If PC activity pauses for longer than 3 min, the error happens. No internet, no fingerprint sensor.
Run the PowerShell command, restart the app. All is good again.
This is a known bug in WSL. Microsoft has solved this bug in build 18890. https://github.com/MicrosoftDocs/WSL/blob/live/WSL/release-notes.md#build-18890
It happens when a process in WSL creates and closes a large number of non-blocking TCP sockets, and after that some ephemeral TCP ports are leaked, eventually exhausting all ephemeral ports in both the host and the WSL.
You can try upgrading your system to version 2004 or 20H2 and see if this problem persists.
I am really new to Windows Phone 8 App development. I would be grateful to you if you can answer my question. I have a machine with Intel(R) Core(TM) i3 processor and when checked I found out that my virtualization setting enabled.
I installed Windows Pro 8.1 in to my machine and then it indicates that my Hyper Visor is default switched off and I had to run it. But when I run it after making some of the changes by restarting the machine, suddenly for some unknown reason it undoes every change made finally leaving the machine with no Hyper Visor running.
I come across the same process when I am to run the Windows Phone emulator to test Windows Phone 8 Apps.
I hope my issue is clear to you all, can someone help me to fix this issue or tell me the exact reason behind this?
I would look at my Windows Event log and see if you perhaps there's a problem with Hyper-V being incompatible with a driver or something like that. It may be failing to reboot and the doing a system restore to get the machine back to a bootable state (by rolling back Hyper-V). I've had problems with Hyper-V and my HP laptop's blue tooth drivers:
Here's the thread where I found out about that:
HP Bluetooth / Hyper-V woes
Updating the driver to the newest version on HP's site fixed my computer for a while, but then I had problems with Windows Update hosing my machine with an update to the Bluetooth driver.
I seem to have fixed it for good by going to RA Link's website and downloading a version of the driver that's newer than the one on HP's website. I'm not at my personal computer right now, but if you'd like I can see if I can find the driver version that seems to have fixed my Bluetooth/hyper-v problems for good.
-Eric