Recommended Posts

my laptop has an AMD ryzen 7 4800H with integrated AMD radeon graphics, a GTX 1660 TI, my OS is in windows 10. My laptop has a 144hz display and an external monitor (60hz) that is connected to my laptop which works PERFECTLY FINE before everything.
 


So on my laptop screen, DOTA 2 was open while in my external monitor/display, I have my Discord and website open. I was just watching youtube vids when suddenly my monitor froze then laptop display turned blue with text saying " ;( windows ran into a problem" or something like that. At first I thought it was the fabled blue screen that breaks your computer but to my suprise it just automatically restarted my laptop, upon typing my password on my lockscreen, I noticed that my external monitor isn't working and that my laptop display looks weird. So, I asked a friend and told me to check my device manager and I saw that my AMD Radeon Graphics has this "code 43" thing, so he said to just update my drivers and update my windows software, so I did all that and its still there. I did a little exploring myself on my laptop and found that my laptop display was using MS basic display and that it was on 1hz, now I was panicking because I was thinking that my driver is broken or gone, so he told me to try using the one on the AMD website that updates drivers, and so I did that but still nothing. As for the monitor, I tried trouble shooting it, connecting-disconnecting it, force detecting with settings, using the "add device" button under "Bluetooth and other devices"  still nothing, I really dont know what to do. I dont even know what happened before the blue screen

I seen people uninstall their drivers then install it or using the roll back options but idk, what if something happened to my laptop, I dont wanna risk it ;(
 

 

OK, first off, how is the monitor connected to the laptop? (HDMI, Display port, etc) second, you said that you have integrated graphics as well as a GTX 1660. Have you checked that the Nvidia drivers are current, version 460.89 is the most current. Also I would attempt to disable the integrated graphics or the Nvidia, and see if the display comes back. I found this website that talks about the error 43, and how to potentially fix it. Also check AMD and see if your drivers are up to date, as that can cause issues as well. Third, check and see if there a specific driver for the external monitor, sometimes that can fix issues as well. As a last result, download and run DDU (Display Driver Uninstaller) and let it clean the system of all display drivers, and then reinstall them.

do you have any files in your log folder? ALL BSODs are saved there. We need the exact 000X000## code so we can help you :)

11 minutes ago, Mindovermaster said:

do you have any files in your log folder? ALL BSODs are saved there. We need the exact 000X000## code so we can help you :)

Forgot about that, he can download Whocrashed (this is a direct link to the download)

  • Like 2
1 hour ago, jnelsoninjax said:

OK, first off, how is the monitor connected to the laptop? (HDMI, Display port, etc) second, you said that you have integrated graphics as well as a GTX 1660. Have you checked that the Nvidia drivers are current, version 460.89 is the most current. Also I would attempt to disable the integrated graphics or the Nvidia, and see if the display comes back. I found this website that talks about the error 43, and how to potentially fix it. Also check AMD and see if your drivers are up to date, as that can cause issues as well. Third, check and see if there a specific driver for the external monitor, sometimes that can fix issues as well. As a last result, download and run DDU (Display Driver Uninstaller) and let it clean the system of all display drivers, and then reinstall them.

The monitor is connected using HDMI cables, I checked my nvidia drivers and no, they are not updated (installing the updated drive right now). About the disabling of integrated graphics or nvidia, I dont know how to and I'm scared it might affect something, so I might do that as a last resort. I checked the website you sent that talks about code 43, I did about 2 of the methods, the others require uninstalling the drives, updating the motherboard, and flashing(?) which I myself dont know what the outcome may be so I didnt do those. I dont think my monitor has a specific driver. Ill also do the DDU as last resort. (update just installed, im about to restart to check if there are any difference)

1 hour ago, Mindovermaster said:

do you have any files in your log folder? ALL BSODs are saved there. We need the exact 000X000## code so we can help you :)

I downloaded the app, do you mean the bugcheck code? I'm not sure, I'm not familiar with those lol

11 hours ago, Vindicta said:

I downloaded the app, do you mean the bugcheck code? I'm not sure, I'm not familiar with those lol

Open Whocrashed, and press the button that says Analyze, then it will instruct you to scroll down and see the results. It will then give you an idea as to what caused the BSOD,

2 hours ago, jnelsoninjax said:

Open Whocrashed, and press the button that says Analyze, then it will instruct you to scroll down and see the results. It will then give you an idea as to what caused the BSOD,

here you go,

image.png

16 hours ago, Mindovermaster said:

do you have any files in your log folder? ALL BSODs are saved there. We need the exact 000X000## code so we can help you :)


here it is image.thumb.png.71331d3855754e9a37df451d8a48f173.png

Yeah, that's a Memory problem...

 

Try running MemTest. It's on a bootable CD/USB. Run it for at least one cycle, see what it brings up. Overnight is preferred. Try running this with only ONE stick at a time. If it's just one stick, you can refurb the bad one, or can still use the system with your remaining stick.

 

ANY warnings, your memory is bad, need to buy new ones.

Exactly what I just determined from the dump files. Hardware.sys so either CPU or RAM, and considering one of the errors was Memory Management, I would say it is a strong possibility that you have bad RAM modules.

Update: I slept just before the replies so, sorry for that but before I slept I shut down my laptop then for some odd reason after waking up just now and opening my laptop code 43 was gone, my display were connected to my radeon graphics instead of the MS basic display, as well as my external monitor being detected and can be used by my laptop for some reason. I dont know what I did yesterday but I followed some of you guys' tips, maybe one of those fixed the code 43. As for the RAM problem, I didnt expect to run into ANY PROBLEMS really, especially because my laptop is pretty brand new (bought about last week of november or first week of december) but I'll try and find guides on how to use the MemTest that Mr. mindovermaster was saying so I could avoid more BSOD and heartattacks xD. Just wanna say thanks right now because idk what might happen I do the test lol

  • Like 1

Good to hear that it is working like it is supposed to. It will not hurt anything to run Memtest,it's just to rule out the RAM being the issue. I have had brand new out of the package RAM that ended up testing bad > month, so you can never be too careful and check everything, even if it highly unlikely that it could be the problem. Even with years of experience of building computers, I have found that sometimes it is the smallest, most obscure thing that causes the biggest problems, like something not screwed down all the way, or a cable not completely plugged in, and have spent hours upon hours trying to figure out what happened, only to discover something minute like the a fore mentioned items!

  • Like 1

To what JNelson said, do the memtest, anyway. Even though it may work fine again, you might come across this same error.

 

I had several RAM sticks that went bad. The system would work, but not to it's full potential. RMA or replace. Will save you more times than you know.

  • Like 1
  • 8 months later...

@Vindicta

I'm facing the same issue with my zephyrus g14 

I was working suddenly thought to clean dust from my table so I turn it off my clean the computer table and stand 

 

After it I plugged my laptop In 

It's detects my external monitor but no but video output 

 

I have perform have perform hdmi cable replace tried on different monitor 

 

Also updated my integrated amd and dedicated graphics driver 

 

Upon latest driver of amd its says black screen crash bug report 

 

Please help me out 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!