Windows 10: reboot

If I reboot my pc I will lose programs or folders

:)

 

Windows 10 endless loop reboot

Hi,

• Have you checked if the hard disk is set as first boot device in the BIOS?
• Which version of Windows is installed on the computer?
• What did the HP supported suggested you to fix the issue?

I suggest you to follow the steps provided in the following article and check if it helps.

Windows 10 endless loop reboot

If the issue persists, please get back to us with the more information about the interaction with HP support and the outcome of the issue.

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

 

HyperSLI (Enabling SLI on non-sli motherboards)

Boot problems

Hi everyone.

I've got some problems during instalation. I disabled UAC, passed the first install step, rebooted and completed install. But after consequent reboot Windows detects 'ntoskrnl' or something is corrupted.

Everything was fine on 'old' windows, but after I made a clean windows installation, everything goes this way.

Any suggestions?