Edit metadata -> Bluescreen

[alfred.s]

Meanwhile, I tried the driver verifier and removed all reported drivers - no change.
Different versions of Nvidia driver - no change.

The computer is running and running. It only crashes sometimes while editing metadata.
So I probably have to live with it.

[theducks]

What kind (brand) of Mouse are you using?

What exactly part of the metadata were you editing at the crash point?

and Which drives are being used: (post the full path). Do the paths ONLY have ASCII names in them?

1) the Library
2) for TMP and TEMP (user environment setting)

[AnotherCat]

Originally Posted by alfred.s

Meanwhile, I tried the driver verifier and removed all reported drivers - no change.
Different versions of Nvidia driver - no change.

Have you tried disabling the NVIDIA Display Adapter in Device Manager, rebooting the PC and seeing if the problem persists?

You will, of course, get an ugly screen while you do so, but it may resolve whether it is the adapter or not.

[BetterRed]

@alfred.s - Its unlikely to be drivers - 10-20 years ago it might have been but not today.

Your HP computer is quite old - actually its a rebadged compaq system - things wear out, just like parts on cars and appliances.

I'll bet London to a brick on that the problem is the graphics card, no amount of software fiddling will fix it. Go to your local computer shop and buy the best graphics adapter you can afford, preferably with the ATI chipset - AMD cards are pretty good.

I've had it with NVIDIA bloat and pushing new drivers down my throat whenever they add support for their latest whiz-bang that I neither have nor want.

BR

[PeterT]

Any chance that the computer is overheating, and that there is a build up of dust?

Additionally, to get some analysis done of the dump file take a look at http://www.resplendence.com/whocrashed

[alfred.s]

Originally Posted by theducks

What kind (brand) of Mouse are you using?
What exactly part of the metadata ...
Do the paths ONLY have ASCII names in them?

Mouse: HP PS/2
Editing varies. Sometimes I do an internet search, sometimes I edit the book-series, sometimes I move to the next book, sometimes the edit-window is just open without any action.

Path to library: d:\ebooks\temp
TMP/TEMP: c:\users\alfred\appdata\local\temp

Originally Posted by AnotherCat

Have you tried disabling the NVIDIA Display Adapter in Device Manager,

Did not test this yet, because it scrambles my screen and desktop completely.
Almost unusable.

Originally Posted by BetterRed

Your HP computer is quite old - actually its a rebadged compaq system - things wear out, just like parts on cars and appliances.
BR

It's 3 years old and I use 10 of them for business and one privately for each family member. They are all a bit different in parts and OS (XP,Vista32, Win7-64) and they all run 24/7 without any significant problems.

Originally Posted by PeterT

Any chance that the computer is overheating, and that there is a build up of dust?

It's cleaner as my car. Definitely no overheat (monitored as well).

[alfred.s]

Just installed whocrashed. Maybe it helps.

[BetterRed]

Originally Posted by alfred.s

It's 3 years old and I use 10 of them for business and one privately for each family member. They are all a bit different in parts and OS (XP,Vista32, Win7-64) and they all run 24/7 without any significant problems.

Have you tried running your calibre on one of the other machines. Its easy to move calibre between machines. Install calibre on other machine, and copy your library(ies) and configuration data to the other machine.

Or, IMO a better alternative, you could install calibre portable onto a USB drive, copy your library(ies) and configuration into the calibre portable folder on the USB drive. You can then test the USB install on your machine and a couple of the others. If it crashes your machine but not the others then its your machine or system software. If it crashes other machines then it's the calibre software or the calibre data, i.e. libraries or config or a combination thereof.

BR

[theducks]

you might try using a different (very short) TMP/TEMP path, but this issue usually only affects really long author-title names (excessive characters in a path)

[alfred.s]

Got a little closer to the solution: Whocrashed reports in most cases "vsdatant.sys" to cause the crash. Goggle shows many posts regarding "vsdatant.sys" and bsod.

Right now, ZoneAlarm ist deinstalling. I will keep you informed, if it helps.

[alfred.s]

I think, I got it. Till now, no more crashes since I removed ZoneAlarm.
Still, not 100% sure. But I will keep you updated.

[BetterRed]

Originally Posted by alfred.s

I think, I got it. Till now, no more crashes since I removed ZoneAlarm.
Still, not 100% sure. But I will keep you updated.

for keeping the community informed and kudos to PeterT for identifying the right diagnostic tool.

BR

[theducks]

Originally Posted by alfred.s

I think, I got it. Till now, no more crashes since I removed ZoneAlarm.
Still, not 100% sure. But I will keep you updated.

Thanks for the report.
Wow, the ultimate tool for protecting your computer: If in doubt: BLUE SCREEN IT


For those Windows XP an higher users that miss it: Microsoft (Sysinternals) offer the Bluescreen screen saver
http://technet.microsoft.com/en-us/s...rnals/bb897558


the first time it fires off while an IT type is walking by

[alfred.s]

No more BSODs - Great!
THX to everybody!