Runes of Magic US / AU

Quoted from "GarryL;532988"

It may also be your PSU (power supply) that is at fault. A failing PSU will cause frequent reboots.

Quoted from "GarryL;532990"

It may still be your PSU because your graphics is drawing more power when it is under load. Nothing to do with how well things are plugged. It is one way that a failing or underpowered PSU can affect a computer. Not definate but certainly a possibility.

Quoted from "pazuzzu;533027"

go to my computer..right click and hit properties. under advanced system settings (skip that if not win7) hit startup and recovery. uncheck auto-restart. then you can catch the bugcheck bsod ID. if its rom faulting it wont be in the event logs.

when you reboot you can un-pack the dmp file and see what caused the fault directly if the bug code isnt informative

Quoted from "Kalvan;533021"

While AngelIsrafel's description can work, it can also incur a lot of work. You don't need to have the exact makes and models of your hardware components. You will need to know the CPU make and model, video card model, the type and number of system RAM modules that are installed in your computer, and the power output--in watts--of your PSU. (For OEM power supplies, do a search for your precise model and check the system specs. Most will show the PSU's output in watts.) Once you have that information, you can go here: http://www.msi.com/service/power-supply-calculator/

The first set of inputs require the precise make, processor modell, CPU core name, and core sub-model. You can ignore the CPU code.

The second set of inputs is for the video card vendor, model, and number of installed cards. Note that some model lines are unavailable, so choose the one that's closest to the one installed in your computer.

The next group of inputs are for optional PCI cards, PCIe-X cards, and various storage. Each of these draw power from the PSU, so select accordingly.

External devices: Count the number of USB or IEEE 1394 (Firewire) external devices which are connected and do not have their own power supplies--for example, most external HDDs and optical drives have a power brick of their own and do not draw power from the computer's USB/Firewire connection.

Memories: This is where you need to know the exact type of system RAM modules and the number which are installed.

Others: Lastly, the number of fans inside your computer and if you have a front bay card reader. Count the case fans and CPU fan, but not the PSU or GPU fans--the CPU fan is powered from the system board, the PSU and GPU fans are already taken into consideration.

Compare what the PSU calculator shows against the advertised nominal output of your PSU. The calculator will show the power draw at 80% load. I myself recommend having 80-100 watts of reserve power available, just to be on the safe side.

PSUs age and downgrade over time and the amount of usage--or abuse--they receive. Better-quality PSUs will last longer and take more abuse and strain than lower-quality PSUs. This includes OEM power supplies, which tend to be of average or lower quality.

And also do note that if you're using an OEM power supply in a computer which isn't marketed as a premium or gaming machine, chances are that the PSU is going to be a bit on the weak side, output-wise. Average industry standard for newer computers is approximately 350W. Older, and especially for "value" computers is 250-300W. YMMV here.

Quoted from "pazuzzu;533041"

you can try the event logs...applications. search for error. it will be under "windows error reporting" the code might be there but usually have to unpack the minidump

Quoted from "pazuzzu;533044"

right click my computer...hit manage. left side will have event logs. under windows-->applications just hit control-f to search and type "error". but like i said if it's rom causing the bsod it generally wont appear in the logs.

its possible the macair could draw too much current but highly doubtful...the lack of current would increase the perceived ohm load which would generate heat issues so you would notice pretty quick i imagine.

more than likely its just a display driver fault with something..happens enough.

Quoted from "pazuzzu;533055"

if you know the last time it happened roughly just go to windows folder/minidump and find the one created around that time. if its not in there it could be in windows/livekernalreports/watchdog

you can send it to me via pm if you like. unpacking them isnt pretty

Quoted from "pazuzzu;533060"

no..in the minidump folder is a type of file called a...minidump. whenever something crashes, and doesnt totally corrupt the kernel, it dumps the state of...everything...in a that file for debugging. you just have to find the one that was made at the time you had a bsod.