Nvidia BSOD problems

I'm actually not on onboard,I'm still with my 8400. I haven't time to pull it out and try with onboard.

I think you should try the onboard first. Good advice by Jonathan.

If that doesn't fix it, there is one other thing I'd look at that I haven't seen mentioned here yet: your camera software from Vimicro products. The corresponding exe (vm305_sti.exe) seems to have caused some crashes and loads of warnings.

Also, take a look at MSE and make sure it is updated. I see 2 fake driver files (from MSE) where there should be only one.

Your Hardlock driver from Alladin is too old (2005). there is newer here: Aladdin Knowledge Systems: Support

These are the drivers for the camera, delete or check to make sure you've got a W7 compatible one:

usbVM305.sys Thu Mar 08 12:05:31 2007
vvftav.sys Sat Jun 23 07:52:58 2007

As Jonathan already said, make sure you get rid of sptd.sys...

Hello Mvdb,thanks for posting.
Things that I done:
Updated driver for the camera. The latest that I found was from 2007(15.06.2007),and installed it.
Updated Hardlock driver with the latest from the web site.

For question about that 2 drivers from my camera. I don't found drivers compatibility with Windows 7. In folder downloaded with drivers there is only XP folder. It seems to be that XP drivers are running with Win 7.
I was made a seach on Google for that 2 drivers,and according to this usbVM305.sys there is no Windows 7 support.
Also for the vvftav.sys,there is no Win7 support.
Should I delete them ?

For the onboard chipset. I'll see if anything happen today(BSOD/random reboots),I'll go with onboard. If there are no problems,I'll wait out one more day.

StalkeR said:

I just finished Ram memory testing with MemTest,SFC ( it found some errors and say that repair them)

Which RAM test?
Windows RAM test or memtest86+?
Try this tut: RAM - Test with Memtest86+


If SFC found errors and said it would fix them, you will usually need to run it a couple more times so it can fix all the errors. It usually takes more than once.

Yes,I'm testing memory with MemTest86+. And SFC said that some errors were found,but it successfully repaired them. If you need more info about that error,I can post here the CBS file.

This f**king card is making me furious....
While was working I got that error,Display driver nvlddmkm stopped responding and has successfully recovered.
Here is from Event Viewer.

Attachment 172901

What else can we do? We've tried everything driver-related; we are left with hardware. Most likely, the card itself is bad, but if that continues under the onboard graphics, we know there is something else happening.

Jonathan_King said:

What else can we do? We've tried everything driver-related; we are left with hardware. Most likely, the card itself is bad, but if that continues under the onboard graphics, we know there is something else happening.

I agree, but haven't seen the full results of memtest yet? Have 5-7 passes been finished?

+... before definitely blaming hw... I'd like to see a day or two in Safe mode /w networking. If it remains stable then... it might not be hw.

Hello guys. Tommorow(I mean today) I'll go with onboard graphic,and I'll see. For the memtest 2 passes have done,and no errors were found.
For running in safe mode with networking,I don't know about that...

I agree with Jon and Mvdb, switch to the onboard graphics and see how that runs.

But first, run memtest86+ for a full 7 passes. Best to let it run overnight while you sleep.
You can stop the test if you get any errors.