BlueScreen on windows vista

[demone]

Hi I'm getting from time to time some bluescreens when compiling.

The first blue screen I get was when i tried to build (and rebuild) several libraries (irrlicht, boost, ogre... I'm speaking about compiling! not using)
I was thinking that the problem was just the MultyThread compiling (I was using 4 threads since I have a quad core).

So I disabled it. But today again 2 bluescreens when compiling. So here's a summary of the problems:

--When compiling with multiple threads the problem is very curious.

1) Some C::B /mingw process is not correctly terminated, and still running after the compile has ended OR aborted OR C::B closed. (so one or more cores are used up to 100% by processes wich are doing nothing (theorically))
2) Closing windows/ sometimes just closing C::B causes a blue screen (a system process has been terminated in a unusual way).

--When compiling with a single thread

1) aborting compilation can cause a blue screen

I'm not using PCHs.

I have window Vista latest update.
EDIT:
Also wanted to note that my Antivirus programm was disabled when compiling (I know antiviruses can cause problems sometimes so I put it off every time i start a programming session).. and wanted also to note that my antivirus marks "mingw" stuff as very dangerous (that's why i close the antivirus program ).

EDIT2:
of course i'm using code::blocks 10.05 (I tried both the mingw version shipped with c::B and the last stable mingw release both causes bluescreen
so maybe there's something in code::blocks since compiling from console works fine and also using GNUmake works).
I have by default 2 accounts on my pc . one with the c::B + shipped mingw and one account with the custom c::B setup with the latest mingw stable package

[oBFusCATed]

No userspace can crash your OS, this is
1. driver problem
2. stability problem (overheating, broken/fat capacitors or something like that)
3. problem with you hard driver (click of death, bad sectors, etc)

For 2. just try a torture test program, like IntelBurnTest, prime95, Linx or something similar.
If you have overclocked your pc, remove the overclock and try again, keep in mind that
compiling is very heavy process.

[demone]

No userspace can crash your OS, this is
1. driver problem
2. stability problem (overheating, broken/fat capacitors or something like that)
3. problem with you hard driver (click of death, bad sectors, etc)

For 2. just try a torture test program, like IntelBurnTest, prime95, Linx or something similar.
If you have overclocked your pc, remove the overclock and try again, keep in mind that
compiling is very heavy process.

well the pc I'm using for developing is very clean I don't think it has problems. I just have 1 browser, antivirus program, Ccleaner, c::b + needed libraries (8 libraries included ogre,boost and irrlicht) and my projects (3 actually). And the last time I formatted the pc it was 5 months ago.

And I'm not a fan of overclocking so overclocking is disabled.  (I know that some machines do overcloking automatically when needed but mine not and I will not overclock my machine)..

I tried intelburn test anyway Linpack at maximum stress level succeded... what else can be?

EDIT:

I rebooted the PC and runned scandisk on C and D. no problem founds. I think also that drivers are up to date and ok.

[oBFusCATed]

I rebooted the PC and runned scandisk on C and D. no problem founds. I think also that drivers are up to date and ok.

Scan disk is useless. You should try a surface testing program. HyrenCD has many such programs.

p.s. If your cpu cooler is filled with dust it can cause overheating. Clean you PC, too.
p.p.s. You should run intelburntest for 20-60 minutes at least.

[demone]

I runned intel burst for more than 40 minutes.. the temperature probe detected 58 C° (CPU temperature) after intel burst. Usually when developing I spend most of the time writing code and sometimes compiling so when compiling i rarely go above 45-50 C°.. I think that this should be ok (unless also my temperature probe is broken. when not compiling I'm under 40 C°

If you have windows vista (32 bit) have you just tried to compile for example irrlicht (there is a code::blocks project inside source folder) and try to abort compiling when it is about at an half? (Aborting compiling on small projects doesn't cause blue screen).

I convinced my friend to reproduce the bug on his laptop (first I had to bluescreen my computer to show him that bluescreen is not irreversible damage .. mwahahah). Also his computer bluescreened (and now if his PC will break up I don't know if he will ask for refund XD).

Wich is the chance that this is an issue of my PC?

[ollydbg]

I'm using C::B under Windows for more than 2 year. No bluescreen happened.
I guess your system or some hardware problem, it is strange that you friend can reproduce your problem....

[oBFusCATed]

demone:
C::B is a userspace probgram, there are no drivers in it.
The compiler you use is the same. No drivers in it.
Both programs use the OS APIs to communicate with the hardware.
So both programs can cause BSOD on their own, but drivers could.

The process of compiling is extremely heavy on the hardware, because it stresses all subsystems: CPU, disk subsystem.
I've seen my system crash under heavy compilation and later it turned out that my system is not stable. The OS is not so important.

How many threads are you using for your compilation? Try with only 1 if you use more.
Have you tried with to see if your hdd is OK, using a surface test program?

Have you tried IBT on your friends laptop? I guess it overheat as some of the laptops are not meant for heavy load.

[demone]

...
I was thinking that the problem was just the MultyThread compiling (I was using 4 threads since I have a quad core).

So I disabled it.
...

as previously sad i'm using just 1 thread for compiling. (after found that multiple threads are not very stable)

I tried the surface test and is ok..

Has anyone tried at least to abort a very long compile task on Vista? (10 or more minutes of compiling for a single target).
I tried to do the same on my old winXP and I have no troubles. maybe it is an issue of Vista?

@ollydbg: i'm trying to follow oBFusCATed instructions for find what is wrong, and my friend plays rage at high details on his laptop so he is probably have heating problems with newest GTX inside). Have you vista too?

[ollydbg]

@ollydbg: i'm trying to follow oBFusCATed instructions for find what is wrong, and my friend plays rage at high details on his laptop so he is probably have heating problems with newest GTX inside). Have you vista too?

I'm on WinXP.
I have used Vista before. I found that Vista's harddisk IO speed is too slow. When build a large project, it takes one times longer than build on XP.

[reckless]

Vista can be a bit quirky in places but is generally very stable. If you know how to tweak services you can boost its performance quite a deal by turning of indexing (slower searches but way faster disk io) search tweaks for vista.
As for BSOD's its newer easy to find out what causes it but compilers dont they may stress the system though so it triggers a fault but the cause is allmost 100% certain to be somewhere else. As an example i can tell you i been fighting for years with my gfx card causing lockups and black screen o deaths, i replaced every piece of hardware including the gfx card and it didnt work. Turned out to be a bad monitor so even when something seems obvious (likely a broken gfx card) it might not be that. The only advise i can give is if you dont have a massive amount of hardware to replace from, start with something minimal (mainboard cpu + ram and gfx card) try first with one stick of ram and if stable plug in more sticks. Continue with whatever piece of hardware you have (one at a time) untill it becomes unstable, and you most likely found the cullprit.

[MortenMacFly]

We are no forum for computer problems -thus, I am locking this topic now. To summaries: C::B cannot be the cause for  a blue screen as it runs in user space (as oBFusCATed said already). I may be the trigger, but the actual problem lies elsewhere.