Windows 10 crashing with no bsod.

[Jolaoso]

I recently have been getting Radom crashes with multi colored lines when Windows crashes, and I'm not sure why. Even when I'm not doing something intense it crashes and I have to force shut it down because it seems it does not want to shut down its self. Ive look online and non of the solutions worked. Any suggestions? I will provide a picture in a bit.

(Update) Forgot about the laptop and thought it was time to build the PC i was suppose to.

 

[LinuxDevice]

What you are describing might be typical of overheating. Is ventilation good, and without dust covering things?

 

[Jolaoso]

What you are describing might be typical of overheating. Is ventilation good, and without dust covering things?

CPU stays between 50-80 " never hit 90"

 

[Jolaoso]

What you are describing might be typical of overheating. Is ventilation good, and without dust covering things?

Now I'm running into a issue. The computer froze again and and turned it off. Now everytime I try turning it on, a few seconds later it just shuts down. Not it won't even turn on properly.d

 

[LinuxDevice]

If power consumption exceeds some rail's expected value it will do what you described (the power supply itself will do this...and it isn't just too much power being drawn, it's anything making the power unstable...switching supplies won't regulate if the consumption is too low so there is a fraction of a second after a power button is hit before the supply actually powers up...it is waiting for one of the rails to become stable).

The other time when it will do this is what is called a triple machine exception...this only occurs when there are seriously wrong software interrupt states in the kernel where data corruption is likely if continuing...the CPU will simply power off the system. So power supply is more likely...you might get a triple machine exception if you have a badly corrupted driver. Getting a driver that badly corrupted is somewhat difficult if there isn't an outright hardware failure.

People usually think of using too much power to only be power rails going to the motherboard. There is one other case I know of which is quite possible, and perhaps common. The USB ports define standards of how much current the USB peripherals are allowed to use. USB2 has a lower maximum current than USB3. If your USB ports are consuming too much power, then a few seconds after powering on it is likely to simply turn the system back off. Disconnect your USB devices and see if it still has the issue during a cold start. Plug the keyboard and mouse in only after it starts, one at a time.

I did find one odd culprit like this in the past. Some USB3 connectors are backwards-compatible with older USB2 ports. In theory they just throttle back to USB2 speeds when in a USB2 port. One of my devices forgot to also consume less power...it tried to consume USB3 standards power from a USB2 port. This caused a shutdown similar to yours. Moving the cable from the USB2 port to a USB3 port solved this.

Too many USB devices can also cause issues. An externally powered USB HUB will get around this.

 

[Jolaoso]

If power consumption exceeds some rail's expected value it will do what you described (the power supply itself will do this...and it isn't just too much power being drawn, it's anything making the power unstable...switching supplies won't regulate if the consumption is too low so there is a fraction of a second after a power button is hit before the supply actually powers up...it is waiting for one of the rails to become stable).

The other time when it will do this is what is called a triple machine exception...this only occurs when there are seriously wrong software interrupt states in the kernel where data corruption is likely if continuing...the CPU will simply power off the system. So power supply is more likely...you might get a triple machine exception if you have a badly corrupted driver. Getting a driver that badly corrupted is somewhat difficult if there isn't an outright hardware failure.

People usually think of using too much power to only be power rails going to the motherboard. There is one other case I know of which is quite possible, and perhaps common. The USB ports define standards of how much current the USB peripherals are allowed to use. USB2 has a lower maximum current than USB3. If your USB ports are consuming too much power, then a few seconds after powering on it is likely to simply turn the system back off. Disconnect your USB devices and see if it still has the issue during a cold start. Plug the keyboard and mouse in only after it starts, one at a time.

I did find one odd culprit like this in the past. Some USB3 connectors are backwards-compatible with older USB2 ports. In theory they just throttle back to USB2 speeds when in a USB2 port. One of my devices forgot to also consume less power...it tried to consume USB3 standards power from a USB2 port. This caused a shutdown similar to yours. Moving the cable from the USB2 port to a USB3 port solved this.

Too many USB devices can also cause issues. An externally powered USB HUB will get around this.

USB, i might be guilty of breaking a USB capacitor but i've never used those ports ever since 😀. But what about memory? I just changed out the memory and the computer actually turned on. I dont know if it will stay on but im keeping my eye out for it.

 

[Jolaoso]

If power consumption exceeds some rail's expected value it will do what you described (the power supply itself will do this...and it isn't just too much power being drawn, it's anything making the power unstable...switching supplies won't regulate if the consumption is too low so there is a fraction of a second after a power button is hit before the supply actually powers up...it is waiting for one of the rails to become stable).

