"New" PC crashes: No video signal,no Bluescreen, no Event Viewer entry

And 1% the memory, it should be tested?

HedgeToaster said:

I already ran a RAM Test (Test Mix = Extended, Cache = ON, Pass count = 3) -> "The Windows Memory Diagnostic tested the computer's memory and detected no errors".




I'll have to put checking that on my todo list.


EDIT: Hmm. A brief check of their website gives me some mixed messages. I'm currently back on my regular Windows instead of the freshly installed one, and the driver version number is identical, but its release date is 12/2021, which doesn't match when I installed it in January/February 2020, and I don't think I've ever reinstalled. Not sure if auto-update, bad version numbering, or me misreading something.



Update-News | AVM Deutschland


...Did Windows 11 even exist in Febr2020?


_____________________________________________________________________________

I've just had an epiphany. A really, really stupid epiphany.

My PC is connected to the my monitor via, uh, DCMI... or VGA? Probably DCMI. It's a white adapter, not blue. Irrelevant.



...And my TV is connected via a several meter long HDMI-cable, which I use as a screen mirror to watch Youtube and such.


When I installed the new Windows, resolution was all messed up. The moment I even opened "Display", it instantly auto-corrected... except, it got the monitors mixed up, identifying my TV as screen #1. Which gives me a sneaking suspicion.




Quick question: Can bluescreens happen that don't leave entries in the Event Viewer? As in, basically never?

Because what if I *did* get bluescreens, but they appeared on my TV. Which was turned off.

That would be so dumb. -_-#

And... sometimes I had my PC disconnected to connect my videogame consoles... for which I haven't needed two HDMI ports simultaneously in a long while ........ and that might have been the last time I actually saw a bluescreen on my PC, years ago.

Like I said at the start: "Why am I never even getting any bluescreens". Like, statistically, at least some crashes would have to be bluescreens. Even that one single time Windows still managed to make a memory dump and write an Event Viewer entry, there still was only a "no video signal" message on my monitor.

Blackscreen sus.





I mean I can't easily test that now, but is this possible?

(I'm reluctant to do more stress tests now for fear of somehow causing damage, and it would be very time-inefficient to use the one that's caused crashes before.)


"I mean I can't easily test that now." Unless... there's some safe way to manually trigger a bluescreen just to test this. Like... is there a program for this, "Click here to safely trigger BSOD"?

- - - Updated - - -

wait, no... I just realized that one time where it crashed (see video in first post) where everything except the monitor and keyboard was disconnected included the HDMI cable being disconnected... darn it

but... that crash was still before I realized I had not yet installed the correct MSI / AMD drivers and remedied that. Maybe there's multiple things causing a seemingly similar result going on.

in any case, I'd like to test a "safely cause BSOD"-tool, just to see what happens

In the bsod forum I have already seen those who decrypt the dump files indicated to test the memory with Memtest86 or another version, and to do 8 passes.

To try to create bsod in the bsod forum it is recommended to activate driver verifier to test the drivers. There is a procedure to properly activate it and parameters to test the drivers. I do not know.

How are you doing with your computer?

What I will do, 8 passes with memtest86 or memtest86+ (not sure which one).

Uninstall the usb wifi adapter driver in your new windows 10 installation, from the control panel and then from the device manager if it is still there. Do not connect your usb wifi adapter when you use the new installation of windows. In your new windows 10 installation you only do crash/freeze reproduction tests.

- - - Updated - - -

How to test memory when memtest+ doesn't work?

- - - Updated - - -

If your computer freezes it may be an undeclared bsod. You wait and maybe the freeze will turn into a bsod.

- - - Updated - - -

To try to create bsod I have already said it is necessary to activate driver verifer. It is only for the drivers and not certain that a bsod is triggered. To create a bsod if it's a hardware problem I don't think there is a program for that.

- - - Updated - - -

After each crash/freeze, don't forget to run these commands:
sfc /scannow
Dism /Online /Cleanup-Image /ScanHealth

And if the previous one gave errors you do this one:
Dism /Online /Cleanup-Image /RestoreHealth

At 7 to do the command line Dism /Online /Cleanup-Image /RestoreHealth without an internet connection:
Use DISM to Repair Windows 10 Image

- - - Updated - - -

With memtest86, do 8 passes for 1 memory module at a time removing the other modules, unless in the memtest86 program it is possible to test one module at a time.

itsme1 said:

