NVIDIA GeForce 210 - Version 320.49 stopped responding and has successfully

[ConfusedFusion]

Hello All,

 

I just got a desktop assembled (Intel i5-3330 CPU, Board: Intel DB75EN, Windows 7 32 Bit, RAM: 4GB DDR3, Transcend), for general home use. I got a NVIDIA GeForce 210 video card along with that. 

 

I get this error every few minutes:

 

"Display driver NVIDIA Windows Kernel Mode Driver, Version 320.49 stopped responding and has successfully recovered"

 

After which I get a BSOD. 

 

I have the latest drivers installed. I have tried the forums, nothing has been of much help.

 

Should I get a better graphics card instead?

 

-CF

 

[Phouchg]

You should put it in another computer and see if the card is faulty (most likely).

Meanwhile use the integrated video and maintain heavy load to push the limits (memtest, Prime95).

 

If it's a generic no-name, might try swapping the power supply.

[ConfusedFusion]

 

 

Thanks for that suggestion. Will try it out/

[Top Qat]

I have seen reports that v320.49 doesn't play well with older hardware.

It gave me a few issues (screen flicker, stuttering) on my Gigabyte GTX 460 (1GB).

I went back to v314.22 and everything is working ok. See if that helps.

[PGHammer]

I have seen reports that v320.49 doesn't play well with older hardware.

It gave me a few issues (screen flicker, stuttering) on my Gigabyte GTX 460 (1GB).

I went back to v314.22 and everything is working ok. See if that helps.

The issue is indeed more common with GeForce 400 series and derivatives, though there have been complaints from GeForce 500 series, 600 series, and even current (7xx) series owners as well.

 

I have a GTX 550 Ti, and the 320.49 betas (and the later now-current 326.01 WHQL Forceware release) have been as painless a set of drivers as I have ever used - and I'm coming from AMD (where I had had largely NO issues with Catalyst, and that goes back to the original 3D Rage graphics chipset).  As to why this long-time fanATIc went Green, it can be summed up rather succinctly - price, price, price.  This GTX 550 Ti (refurbished) cost me $63.49USD, including taxes.  Had an AMD HD5770/HD6770 been available for the same price, in the same condition, I would have pounced on it.  So it's not about issues with AMD, for the simple reason that I didn't have any.

[Dark-Heart]

I have a Gigabyte GTX 560Ti OC and I had the same problem with the 320.49 drivers... From what I have seen on various other websites it seems the 320 series of drivers have major issues with some graphics cards. So I reverted back to the 314.22 and so far I have had no issues with these drivers.

[Dark-Heart]

I have a Gigabyte GTX 560Ti OC and I had the same problem with the 320.49 drivers... From what I have seen on various other websites it seems the 320 series of drivers have major issues with some graphics cards. So I reverted back to the 314.22 and so far I have had no issues with these drivers.

I have had a proper look through the windows logs and it seems to be caused by nvlddmkm, which is a component of the Nvidia drivers. If you random lock ups or BSOD or sometimes get the message 'Display driver NVIDIA Windows Kernel Mode Driver, Version 320.49 stopped responding and has successfully recovered' pop up.

 

Check your system logs for this message...

 

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video5

!06d7(2648)

 

If you do have these issues reinstall the 314.22 drivers make sure to select 'Custom (Advanced), once opened click the Perform a clean installation check box' as this will uninstall the 320.49 drivers properly. Custom (Advanced) also allows you to select what components of the Nvida drivers you wish to install too.

[Dark-Heart]

Latest news... I have been onto Nvidia website and they have just released 326.19 (Beta drivers). I have not installed them so can't comment on how well they work yet, I will wait until they go WHQL certified first. If any one has installed them please leave a post on here, informing how well they work etc.. thanks.

[Shasoosh]

Funny, google sent me here after googling the error in the topic plus 326.19. Just got it with my new GTX760. 

[Dark-Heart]

Funny, google sent me here after googling the error in the topic plus 326.19. Just got it with my new GTX760. 

Well it's nice to see Google works then... obviously the 326.19 drivers also has some issues like the 320.49 drivers. I was thinking of buying a new graphics card; now it just might have to be a AMD 7850 instead of the GTX 660, that I was thinking of buying.

[tsupersonic]

The issue is indeed more common with GeForce 400 series and derivatives, though there have been complaints from GeForce 500 series, 600 series, and even current (7xx) series owners as well.

 

