Danielsan
11-04-07, 11:04 AM
I have never had such an error untill 3 days ago when I tried the DX10 version of Hellgate Londonīs demo, then WoW inhereted the error and started producing it too. I rebooted with no effect, actually I had to unplug the powerchord for 30 secs after which the error was gone. Have played untill today with no problems, I decided to give the Hellgate London game another shot .. and voila .. the error was back.
Just for the kicks I gave WoW a shot and it started giving me errors as well, I once again removed the powerchord and things seem to be back to normal.
My neighbour however has had this error far more frequently, his system seems pretty identical to mine and we both have all the MS patches including latest drivers, dx10 etc. installed.
So, my best estimate is that some people will hardly ever see this error, while others fight with it frequently and the probably most annoying aspect is that no solution will be found within the nearest future if the error is caused by certain random call procedures. To identify the faulty call procedures responsible for the error would take a long long time, especially if they come from various firewalls, antiviruses, antispyware or any other background software running.
Motherboards which have a steady supply of power to USB and PCI devices regardless of whether the PC is shut down, mine always supplies the USB/PCI devices with power and there is no way to turn it off. If a wrong call procedure somehow destabilises the power to the various circuits one could continuously get the error untill the power is fully unplugged and depending on motherboard a bios reset could perhaps be the only viable solution.
In my case Hellgate London may not actually be the culprit, it could be the interaction between certain peripheral devices and/or software running in the background which cause the application to behave abnormally.
I am not an expert but I have looked at over 50 pcīs with this very issue and I am quite convinced that the 8800s have an error which is small in nature and will only surface under certain circumstances. I have also met quite a few people who never had the error, blamed others for bad handling of their PC .. and all of a sudden they were fighting the Nvlddmkm problem themselves.
Well, there is already another thread but I chose to make mine .. if that offends anyone sorry, but its one of the few priveligies a guy has on the internet now adays :) .... sue me.
Just for the kicks I gave WoW a shot and it started giving me errors as well, I once again removed the powerchord and things seem to be back to normal.
My neighbour however has had this error far more frequently, his system seems pretty identical to mine and we both have all the MS patches including latest drivers, dx10 etc. installed.
So, my best estimate is that some people will hardly ever see this error, while others fight with it frequently and the probably most annoying aspect is that no solution will be found within the nearest future if the error is caused by certain random call procedures. To identify the faulty call procedures responsible for the error would take a long long time, especially if they come from various firewalls, antiviruses, antispyware or any other background software running.
Motherboards which have a steady supply of power to USB and PCI devices regardless of whether the PC is shut down, mine always supplies the USB/PCI devices with power and there is no way to turn it off. If a wrong call procedure somehow destabilises the power to the various circuits one could continuously get the error untill the power is fully unplugged and depending on motherboard a bios reset could perhaps be the only viable solution.
In my case Hellgate London may not actually be the culprit, it could be the interaction between certain peripheral devices and/or software running in the background which cause the application to behave abnormally.
I am not an expert but I have looked at over 50 pcīs with this very issue and I am quite convinced that the 8800s have an error which is small in nature and will only surface under certain circumstances. I have also met quite a few people who never had the error, blamed others for bad handling of their PC .. and all of a sudden they were fighting the Nvlddmkm problem themselves.
Well, there is already another thread but I chose to make mine .. if that offends anyone sorry, but its one of the few priveligies a guy has on the internet now adays :) .... sue me.