How are you doing with your computer?

Crash now replicated on new Windows without any stress tests or anything special on autostart*, just "turn PC on for 10 minutes, turn it off for 10 minutes, turn it back on for 10 minutes, repeat". It crashed on bootup #4.

^{*well, I did start up some analysis programs to list temperatures and CPU load, etc, and an "auto screenshot once per second"-tool to keep track of that in case it crashed ..... but no programs causing workload for the PC}

Didn't uninstall the WLAN stick yet, hadn't seen the post yet.




Otherwise? Everything's a bit chaotic at the moment! ^_^;;;

Short version: Warranty's technically over on 22.01., but they said something like "it's okay if you send your PC during the next week".

They didn't specify an exact date, so... I guess I'd have to send it off by the end of the week. (26th - 28th...ish.)

I'll still try to figure things out until then, obviously keeping the PC at home and not risking damage in transit is much preferred. ^_^;

Noticed some stuff that might give clues, but I didn't have time yet to write it down, put screenshots together, etc.


___________________________________________________________________________________________________


Quick questions regarding memtest:

"memtest86 or memtest86+"

I'm not sure where on MemTest86 - Download now! "memtest86+" is, unless you mean the "Pro" version. I guess I'll just go with "Download MemTest86 Free (Version 10.2 Build 1000)"


1) Is this more thorough than running mdsched.exe? Because I already ran a RAM-test with mdsched.exe, with the settings "Extended", "Cache: Active", and "Pass: 3", and that found no errors.





So is that still recommended?

2)

With memtest86, do 8 passes for 1 memory module at a time removing the other modules, unless in the memtest86 program it is possible to test one module at a time.

I'm guessing if I just leave all RAM sticks in and it doesn't find any errors, I don't have to check each stick individually, right?

Of course if it does find errors, I'd check them individually to identify which of the two RAM stick may be faulty.

3) It's possible to just quit the test anytime, right? So I can boot up the program and look at the settings and such before actually running it.

Memtest86 free or memtest+ free too.
The difference and how to use them: MemTest86 vs MemTest86+ | How to Use MemTest86 (+)
You can quit at any time.
Yes it is better to use memtest than windows test.
You make 8 passes and if you have errors in the first pass, you can stop, your memory is failing. And then you test one module at a time.
If you have no errors for the memory modules then there is no need to test each module individually.

Yes, you have to hurry, you don't have too much time. Uninstall the wifi driver and memory test, and see what happens.

Although I mentioned before the BIOS you did not spend attention to it.
I am puzzled by the BIOS. Speccy finds firmware M50
Looking to the MSI site, I have the impression to find cmplete other assignments for your motherboard.
Moreover, BIOS updates seem to take place about every 4 months.
Maybe contact your supplier to this matter.

itsme1 said:

Memtest86 free or memtest+ free too. [...]
You make 8 passes and if you have errors in the first pass, you can stop, your memory is failing.

I guess according to that article you linked memtest86+ is the better option.

Okay, another quick question: I can't seem to find where to change the number of passes in memtest86+:





Or does it run indefinitely? I want to run it overnight.

I've seen how it's done in memtest86 (unless that video is out of date), but not memtest86+.


PS: Sorry for not replying to everyone.

There is no number of passes to indicate, it continues the passes indefinitely.

- - - Updated - - -

MemTest86+ - Test RAM

itsme1 said:

There is no number of passes to indicate, it continues the passes indefinitely.

- - - Updated - - -

MemTest86+ - Test RAM

Okay, thanks! :)

- - - Updated - - -

itsme1 said:

You make 8 passes and if you have errors in the first pass, you can stop, your memory is failing.

No errors found after 12+ hours and a little over 8 passes.

itsme1 said:

Uninstall the wifi driver and memory test, and see what happens.

Not had time yet to try this, currently focused on "how do I get the PC packaged up safely for transport".

itsme1 said:

it is recommended to activate driver verifier to test the drivers. There is a procedure to properly activate it and parameters to test the drivers. I do not know.

Is it this procedure? Enable and Disable Driver Verifier in Windows 10

This sounds like something I could try letting run overnight and check back in the morning, should be especially quick if I use it on the new Windows install.

I'm guessing there'd be some logfile somewhere of which driver was misbehaving?

That also should 100% certainty clear up if it is the Wifi driver or not, right? Then I don't have to rely on random chance with "turn on/off for 10 minutes, repeat until random crash".