I have a GTX 550 Ti, and the 320.49 betas (and the later now-current 326.01 WHQL Forceware release) have been as painless a set of drivers as I have ever used - and I'm coming from AMD (where I had had largely NO issues with Catalyst, and that goes back to the original 3D Rage graphics chipset).  As to why this long-time fanATIc went Green, it can be summed up rather succinctly - price, price, price.  This GTX 550 Ti (refurbished) cost me $63.49USD, including taxes.  Had an AMD HD5770/HD6770 been available for the same price, in the same condition, I would have pounced on it.  So it's not about issues with AMD, for the simple reason that I didn't have any.

320.49 is the latest WHQL, and 326.19 is the latest Beta...I've had zero issues on 320.49 with my Gigabyte GTX 560 Ti on Windows 8.1 x64

[Dark-Heart]

320.49 is the latest WHQL, and 326.19 is the latest Beta...I've had zero issues on 320.49 with my Gigabyte GTX 560 Ti on Windows 8.1 x64

320.49 was a beta driver then later Nvidia had them WHQL certified...

[tsupersonic]

320.49 was a beta driver then later Nvidia had them WHQL certified...

Yes I know that. I was more referring to PGHammer's statement of 326.01 WHQL drivers, which don't exist. 

[Dark-Heart]

According to this post the 326.19 beta drivers include the 326.01 WHQL drivers. The 326.19 beta is supposed to be for is Windows 8.1 Preview.  https://www.neowin.net/news/nvidia-releases-new-geforce-beta-driver-for-windows-81-preview

[Shasoosh]

326.29 Beta are out. Testing them out now.

[Dark-Heart]

326.29 Beta are out. Testing them out now.

Really... just had a look on the Nvidia website no mention of them on the .co.uk and .com site.

[spikey_richie]

Go to Control Panel > nVidia Control Panel > PhysX > Change the drop-down on the right from Auto to your 210, apply and close.

It happens because the PhysX engine doesn't work well with the embedded gfx controller in the CPU. I've had your exact problem 3 or 4 times, and every time the fix is as above. You'll find when you update your drivers, the setting MAY revert back to Auto so it's worth going back in every now and then and checking it's still set to your 210.

 

HTH.

Really... just had a look on the Nvidia website no mention of them on the .co.uk and .com site.

 Download and use the nVidia Experience app, they'll shop up in there.

[Max1894]

Just made an account to throw my 2 cents in here. I updated to the newest 326.19 beta drivers and had issues overnight last night. I ran memtest86+ just to rule out a memory issue of some sort and it came back clean. Now, I suspect that the recent 32x.xx series of drivers dont play nice with older graphics cards (ie 400 series and 500 series). I've run each driver released since 314.22 and each one had the same issue ("Event ID 14 from source nvlddmkm"). Now, I'm still testing out 326.19 to see if it's an issue with overclocking, some miscalibrated setting, or otherwise an issue on my end, but from what my own experience (and what Ive seen around in other forums) it seems that 314.22 is the last useable driver for pre-600 series cards.

[Max1894]

Just made an account to throw my 2 cents in here. I updated to the newest 326.19 beta drivers and had issues overnight last night. I ran memtest86+ just to rule out a memory issue of some sort and it came back clean. Now, I suspect that the recent 32x.xx series of drivers dont play nice with older graphics cards (ie 400 series and 500 series). I've run each driver released since 314.22 and each one had the same issue ("Event ID 14 from source nvlddmkm"). Now, I'm still testing out 326.19 to see if it's an issue with overclocking, some miscalibrated setting, or otherwise an issue on my end, but from what my own experience (and what Ive seen around in other forums) it seems that 314.22 is the last useable driver for pre-600 series cards.

 

Literally 20 second after making this post, my pc locked up again, but this time it actually crashed and restarted itself (which was a first). I'm just going to go ahead and say that it's probably avoid the 32x.xx series of drivers for oder gen cards unless you want headaches and hastle :pinch: I'm probably going to roll back my drivers later today to 314.22. Oh, if anyone is intrested, I suggest you follow the guide posted on overclock.net for doing a completely clean install of the drivers (http://www.overclock.net/t/1150443/how-to-remove-your-nvidia-gpu-drivers)

[seta-san]

 

Hello All,

 

I just got a desktop assembled (Intel i5-3330 CPU, Board: Intel DB75EN, Windows 7 32 Bit, RAM: 4GB DDR3, Transcend), for general home use. I got a NVIDIA GeForce 210 video card along with that. 

 

I get this error every few minutes:

 

"Display driver NVIDIA Windows Kernel Mode Driver, Version 320.49 stopped responding and has successfully recovered"

 

After which I get a BSOD. 

 

I have the latest drivers installed. I have tried the forums, nothing has been of much help.

 

Should I get a better graphics card instead?

 

