Sometime ago, I wrote a note about the computer problem at the language lab at the university where I’m studying. Apparently, although we’ve had two weeks of break, the problem is still there. I mean to say that I thought the problems were taken care of during the break, but they weren’t.

Yesterday, when I was in the middle of my work at the lab, the computer next to me had a BSOD without even being touched. I logged in, because, as is instructed by the teacher, that the one next to us should also be on although no one is using it. That way, we know if there is something wrong with the system or not. Well, there is.

Then, another computer, which was being used by a student, also had a BSOD. It really made me think. What is the problem actually? I’ve always thought that it’s a software problem, like missing DLLs or messed up registry files or something. Yesterday, I did a little research on atapi.sys. I happened to notice that there was a problem with accessing atapi.sys when the computer went BSOD. I googled “BSOD atapi.sys.”

There’s one forum, I forgot the name, and there’s an intriguing, at least to me, solution. Some guy also had the same problem and he posted the log files and everything else in details. Apparently, it’s hardware problem, and I quote, “A driver gets updated, which changes the underlying assembly code to a different set of instructions. Those instructions when run in the new sequence are what expose the errata/bus noise/cache fetch failure,” JoeHobart. That sounds to make sense.

Wait! My brain just gave me a call. Yes, I know it all along that it could also be hardware problem, but for some reason, it didn’t come to my mind when I encountered it, but what is the real problem here? A BSOD is usually caused by missing DLLs, registry issues, driver problems and also faulty memory.

Well, if it’s really registry issues or missing DLLs, fixing the MBR (Master Boot Record), editing the registry and replacing the DLLs will be a solution, but I think that they have made some changes in the registry. My other suggestion is try reformatting one of the computers that usually fails. If it solves the problem, then reformatting the rest of the computers will probably solve the whole problem, but if not, then it is hardware.

More about the forum that I found on Google. Later on, JoeHobart explains that BIOS update will give a significant result to the problem and reinstalling (Reformatting) won’t. Point taken! But unfortunately, while the BSOD happened, I didn’t remember much of what is going on. I only remembered about atapi.sys of not being able to be accessed, but I’d definitely recommend the University to update the BIOS to all computers. Maybe it is the solution.