Hmmm, I don't tend to look at the error codes at first. Try going to Control Panel > Administrative Tools > Event Viewer and then post all information regarding your error.
Most BSOD are due to power defficiencies, try going into your BIOS and then the hardware monitor or something along those lines and then take a look at your voltages, I know on ASUS motherboards if something is out of the ordinary it will highlight it in red.
And also i can't find the hardware monitor tab or anything similar in my bios. The closest i could find is the "POWER" tab and it didn't show anything useful.
Last edited by peterson93; Sep 5th, 2009 at 11:40 pm.
And also i get other blue screens as well, mainly during startup and 5minutes after i log in to desktop. If i can log in to desktop fine after 5 minutes, i can use it for 6hours without any problems most of the time.
Most BSOD's are caused either by harware/driver malfunctions, or by core sys files being corrupted/removed (most commonly by malware, but also by poorly coded applications removing/tampering with core files).
As the "Ntfs.sys" reference suggest the latter (a core sys file corruption), best to first run a recovery install from your Windows disk (will need to boot from said disk), then use something like MalwareBytes to scan for any infections to rule out the Malware side of things. Once you know is clean, you'll need to reinstall any SP's and updates (some apps may also need to be removed and reinstalled, depending on their reliancy on certain Windows SP's).
Last edited by kaninelupus; Sep 6th, 2009 at 6:49 am. Reason: more info
They're not all 0x000000F7. Most of them occur during startup and 5minutes after i log in to desktop.
For us to help diagnose at a distance, it's important that you catc h the code, the system (e.g. NTFS.SYS), any supporting error text and the stage during startup or normal working at which it occurs.
Is there any pattern?
Could you supply a listing of what MNSCONFIG syays are your startup DLLs and programs? Then we can recommend a controlled switch of of these until the problem goes away, or if it doesn't we can rule out certain causes.
There may well be RAM misbehaviour. There are RAM tests you can carry out. Perhaps you should do that and report.
BSODs on NTFS.SYS can point to a corruption of system files as kanineplus said. However, I've seen a few systems throw up NTFS.SYS related BSODs and the problem turned out to be faulty hard drives. Apart from the steps mentioned above, I'd also recommend tunning any vendor specific diagnostics on the hard drive.
If you could provide us with the model number of your system (or maybe the brand of the motherboard and hard drive) we could suggest a few other steps.
No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Unsolved 
Offline 
