I did allow malwarebytes to fix the open command, and rechecked it today, it is still in its fixed state, but 10 mins after startup, I received my second 'kernel data inpage error' blue screen. Interestingly avast did not detect this registry modification using its own full scan option (I used avast just before I started malwarebytes).

The options in malwarebytes to scan:

-memory objects

-startup objects

-registry objects

-file system objects

-additional items against heuristics

Malwarebytes does not detect the uncorrected registry change if I set it to only scan 'registry objects'. Ive tried most of the above alone, so im assuming it must be picked up from either file system or additional items?

after I read some malware forums stating that Iolo System Mechanic was one of the only pieces of legit software that modified this value (adding the quotes), with admin mentioning that its an obvious vulnerability, I thought it couldnt be a false positive.. but Im sure there still a chance. As a test, I have kept this value to its modified good/fixed state with the quotes in the registry, but no blue screens as yet. Quite a surprise, since I received one late last night and 10 mins after startup today. If I do get a third blue screen, or if some programs stop working correctly I will restore to its 'bad' state to see if it makes a difference. Failing that, a system restore. Ive noticed a 'kernel data inpage error' blue screen may also be related to hardware as well as software. Perhaps reading event viewe/systems report or similar just before the system gave up might give a better indication of exactly what the problem is. thanks for your replies :)