Thanks for checking it.
My brother told me that he was only listening songs and chatting with his friends through Windows Live Messenger and then the BSOD occurred all of a sudden.
I too, had been using it for almost a week but no BSOD on my watch.
It seems the number of BSOD were decreased almost completely after Dealer's tech guy flashed my BIOs to a newer version.
but you speak of mobo's controller thing there's one issue that happened recently
remember the first time I told you that I went back to change DVD-RW once because I found it defected after Its reading ERROR while setting up OS.
This ERROR reading Issue had happend again (noted that this is a newly claimed LG22X DVD-RW) with my newly-bought Command&Conquer4 Disc.
I worried as much because I used it to setup others game back then when I just got it back from claimation service and It was ok!
So I try this C&C4 disc on another my PC which happens to had the same LG22X DVD-RW Drive and it got through just fine!
Surprising enough, so I replaced that failure drive with the same LG22X DVD-RW Drive from another PC and try installing again to check whether the problem could come from a cable or Mobo controller itself? but everything went very normally, my C&C4 was successfully installed.
So I sent it to claimation service again (tiring) and in waiting....
Now I used an ASUS DVD-RW drive instead and no problems so far!
(I bought it myself but forgot and left it under my desk almost a year, Do you believe that!?)
Is your system sitting under a desk where airflow could be compromised ?
kind of.. but I think It could not be Thermal problem.
Is the power supply in your house stable ?
ofcourse it is, I think.
I would check for the differences and be talking to your dealer ?
I already spoke to them once and they told me that it could be because an external 3rd party hardware and its drivers... because these are the only diferrences between when they testing at the service and my test at home.
Come to think of it. There is one 3rd party hardware that I used; It's the keyboard.
Normally I would buy Microsoft or Logitech Keyboard but this was the first time for me buying some Unknown brand keyboard cuz my little bro loved it.
but since the debugger blames ntfs.sys this keyboard thing is out of the question.
I will continue using it as normal for now, to see if the BSOD will occur again and if it does ..will it be ntfs.sys or else?
Hopefully, this was just some random BSOD that doesn't happens too frequent to undermine any daily usage because I can let it go and try fixing it little by little.
Optimistically, At least It's better than the first time I posted help, That was like one BSOD after another, a real nightmare.
I'm Glad I could get some help here
