• 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.

Not Exactly a BSOD, but Black screen and System Shutdown

Status
Not open for further replies.
I just got a new used motherboard 2 weeks ago MSI MEG B550 Unify-X. Since using this mobo I've had multiple instances where I lose display as in the screen goes black, I then get a 00 on my motherboards Debug LED readout. Pressing the case power button does nothing, the same with pressing the reset button on my case. I also have a power button and reset button on my motherboard and pressing them does nothing, my system stays on, with a black screen and my fans going at the normal speed, they aren't ramping up or anything. The only way to restart the system is to turn off the PSU then turn it back on and press the case power button and my system boots like nothing happened.I do not have a minidump file to share unfortunately. I checked Event viewer and all it shows is The previous system shutdown at ... on ‎... was unexpected. I've included the event viewer text attached to this post. I checked my system temps and all are in normal range. Including CPU and GPU. I wenrt ahead and ran scandisk and there are no errors I also validated my Windows install and there are no errors with that. I thought maybe it was a BIOS issue so I went ahead and rolled back from the newest bios version to the 2nd newest bios version and it still happened.
Also i noticed in Event viewer that i am getting a lot of errors having to do with network and some software. If you guys have any programs you want me to run that will provide some more info I'd be happy to do that. I'm on the latest build and version of Windows 11 Pro.
 

Attachments

  • Event viewer.txt
    1.3 KB · Views: 0
the mere fact it is a used mobo may be the reason, do you know why they were selling it?
what is the warranty?

have you tried using the mobo with the barest of hardware components attached? (eg: one memory stick, one drive, no DVD unit, no mouse, no peripherals)
 
sorry for the late reply. They were selling it becuase he switched over to Intel. I messaged him a few times and he said he never had a problem with it. He was running a watercooled system with the board so I made sure to check the board for possible liquid damage but didn't see anything. On a side not, I think, finger crossed that I might have figured out what was causing the shutdowns, but I'm not 100% sure. So when he gave me the mobo, it was in box from his new mobo, in that box was a cpu cooler backplate and a rubber gasket. I didn't use the backplate becuase he said it was for an Intel CPU but I decided to use the gaskey on the backplate I had. When I installed the gasket between the backplate and the mobo it didn't cover the entire backplate so when i tightened down my aio pump it made the backplate bow out a bit. i am thinking that maybe that was warping the cpu socket a bit and causing the blackscreens. I removed the rubber gasket and since then I haven't had any problems, BUT then again i haven't really stressed my system since then either. So later today I'm going to stress my system for a few hours and see what happens.
 
nope that wasn't the problem, it just did it again. I have no idea what is going on. The really strange part is it only ever happens when i step away from my PC. It has NEVER happened when I'm using the PC, only when it is idle but being stressed. I wonder if it's some kind of power saving option in the bios or something, but then that doesn't explain the 00 error code on my mobo debug LED or the fact that I'm not able to shut off the PC unless I flip the power switch on the PSU. Again I asked the seller specifically if he ever had this problem before and he said no.
 
Okay update. I disabled pbo and cpb in my BIOS and haven't had any issues since but I really don't see how that should have been the issue considering this motherboard is supposed to be extremely good for overclocking, so I don't see how having 2 settings that were enabled by default in the BIOS would be causing the issue. I went ahead and purchased a different set of RAM since my current set isn't on the QVL. Although I don't think that is the issue either since I ran it through memtest and y-cruncher with no errors, but I'm actually hoping that was the issue. I'll see later today when I receive the RAM.
 
You have posted here for how long?

Hard to give proper diagnosis when all you have supplied was the motherboard.

