Tue, Apr 25 2006 17:54
bradley
Hey Peter! That was pretty easy!
So on my glowing blue baby test server I got a dooozy of a BSOD yesterday... just as I was needing it to be in good shape for Vlad's SBSgroup meeting. So I got it operational and it sent off a Dr. Watson... but I remembered PeterGal's post on how to do debugging... so while I sent the dump file off to the expert of "~", I made him a deal..that I'd try to look at it first and see if I could figure out what was doing it.
..now I had an idea that the virtual cdrom driver that I'd downloaded probably was the culpret since it was unusual and not my normal thing that I install on my server... but I followed Peter's blog post....
I downloaded the debugger tools....
I set the symbols like he said to do
I ran the program and....
Probably caused by : atapi.sys ( atapi!IdeLogSaveTaskFile+1f )
Now given that the cdrom virtual cdrom has a post in their forum about atapi.sys... what do you want to bet that that virtual cdrom driver is the one causing the issue.
... and like many things in tech.... that wasn't so hard to do after all!
Now I can't wait until my next BlueScreen! This is cool!
Filed under: News