Dubstepforum.com

I hate when this happens, for what ever reason it may be.. Thank god DAW's have auto recovery via Undo saves :3 gehe..

Never. How do you do that with a DAW?..

Blue screens are usually a hardware configuration error.

mks wrote:Blue screens are usually a hardware configuration error.

Well when your maxing CPU usage to high, that your CPU can't handle it, it goes into a bitch fit and BSOD's

SMOR3S wrote:

mks wrote:Blue screens are usually a hardware configuration error.

Well when your maxing CPU usage to high, that your CPU can't handle it, it goes into a bitch fit and BSOD's

Definitely a hardware issue. If things are working fine your CPU should not be causing BSODs just because it's being maxed out.
This is why when you buy an actual computer built for recording audio the better companies will actually stress test each build to insure things like this don't happen because of a hardware issue.

Yeah a blue screen is a pretty serious error these days - as others have said it's possibly a hardware issue. Are you producing on a laptop? Does it have adequate ventilation? Have you changed default voltages or speeds?

I've never got blue screened while making music, but I got blue screened while coding like 2 times

What version of DOS are you using?

never? this thead is....

This is why you stress test your build once you build it. If you get BSODs then something is wrong and you go sort it out. It should be part of your building process imo especially if you're doing any tweaks such as overclocking

countless!

not so much these days though

Not since about 2002 I don't think.

Can't remember the last time I saw a machine (any machine) BDOS if I'm being honest

My work comp used to do it all the time. It was in a really dirty environment though so I'm sure that had something to do with it. Aside from that I haven't seen a BSOD in over 10 years on any of my comps.

I switched over to Mac about 2 years ago and haven't had any problems. Although I have no idea what the equivalent to BS is on a Mac...

Brothulhu wrote:This is why you stress test your build once you build it. If you get BSODs then something is wrong and you go sort it out. It should be part of your building process imo especially if you're doing any tweaks such as overclocking

Yep! There's lots of tools available out there to do the job. If you are investing countless hours on your recording PC then it is definitely worth taking that extra step! Currently using my PC that I built for gaming to record on until I can afford to build another dedicated PC. Have not had a single BSOD yet. I'm also running Windows 8 Pro with zero issues! No more firewire/wifi stack issues, yippee!

Its not necessarily related to hardware, it happens to me a lot on one of my laptops. For me it tends to be when I've installed new software when it happens. All I know is that when I delete the software it stop doing it.

goldengrime wrote:Its not necessarily related to hardware, it happens to me a lot on one of my laptops. For me it tends to be when I've installed new software when it happens. All I know is that when I delete the software it stop doing it.

Ya it's not my hardware.. I used to be an avid overclocker, so I know what settings are what.... I am pretty sure it's my Scarlett 2i2 maybe, cause at times when I get High CPU load in Ableton, once in a while, my Ableton will freeze, the CPU meter will stick, and my Asio driver in my tool bar will turn "red"... I have tried unplugging the USB cable from my AI, and then trying to plug it back in, but once I go to unplug it, I BSOD LOL!

^ your soundcard IS hardware fool

£10 Bag wrote:^ your soundcard IS hardware fool

Well I meant internal hardware, but I see what you did there

SMOR3S wrote: Ya it's not my hardware.. I used to be an avid overclocker, so I know what settings are what....

Knowing what settings are what doesn't really mean anything if it's still unstable. Your settings can be perfect but if you don't have enough cooling, have some faulty hardware etc. they still will cause issues