-CF

 

install the 114.22. The bug is known and they are working on it.

[PGHammer]

Go to Control Panel > nVidia Control Panel > PhysX > Change the drop-down on the right from Auto to your 210, apply and close.

It happens because the PhysX engine doesn't work well with the embedded gfx controller in the CPU. I've had your exact problem 3 or 4 times, and every time the fix is as above. You'll find when you update your drivers, the setting MAY revert back to Auto so it's worth going back in every now and then and checking it's still set to your 210.

 

HTH.

 Download and use the nVidia Experience app, they'll shop up in there.

You mean GeForce Experience -  it is out of beta and included with all Forceware drivers (opt-in).

Just made an account to throw my 2 cents in here. I updated to the newest 326.19 beta drivers and had issues overnight last night. I ran memtest86+ just to rule out a memory issue of some sort and it came back clean. Now, I suspect that the recent 32x.xx series of drivers dont play nice with older graphics cards (ie 400 series and 500 series). I've run each driver released since 314.22 and each one had the same issue ("Event ID 14 from source nvlddmkm"). Now, I'm still testing out 326.19 to see if it's an issue with overclocking, some miscalibrated setting, or otherwise an issue on my end, but from what my own experience (and what Ive seen around in other forums) it seems that 314.22 is the last useable driver for pre-600 series cards.

As I stated, I have a GTX550 Ti (refurbished) and I haven't had a lick of trouble.

 

Not in Windows 8, 8.1 Preview, or Server 2012R2 (yes - same drivers).

 

The issue may well top out with the GTX400 series and GTS (not GTX) 500 series.

 

It's why I have asked about overclocking - I run my TI dead-stock.

[Iron Mew]

After updating the drivers for my GTX560 I was getting constant crashes. Got here from a Google search for the "06d7(2648)" error. I thought I'd make an account for anyone who might have the same problem in order to point out that the following:

 

Go to Control Panel > nVidia Control Panel > PhysX > Change the drop-down on the right from Auto to your 210, apply and close.

It happens because the PhysX engine doesn't work well with the embedded gfx controller in the CPU. I've had your exact problem 3 or 4 times, and every time the fix is as above. You'll find when you update your drivers, the setting MAY revert back to Auto so it's worth going back in every now and then and checking it's still set to your 210.

 

...doesn't work. I did that and the crashes just kept on happening.

 

I did, however, solve the problem by downgrading to the 314.22 drivers.

 

GTX560 (non-TI) on an Asus P5K with a Q6600, running Windows 7 x64.

[mediator]

1. This has nothing to do with nvidia drivers. It is a recent malware which attacks the display. You can remove it => http://www.tomshardware.co.uk/faq/id-1691891/removing-malware-proven-completely-remove-bitcoin-mining-malware.html

 

2. After the scan with anti-malware, you should remove it from the startup entry as well => cmd.exe -> msconfig -> startup -> tsiVideo  (remove this tsiVideo entry)

 

3. Remove everything from "C:\Users\Your_username\AppData\Local\Temp\iswizard" or perhaps "C:\Users\Your_username\AppData\Local\Temp\"

 

4. Reboot and see if entries are still being created in "C:\Users\Your_username\AppData\Local\Temp\iswizard"

 

I hope this helps. Basically the malware executes through rundll32.exe a dll called "tsivi232.dll" with the entry name "tsiVideo".

[trieste]

Another possible fix is enabling "Use software rendering instead of GPU rendering" in Internet Options.

[Circaflex]

1. This has nothing to do with nvidia drivers. It is a recent malware which attacks the display. You can remove it => http://www.tomshardware.co.uk/faq/id-1691891/removing-malware-proven-completely-remove-bitcoin-mining-malware.html

 

2. After the scan with anti-malware, you should remove it from the startup entry as well => cmd.exe -> msconfig -> startup -> tsiVideo  (remove this tsiVideo entry)

 

3. Remove everything from "C:\Users\Your_username\AppData\Local\Temp\iswizard" or perhaps "C:\Users\Your_username\AppData\Local\Temp\"

 

4. Reboot and see if entries are still being created in "C:\Users\Your_username\AppData\Local\Temp\iswizard"

 

I hope this helps. Basically the malware executes through rundll32.exe a dll called "tsivi232.dll" with the entry name "tsiVideo".

 

Incorrect, it does have a lot to do with the new nVidia drivers, there are many reports the new betas are more geared towards the 700 series, older cards have trouble. I had nothing but problems with my 670s so i reverted back to last released stable and its no longer a problem. This was on a fresh install, so no it wasnt some bitcoin malware.