Blue Screens happen, even on Parallels!
Yesterday while I was writing some documentation on the source code of the Data Persistency library I’m working on, for the first time I had the bad feeling that Windows, running freely on your PC as running “parallelized”, will never change.
A “BAD_POOL_CALLER” has frozen my development virtual machine, even if (fortunately) there were no loss of data.
Windows, after a good reboot, was as good as new, even if I had to wait for a complete dump of the memory. I strongly suggest you never to shut down the PC when a Blue Screen appears: maybe I was unlucky, but the only time I did, Windows was dead! :(
I should really start moving away from .Net and C#, but there are good things in it. I evaluated Java, but in these days I’m so snowed under thousands of things to do that I prefere to end what I’ve started, more than rebuilding everything from scratch. One day I will start analyzing Java in depth (well, it won’t be this big deal… C# is VERY similar to Java)Â in order to be able to get rid of all the virtual machines, using my small White Jewel macBook natively at 100%!
…by the way… I have no idea why Windows got so angry to throw that Blue Screen for a Bad Pool Caller… nevermind!
2 Comments