The other time when it will do this is what is called a triple machine exception...this only occurs when there are seriously wrong software interrupt states in the kernel where data corruption is likely if continuing...the CPU will simply power off the system. So power supply is more likely...you might get a triple machine exception if you have a badly corrupted driver. Getting a driver that badly corrupted is somewhat difficult if there isn't an outright hardware failure.

People usually think of using too much power to only be power rails going to the motherboard. There is one other case I know of which is quite possible, and perhaps common. The USB ports define standards of how much current the USB peripherals are allowed to use. USB2 has a lower maximum current than USB3. If your USB ports are consuming too much power, then a few seconds after powering on it is likely to simply turn the system back off. Disconnect your USB devices and see if it still has the issue during a cold start. Plug the keyboard and mouse in only after it starts, one at a time.

I did find one odd culprit like this in the past. Some USB3 connectors are backwards-compatible with older USB2 ports. In theory they just throttle back to USB2 speeds when in a USB2 port. One of my devices forgot to also consume less power...it tried to consume USB3 standards power from a USB2 port. This caused a shutdown similar to yours. Moving the cable from the USB2 port to a USB3 port solved this.

Too many USB devices can also cause issues. An externally powered USB HUB will get around this.

Scratch that i just got a "Reference by pointer" bsod.

 

[LinuxDevice]

Bad RAM can reach a triple machine exception and instantly boot. So can a USB power issue...if a capacitor was damaged then it might be it just took time to break down enough to matter.

Some power supplies also just go bad...they become marginal. This is actually more dangerous than complete failure (like brownouts are more dangerous than complete power loss). Basically you can't be sure that memory or other parts of the system actually do what they are supposed to do all the time unless power is stable and sufficient. This is also a good reason to use an UPS which protects not just from power loss, but also from brownouts.

You can get power supply testers for about $20, though you should read reviews before getting one...quality is amazingly different among testers of the same price range. Newegg sells some and has reviews.

FYI, in a case of something USB going bad it does tend to start to power up and then shut off. Bad RAM tends to start booting and then lock...and less often just reboot. A bad power supply or brownouts can do any of the above...including damage to components.

 

[Jolaoso]

Bad RAM can reach a triple machine exception and instantly boot. So can a USB power issue...if a capacitor was damaged then it might be it just took time to break down enough to matter.

Some power supplies also just go bad...they become marginal. This is actually more dangerous than complete failure (like brownouts are more dangerous than complete power loss). Basically you can't be sure that memory or other parts of the system actually do what they are supposed to do all the time unless power is stable and sufficient. This is also a good reason to use an UPS which protects not just from power loss, but also from brownouts.

You can get power supply testers for about $20, though you should read reviews before getting one...quality is amazingly different among testers of the same price range. Newegg sells some and has reviews.

FYI, in a case of something USB going bad it does tend to start to power up and then shut off. Bad RAM tends to start booting and then lock...and less often just reboot. A bad power supply or brownouts can do any of the above...including damage to components.

I understand that but in my situation I'm not sure which of the 3 is causing it. Is there any way to tell? There's no blue screen showing me a error.

 

[LinuxDevice]

A $20 power supply tester can usually spot a marginal "out of spec" supply. Booting a single RAM stick and running under memtest86+ (it's free, you make a bootable CD and it has its own mini-operating system) for a few hours minimum might tell you about that particular RAM stick. Corruption due to some hardware failure (other than RAM) would be difficult to trace without swapping out major components (such as motherboard). The video card has RAM in it too, but it is not something easily tested...usually bad video RAM results in "artifacts" (things like suddenly getting bad pixels all over). Multi-colored lines does not sound like random pixel failure, so it doesn't sound like video hardware failure. Any component you can test swap with another is a good way to proceed...sorry, other than memtest86+ I don't know of many free ways to test.

 

[Jolaoso]

A $20 power supply tester can usually spot a marginal "out of spec" supply. Booting a single RAM stick and running under memtest86+ (it's free, you make a bootable CD and it has its own mini-operating system) for a few hours minimum might tell you about that particular RAM stick. Corruption due to some hardware failure (other than RAM) would be difficult to trace without swapping out major components (such as motherboard). The video card has RAM in it too, but it is not something easily tested...usually bad video RAM results in "artifacts" (things like suddenly getting bad pixels all over). Multi-colored lines does not sound like random pixel failure, so it doesn't sound like video hardware failure. Any component you can test swap with another is a good way to proceed...sorry, other than memtest86+ I don't know of many free ways to test.

(This is a laptop by the way and I will try the memtester) I did switch out the single ram sick for another one of same specs and I still got the same results even worse. Got more than 5 different blue screens, plus the typical freezing with no blue screens. And the CPU is still maintaining temps under 80. I even switched chargers and nothing changed. I've tried to update drives but I can't even do that without running into issues.