somegod wrote:

Man i ussually run linux on my pc but needed to run windows and this is what i got
Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.0.6001.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    f4
  BCP1:    00000003
  BCP2:    8683F288
  BCP3:    8683F3D4
  BCP4:    82054400
  OS Version:    6_0_6001
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\WINDOWS\Minidump\Mini071208-01.dmp
  C:\Users\somegod\AppData\Local\Temp\WER-128451-0.sysdata.xml
  C:\Users\somegod\AppData\Local\Temp\WER68C0.tmp.version.txt
yes the famous bsod aka blue screen of death, microsoft you need to get your self together and mke a better os.

Were you installing Vista, or just trying to run it after its been installed? If its the latter, make sure you have the SP1 version of the disc, and have the drivers ready to install. I don't know what else to add. Ask Powerslave, he probably would know what all of the codes mean.

Jsamp doesnt know what he is talking about so disregard his negativity.

Is it XP? You could always install tiny XP. Could prevent the BSOD and make install, boot up, and everything run faster sense your only using it for a little bit.

Its vista. Only vista has the directory C:\Users\ without you making it yourself.

Yeah im sure thats a hell of alot more stable than XP. Some fat ass copied XP's coding and made small changes to it and called it reactOS. Alot better than a multi million dollar cooperation.

Lol. Yeah i know. I get that alot. Okay but still like its gonna be more stable.

Of course, Microsoft doesn't care what your buying as long as you buy it - even if its unstable.

With small free projects like this, people are working their asses off to make sure it works best for everyone because THEY themselves are going to be using it.

Powerslave wrote:

You get the BSOD for many reasons, the most common being Errors with drivers, and bad motherboard resources, HARDWARE failures the CPU detects and flags an error state.   There are different types as well, the very TOP LEFT should tell you what happened, like "MACHINE_CHECK_EXCEPTION_FAULT" or something like that.

Somegod: I see you said your overclocked your CPU when that happened, so you did cause it.  You are blaming the O/S for your error, which the CPU sent to the O/S which is why it did that.  The CPU will send these errors to the Kernel, and the BSOD happens to prevent damage to your file system, or to the hardware.  Once the BSOD occurs, usually, everything is powered down, the HDDs park, and the CPU and all other hardware go into a low power state.   It can also be as simple as a voltage and/or overheating problem with the CPU due to the overclocking, which became abnormal, so the system was halted. 

The other BSOD is just one that says a problem has been detected and windows has been shut-down to prevent damage to your computer, with NO header at the top left, but this message is, with memory addresses.

Again, it can be something coincidental when you overclocked it.  The memory locations do not seem to point to ROM or other hardware addresses...  THe result of over clocking may be causing ram timing issues with some programs.

I only overclocked it by .2 gigahertz, which shouldnt do any damage i have over 9 fans in my case, it never over heats. and i did the same in linux and still nothing, it may have been other than overclocking but, that occured during my over clocking so i just think it needs to be a little more stable

haha ya, ima try the reactos soon. it interests me.

Mr.TurnSignal wrote:

I wouldnt. It looks UNSTABLE

He said it was working with Linux, it was WINDOWS that gave him the error.  As I said, Windows more closely monitors CPU status.  If the voltage is put of specs (as provide by the BIOS through the sensors), then it will bail.    Believe it or not, there are a kind of DRIVER it loads for a CPU, hos it identifies it, and the specs are provided by the MFR.  Overclocking will raise the vore voltage, no matter how cool you keep the CPU, the voltage will still go up.   EVEN so, the driver, per say, also should have what the clock speed is, and that may get flagged.

I do know instances where CPUs are ovwerclocked and are working just fine.  It all depends on the CPU itself, and what it reports and indicates.  They are making some CPUs specifically so you can't overclock them.  Though they probably are?  They are made not to, and would report a fault to windows if done.  If linux ignores the flags, it will continue to run.  It may not be safe for anything, but, he had it working nice till windows was installed, so that's the issue at hand.

snafupossum wrote:

nickb827 wrote:

Its vista. Only vista has the directory C:\Users\ without you making it yourself.

http://i36.photobucket.com/albums/e30/s … ersinc.jpg

Thats weird... Did you install the version with SP3 integrated on the disc?
And By the way, I love your signature.