NVIDIA GeForce 210 - Version 320.49 stopped responding and has successfully


Recommended Posts

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
 

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.

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.

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.

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 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.

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.

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.

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

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...

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. 

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

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.

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.

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)

 

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.

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.

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.

  • 4 weeks later...

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".

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.

This topic is now closed to further replies.
  • Posts

    • State of Decay 3 is out in 2027, reveals Plague Nests with new co-op gameplay trailer by Pulasthi Ariyasinghe A few months ago, Undead Labs broke its silence about the third entry in the State of Decay series since its announcement in 2020. Today, the studio had a brand-new trailer to reveal at the Xbox Games Showcase, finally giving players a look at the Unreal Engine 5-powered title. A broad 2027 release window is now attached to State of Decay 3 too. The studio confirmed that every scene seen in the gameplay trailer (except for the studio logo) released today is from the game with no cinematic footage. "The quality bar of the moment-to-moment experience is higher than anything we’ve achieved in Undead Labs’ history," says the studio. "State of Decay 3 is being built in Unreal Engine 5, and we’re creating better quality versions of what makes our game the survival sandbox it is, and the combat experience is really, really important to us, and I think you can see it coming through in this trailer." One new aspect of this upcoming entry is the Plague Nests. These are supposed to be dynamic, dungeon‑like enemy hubs with varied “personas” that change tactics each time one appears on a map. These areas will have the best loot in the game for players brave enough to tackle them. The combat system is being overhauled too, letting players do quick and power attacks depending on the situation. This isn't just on the player's side though, as zombies themselves now have multiple new types of behaviors depending on how fresh or decayed they are. "All of these play very differently, especially as you start getting outnumbered or when you’re making noise and running around and trying to save your rear end or the rear end of your friend next to you," adds the developer. Of course, settlement building and community management are massive parts of this third entry too. These are being further expanded with the cooperative focus, giving players much more freedom for playing together than in State of Decay 2. Players will even be able to split up and build settlements in different areas of the same map with different goals. Undead Labs confirmed that playtests are already ongoing for the title, and interested players can sign up to participate by heading over here once more slots open up ahead of the full release. State of Decay 3 is coming out on PC, Xbox Series X|S, PlayStation 5, and Xbox Game Pass sometime in 2027.
    • Doom: The Dark Ages Revelations expansion gives the Slayer a brutal Chain Spear by Pulasthi Ariyasinghe Last year, id Software released Doom: The Dark Ages as a prequel to its reboot series, offering a look at the legendary Slayer character during an ancient war between Hell and Heaven. Today, at the Xbox Games Showcase, id Software returned with a new announcement that unveiled Doom: The Dark Ages Revelations as its first story expansion. The expansion will see the Slayer being betrayed and cast into a "merciless purgatory only escapable by confronting haunting truths." Somehow, there is one ally in all this chaos seemingly attempting to help our protagonist escape his fate. Players will be ascending this prison and fighting plenty of new demons and abominations as they work to free the Slayer's followers. One new aspect of the expansion will be the Chain Spear. This new weapon is described by the studio as a "uniquely satisfying combat system that rewards mastery with a potent combination of power and mobility." Check out the trailer below to see the new weapon in action, where the Slayer is seen using it to even pin enemies to walls. id Software is also preparing a free update to all owners of Doom: The Dark Ages that will land alongside the new paid expansion. Dubbed the Ripatorium 3.0 update, this will add more customization options, an improved pass code generation system, and preset options for players diving into the game's arena challenge mode. Expansion buyers will also receive additional maps, demons, and new weapons to use in this mode in addition to the story levels. Doom: The Dark Ages Revelations expansion is out on July 7 across PC, Xbox Series X|S, and PlayStation 5 with a $19.99 price tag. Those who own the Premium Edition or the Collector's Bundle will receive the expansion for no extra cost as well.
    • Hyped for this. Replayed the remasters recently and they're so well done, and Crash 4 was great too. I trust this team to deliver.
    • Ninja Theory's new Hellblade game is action-focused and set in Purgatory by Pulasthi Ariyasinghe Ninja Thery has been building its award-winning Hellblade series since 2017, delivering Senua's Sacrifice and Senua's Saga since then. Today at the 2026 Xbox Games Showcase, the studio had a brand-new installment announcement featuring Senua again, but this time, she is in a version of purgatory, and the focus is on the action. Simply named Senua, this new entry is described as a "full-on action-adventure" experience, delivering an expanded focus on combat, puzzle-solving, and freedom of exploration. The developer says that it is keeping the same high production values and storytelling features of the previous games while giving what players have been asking for in the gameplay department. The entirety of Ninja Theory is now working on Senua, giving the project much more manpower than ever before, while also letting the team draw on its action roots from Devil May Cry and prior titles. However, the studio also confirmed that its previously announced Project Mara horror experience is no longer in development. Alongside snappier traversal moves, Senua will be able to take stealth and direct combat routes. She has access to her own sword, plus any enemy weapons as well, with dual wielding also being an option for most dropped melee swords, axes, and other weapons. Outside of melee combat, Senua will be able to use special abilities that let her alter the reality around her. The world is said to be about twice the size of Hellblade 2. While this won't be an open-world experience, the linear story will let players explore their surroundings further than before. The story of Senua will be set after the events of previous Hellblade titles, with our protagonist being stuck in her own version of Purgatory. The series' well-explored psychosis themes will return as well. "She’s trapped between life and death on a quest to reach the afterlife and be reunited with the ones that she’s loved and lost," adds the studio. "Her belief is that by healing the wounds of her life, she can find the peace that is the key that unlocks the gate to the afterlife." Senua is releasing on Xbox Series X|S, PC, and PlayStation 5 sometime in 2027.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      492
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      68
    5. 5
      ATLien_0
      67
  • Tell a friend

    Love Neowin? Tell a friend!