New
#11
Have your done OS repair from your 7 install DVD? [with of course the DVD reader set as first boot device in bios]
Go to repair instead of install.
Have your done OS repair from your 7 install DVD? [with of course the DVD reader set as first boot device in bios]
Go to repair instead of install.
Also found this:
Windows 7 64, Blue Screen Stop Error: 0x00000050 during reboot or - Microsoft Community
Notable:
"Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM)."
So it's possible that CPU is toast: L2 is CPU cache, and there is nothing to fix it other than replacing if that is the case, not saying it is, though: BUT IT IS A SUSPECT.
If you didn't let that CPU cool down, and rebooted it right after it turned off, yeah it could easily be kaput now.
I would try each stick of RAM separately, also.
The first step in my mind is monitoring the temps and make sure you are not overheating. Nothing else matters until you make sure you are not running hot.
So is this thread's title mistaken and your CPU is not overheating? That would be what to address first if it is.
Cleaning dust may not be enough with an overheating CPU which needs the thermal paste replaced as shown in the video I provided.
If the CPU temp is normal and still functioning then disinfect first as OS may not repair otherwise. If no OS appears to repair when booting into System Recovery Options on disk, try jumpstarting it to appear using Bootrec.exe tool as listed in Troubleshooting Windows 7 Failure to Start
Last edited by gregrocker; 21 May 2013 at 12:53.
Hi, Gregrocker.
Thanks again for your concern !
Like stated in my very first msg: what most likely happened is that the CPU got too hot while rendering a video clip. I was not at my computer while this happened. I started rendering and I went away. When I got back to my comp I saw the BSOD. The mobo shuts the power down when the cpu-temp gets too high (set to 70°C) I think that the mobo just shuts down, and doesn't really CLOSE running programs (AND windows) right before cutting off the power. So I guess that it kinda has the same effect as pulling the mains plug in the middle of (heavy) calculations where windows is involved in. So WINDOWS got corrupted.
In the meanwhile I did several repair actions with the original Win DVD, followed a few relevant threads from here and never had problems with the CPU. I never had a crash while doing these tests/repairs. (been testing/repairing continuously for almost two days now ...) For the moment I'm running Memtest86+ (from a boot CD) for about 2.5 hrs. So far NO errors, but I'm only at 48%. So I leave it running to complete at least one full test.
Just about 2 weeks ago I vacuumed all the heat sensitive parts in the way it has to be done. I did this because I heard the beeping warning while rendering. After I did this, the CPU ran about 10°C cooler. (had a temp monitoring sofware installed > "Speccy") I did a few renderings after vacuuming and only on a very few moments I saw the temp go over 60°C. So I didn't worry anymore about overheating and left the comp alone while rendering. Although I made sure that while rendering it was the only prog that was running.
Anyhow ... when the memtest has finished (without failures) I'll follow your advice and try the bootrec.exe
And of course I'll come back here to post the results !
Thanks man, you make me feel like "not being alone on this world"
http://memtest.org/#downiso
Last edited by PaulVdB; 21 May 2013 at 13:41. Reason: added URL
Yes Faladu. I did this already several times, but no results I also followed some relavent threads from here, but again : no results...
Nevertheless : thanks alot for your concern ! If you might have other ideas : they'll be mostly appreciated !
http://memtest.org/#downiso
Last edited by PaulVdB; 21 May 2013 at 13:42. Reason: added url
If you got overheating beep codes after vacuuming the dust out then you still have critical overheating. Those beeps are not normal and mean critical failure, not something you can ignore.
You should have monitored the CPU temps to compare the max temps for your CPU easily found online. Now try booting into BIOS setup to see if it shows any readings.
I'm not sure if one of the boot disks available online has temp reading programs. We don't support them here anyway.
Everything that possibly can be done is here for Troubleshooting Windows 7 Failure to Start leading up to if necessary rescuiing your files to reinstall.
What I'd probably do just to preserve Win7 on HD while answering if the CPU is toast is unplug this HD and try a test install to another HD, or boot Partition Wizard bootable CD to shrink C to do a test reinstall of Win7 to see if it installs and runs. If you have 4 primary partitions you'll need to convert one to Logical using PW first so it doesn't convert the disk to Dynamic. Partition Wizard Move/Resize Partition Video Help.
How to set partition as Primary or Logical.
Dear Gregrocker,
I did monitor CPU temp with Speccy.
When I was rendering video, my temps went up to 70°C
Then I cleaned and vacuumed and temps went up to 60°C
So I set mobo to warn (beep) at 65° and shut down at 75°
Things went fine after that. Once in a while I ran over 65° (ONLY while rendering) and it beeped, but only for a very short time (1 second or less) So after monitoring temps for about 2 weeks, I thought I could trust the system. So last Saturday I had to render a videoclip, and left the computer alone. When I came back, I had the BSOD.
So the safety system worked, and shut down the computer. I have been using (only testing and try repairing) this computer now for about 3 days, it never crashed. I did not load windows, but all tests and repair progs worked just fine. So I'm quite sure that the CPU is OK. I also did the MEMTEST68 test during about 5 hours (tested 130% > one full + 30%) and didn't get any errors. I tried many things discussed on this forum, but none of them seemed to be able to restart my WINDOWS. As long I use Bootdisks, everything works fine, but loading WINDOWS from HD (safe mode or whatever mode) always takes me to the BSOD.
When I used Partition wizard, I could see all my directories, also the directory containing the WINDOWS folder. When I asked Partition wizard to make this partition the windows boot partition, It said that it couldn't find the windows folder ... ?
PS : The windows partition is on an SSD...
Again : I thank you for your interest and the time you spend to help me out. I really hope to get my computer working again without having to reformat/reinstall ...