Continued from:
A quick look at the installed nvidia control panel setting gave me something to check:
The PhysX GPU acceleration was turned ON! (for what Ray Sum needs the laptop for this wouldn't be needed, technically is for working out where things in graphics heavy software will move to i.e. video processing but mainly gaming when you shoot a box and it should bounce around!)
The PhysX GPU acceleration was turned ON! (for what Ray Sum needs the laptop for this wouldn't be needed, technically is for working out where things in graphics heavy software will move to i.e. video processing but mainly gaming when you shoot a box and it should bounce around!)
After changing the setting the system started showing a different blue screen message (mainly accessing incorrect memory address hmm?!)
Whilst doing this I'd thought hmm maybe the "Direct X" was out of date?
Ran it using 'Window Key' + 'Run' then typing into 'dxdiag' couldn't be bothered finding the actual exe in its usual home in the Program Files folder. Whilst this gathered the required information the system crashed a number of times.... (blue screen and gabled text, see next post!)
The following are photos of the built in windows "Action Center" showing problems and possible solutions!
Note that windows also believes that the fault is down to the GPU and that the system isn't particularly reliable (you don't say!)
Whilst doing this I'd thought hmm maybe the "Direct X" was out of date?
Ran it using 'Window Key' + 'Run' then typing into 'dxdiag' couldn't be bothered finding the actual exe in its usual home in the Program Files folder. Whilst this gathered the required information the system crashed a number of times.... (blue screen and gabled text, see next post!)
The following are photos of the built in windows "Action Center" showing problems and possible solutions!
Note that windows also believes that the fault is down to the GPU and that the system isn't particularly reliable (you don't say!)
No comments:
Post a Comment