NTFS is for reading and writing to/from the NTFS filesystem (and understanding how that all works so the OS itself doesn't have to) - actual disk access goes through disk.sys (which then calls the actual driver for the controller, if one exists or can be loaded).
Ah, that makes sense. In this case, the RAID driver would be for the controller, correct?
The virtual hardware levels are not my area of expertise; I'm actually better at actual hardware (have a background in mechanical engineering) and understand drivers and what they do (I do software development), but am not necessarily familiar with the interfaces between certain drivers. This is helpful information, though maybe not for the OP. Perhaps we should continue this in a separate thread or private messaging?
yellowsrt4, back to your problem... My instinct is that your issues are likely being caused by the Comcast driver. Whether it is the driver itself, or a problem it is having with one of your other drivers or your disk, I can't say for sure until you hear back from Comcast and we can eliminate it as a probable suspect.
Did you hear back from Comcast regarding the problem? Did they offer any troubleshooting steps?
Sorry for not getting back sooner. It started bsod even in safe mode... Tried a restore and it failed in the middle (bsod)... Removed the hard drive and had a friend who works at a computer store reload windows on it. The PC it was on functioned fine, so I put it in and poof bsod. She dinged around with the comp and said it could be either the mobo or processor... But she didn't have anything to test it on her. So that is where I'm at...
The only way to really test would be to either try a different CPU in your motherboard, or try your CPU in another board that supports it. Sometimes, local repair shops will test a CPU for low cost in one of their machines.
Have you had the CPU tested?
Last edited by writhziden; 04 Mar 2012 at 20:06. Reason: Update?
Quote