Sorry but you have post on a tech forum asking for help but have provided zero information about your computer or it`s hardware, this makes it impossible for anyone to even hazard a guess as to what is going on.

Is the computer a custom build or brand name such as Dell or HP, if a brand name provide the model name or series number (not serial) if a custom build post the brand and model name or number for the following:

CPU
MB
RAM (including the amount)
Add on Video Card if one is used
PSU (power supply unit)
Providing these details will enable folk to better help you.

If you guys have any programs you want me to run that will provide some more info I'd be happy to do that.

Speccy maybe a MiniToolBox

I just got a new used motherboard 2 weeks ago MSI MEG B550 Unify-X.

After you installed the replacement Motherboard did you perform a clean (fresh) install of windows or use what was on the drive and hope that it works.

Quote from @phillpower2 which might explain why you are having issues.

A new MB means a clean install of Windows and for two reasons **

Once Windows has been installed before doing anything else you must install the chipset drivers for the MB, the SATA/storage device drivers for any SSD and/or HDD followed by the drivers for any add on GPU that may be present, these steps are a must and have to be done before Windows is allowed to check for updates as it has a habit of downloading the wrong drivers on you.

Second reason is down to the Windows product key, ever since Windows 8 the Microsoft servers have stored the licence key and corresponding MB details on their servers, this means that should a user ever need to do a clean install the servers check that the licence key and MB details correspond and if they do the user does not need to enter a product key number, if the MB and licence key do not match the user gets asked for a new product key, see my canned info below;

Unless your present product key is the full retail version you cannot use it with a new MB as an OEM product key is tied to the original MB it was paired with, to use an OEM key with a new MB is detected by the Microsoft servers as software piracy and therefore you get on screen warnings etc..

Exceptions to the above are 1: If your MB is replaced under warranty and 2: If your MB is replaced out of warranty with an alternative type but same brand due to the original model no longer being available, an upgraded MB however will require the purchase of a new OS licence.

If you have a full retail disk and a product key that is not in use on another computer, the OEM restriction/s is/are not the same.

** It is possible to uninstall the previous MB drivers while the drive is still in that PC, the Windows licence key info provided remains the same though, so the workaround is not worth the hassle.

Windows is trying to install the drivers for the previous MB and that is most likely what is causing the system to fall over.
 
Sorry about that, i should have known better.
Specs:
Mobo: MSI MEG B550 Unify-X
CPU: Ryzen 9 5900X
GPU: Asus TUF Gaming RTX 3080 10GB
Old RAM before I replaced it today: Kingston Fury Renegade 64GB (2x32) DDR4 3600 C18
New RAM Just Installed Today: G.Skill Trident Z RGB 64GB (2x32) DDR4 3600 C18
PSU: Corsair RM850X

My PC is not a prebuilt or a OEM, I built it.

Regarding Windows I DID NOT perform a fresh install, while I do understand drivers are different i decided not to do it. I did however install the AMD chipset after installing the OS drive. Also I'm on Windows 11 Insider Dev Build so I figured I wouldn't need to do a fresh install since installing the Dev build was basically a fresh install, I'm probably wrong about that aren't I?

Speccy:
http://speccy.piriform.com/results/QkkYTDUTkjSuX5rMJBSoPxs

For MiniToolBox did you want me to select everything or just certain things?
 
Also I'm on Windows 11 Insider Dev Build so I figured I wouldn't need to do a fresh install since installing the Dev build was basically a fresh install, I'm probably wrong about that aren't I?
Operating System
Windows 11 Pro Insider Preview 64-bit

Since you are under the Windows 11 Insiders Dev Builds, they have their own tech support that is dedicated to the insider program, and you have to go through them for any assistance.

Since the Microsoft insider program requires the OS setup and configured a specific way you will have to contact them to get this resolved.
 
I'd be going back, the Insider version is a sort of Beta version, so you never know. :)
plus I don't believe anyone here is using the Insider version so we wouldn't be able to exactly match what you are seeing or walk you through steps.
 
okay, no problem i do that right now. Turns out I'll have to do a clean install anyway in order to switch back so I'll update this probably tomorrow, now its time to have fun and take note of all my settings, and redownload all the install files for all my programs.
 
Once that is completed create a new thread with a speccy report.
plus I don't believe anyone here is using the Insider version so we wouldn't be able to exactly match what you are seeing or walk you through steps.
No that is not the reason why.

By assisting it would taint the results and the insider program has their own Tech support section for this as I have stated in post #13.

Closing thread.
 
Status
Not open for further replies.