I've got this huge pile of different RAM sticks lying around, and honestly, I can't tell which ones actually work and which ones are just dead weight. Is there any way to test them all to see what's functional and what's broken? Is there some kind of method or maybe a specific tool I could use for testing?
I’ve already tried swapping in a different CPU, and I even went as far as stripping the RAM entirely just to see if it would trigger anything. Nothing. It won't even give me a single beep to let me know the memory is missing. I even tried powering it up with the processor removed... still absolutely zero beep sounds. I honestly don't know what else could be interfering this much—it's just total silence. No image on the screen, no beep during bootup, nothing at all.
The CPU fan is spinning, and I can hear the hard drive humming, and even when I open the case, everything seems to be running normally. I honestly thought the GPU was the culprit, but I tested that theory and... nothing. Still the same issue.
The only thing I’ve noticed is that if I pull the graphics card out, the system starts giving me those error beeps—like it can't find a video card—but I already tried swapping in a different one and that didn't fix anything either.
I’ve got an old desktop sitting here, and I’m running into a bit of a headache. The power comes on just fine, but there's absolutely nothing on the screen—not even a single Beep to let me know what's going on when I try to boot it up. I actually tried pulling the RAM out to see if that would trigger some kind of error code, but still nothing... just total silence and a black screen. Is it possible the motherboard itself has finally given up the ghost?
I can't really complain about how things run once everything is up and running but for some reason, the system boot-up process is just incredibly sluggish I've already checked my settings, and everything is disabled except for my antivirus and Bluetooth.
I've gone ahead and installed all the drivers, and looking at Device Manager, there isn't a single yellow exclamation mark or any indication that anything is missing. Everything looks perfectly fine on my end.
From the moment I hit the power button until everything settles into a normal working state, it takes about 6 minutes. I honestly have no clue how old this thing is or how long it’s been sitting idle. Is there some way I can actually check those specific details somewhere?
Can I even check that once my desktop actually loads?? It’s booting up so incredibly slowly from the second I hit the power button... by the time it finally gets going, I can't even tell what's hogging all the resources during startup.
A few days ago, I installed a used ASUS motherboard and set up a fresh install of Windows XP along with all the drivers, and I'm running into this issue where it takes about 6 minutes from the moment I hit power until the computer actually stabilizes. It feels way too long. Every single step during the boot process seems to hang for at least 30 seconds before I finally see the desktop. My setup is an Intel Core 2 Duo 3.0 with 4GB of RAM. I have two hard drives installed—one is on an IDE connector and the other is on SATA. The OS is sitting on the HDD connected via SATA. I've already cleared out everything I can from the Windows startup items, and I ran a scan on the HDD using CrystalDiskInfo, which didn't show any errors. Once it finally settles down and stabilizes, the machine runs perfectly fine. Temperatures are looking okay: HDD at 43°C and the CPU core around 32-36°C.
I'm honestly stumped on what else I can do to speed up this boot time. If anyone has any advice or ideas, please share them with me.
Hey there... I just got Viber set up on my PC and everything seems to be running smoothly, but I was wondering—is there any way to actually link a second number, or maybe even two different mobile numbers, to the desktop app?
Alright, I get how RDP works, but that’s not what I’m after here. I need to be able to remote into one computer from my own machine without the other person even realizing I’ve logged on. I want both of us to be able to work on the same device at the exact same time without any interference. To be more specific: I have a BluePOS POS system running on Windows XP, and I want to be able to jump onto that machine from a different computer whenever I need to check stats or whatever. The goal is to do this without the servers even noticing I'm there—they need to be able to keep working smoothly on that terminal without being interrupted. Right now, it's a total pain because I have to stop everything at the register just so I can handle some business from my home computer.
I’ve been scouring this entire forum, but I just can't seem to find an answer anywhere.
I managed to get Remote Desktop up and running, and everything connected perfectly fine. But here’s the catch: I can't figure out how to set it up so that when I log in to my home PC, I can work in the background—deleting files, doing tasks, whatever—without interrupting the person actually sitting at the computer. I want to be able to work without messing with their screen or getting in their way.
On top of that, every single time I connect, it kicks the local user off their own monitor. Then, once I disconnect from the remote session to get back to my own machine, I have to go through the whole process of logging back in and typing in my password just to see the desktop again. It's such a hassle.
I know this is technically possible. I've seen people mention it, but I have no clue how to pull it off. From what I understand, business owners use this kind of setup to monitor what their employees are doing on their workstations without them even realizing it.
Hey everyone... I’m running into a weird issue with the date and time on my computer running Windows 7. Sometimes it saves correctly, but other times it just forgets everything when I boot up. My PC runs pretty much non-stop—it turns on every morning and stays powered through late into the night. I already tried replacing the CMOS battery on the motherboard with a brand new one, but I'm still stuck with the same problem. Any idea what might be causing this or how I can actually fix it?
Susan Lee67 said:Inside the chassis, you will find a small connector on the motherboard designed specifically for the internal system speaker, which typically features two distinct wires—usually one red and one black. Could it be possible that this connection has become loose or was never properly seated? I would strongly suggest verifying that everything is plugged in correctly, or perhaps if you aren't entirely comfortable navigating the internal components, you might consider asking a friend to take a quick look for you just to be safe.
Problem solved! I ended up pulling the speaker off my old board and hooking it up to the new one, and now everything is working perfectly... I've even got those BIOS beep codes again! Thanks everyone for the help.🙂
I've run out of cables to plug in, and I can't seem to find any more speakers to hook up... yet the rest of the audio is coming through just fine. Everything else seems to be working perfectly.
I have a quick question for you all. I'm working with a new ASUS motherboard. Everything is hooked up correctly, the PC is running fine, and I just finished a clean install of Windows XP sp3. The build is solid, everything seems perfect, but there's one thing... I don't hear that initial BEEP from the motherboard when I boot up. WHY? What could be going on here?
It hasn't made a sound since the very first time I powered it on...
The Athlon 64 is a processor I'm specifically looking for an AM2+ socket motherboard that takes DDR2, which is why I settled on these two options I came across In some local US shops.