![]() |
|
![]() |
|
||||||
| Main | Classifieds | Register | FAQ | Calendar | Live View | Wccftech Reviews | Arcade | Search | Today's Posts | Mark Forums Read |
|
|
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#16
|
||||
|
||||
|
Quote:
Anyway right now it looks like your hdd is toast.
__________________
See what Pakistani bloggers are saying... |
|
#17
|
||||
|
||||
|
i got my partitions back .. i just unplugged it and plugged it back. But still facing the display problem i had to remove ram clean it and put it back again to get the display working no blue screens lately though ..
|
|
#18
|
||||
|
||||
|
IF prime95 did this to your PC, it is (or was) not very stable to begin with.
Did u check the event viewer to see the error prime95 generated? IF you dont have any more Blue screens it probably meant something was "loose" and now u've plugged it. If u do a lot of plugging and un plugging (which i see you do), you need to make sure: 1. The ram sticks are properly seated 2. The S-ata cables do not have any 90 degree bends in them |
|
#19
|
||||
|
||||
|
well let me explain to you what happened yesterday. When i turned on my pc for the first time in the night after shutting it down in the evening i had the display problem again so i removed ram and cleaned it and put it back again but then instead of putting both sticks at once i placed only one stick in my mobo to see which one causes the blue screen so then i started my pc on one stick and i got my display back and then i read your post of running SMART online analysis it went fine on both hdds and then i ran prime95 after running it for a while it restarted my pc and when it was booting it said windows cannot be started, some hardware is missing and then i did everything i could do to see if the partitions are still available or not but i couldnt find them the second hdd just totally vanished and i had my windows installed on it. Then i reinstalled windows on my other hdd and after installing it i went to Computer > manage > Disk management but it wasnt able to detect my second hdd so what i did is unplugged harddrive and plug it back again ( what d3v said ) and it started working and then electricity went off and when it came back same display problem again -,- then i put the other stick of ram without removing the first one and the display came back.
and btw i havent faced a single bsod since yesterday yet. The only problem now is the display i guess. Will let you know if i face blue screen again. i cant wait to crush this motherboard .. |
|
#20
|
||||
|
||||
|
SMART test is not enough. You really need to do a thorough check for bad sectors.
__________________
See what Pakistani bloggers are saying... |
|
#22
|
||||
|
||||
|
Error 50 can also be due to bad RAM, not only a dying drive.
Do this: Disconnect the 80 GB HDD and see if things work okay. The next time you get a bsod, check if it is ntfs.sys that is causing the error. the 3 major causes of a error 50 are: 1. Failing RAM 2. Spyware 3. Bad Hardware |
|
#23
|
||||
|
||||
|
1. What is ntfs.sys ? And how to check if its causing the blue screen ?
2. It could be the failing ram i guess but how to be sure about it ? 3. I cant disconnect my 80 gb hdd, i have my os installed on it. But i am going to disconnect it forever once i buy my new hdd and my second hdd is new i dont think its the problem . 4. Which hardware could be bad ? |
|
#24
|
||||
|
||||
|
Quote:
2 n 3. Keep checking for Blue screens, if it is always the NTFS.sys that causes the problem it could be the drive. If it varies, it is either bad ram or a rootkit virus. Since you have already installed your OS again, we can rule that out. (You did install from a clean copy right?) 4. Right now, if disconnecting the 80GiG HDD does the trick, it is probably that. But i am not too certain. 5. Try this: use your computer with only one stick of ram IN THE SLOT closest to the processor. See if u can get a blue screen then. |
|
#26
|
||||
|
||||
|
no, i meant the Disc you installed from was clean?
|
|
#27
|
||||
|
||||
|
Googling "ntfs.sys page_fault_in_nonpaged_area" turns up a lot of info.
Straight from the horse's mouth we have this page: Error Message: But I think the best course of action is to post your memory dump files created after the BSOD on this forum (make a new thread). There is a guy there that can make sense of those dump files and pin point the faulty hardware: ntfs.sys PAGE FAULT IN NONPAGE AREA bluescreen - Page 3 - TechSpot OpenBoards
__________________
See what Pakistani bloggers are saying... |
![]() |
| Tags |
| alot, bsod, facing |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Bsod | stickman! | Science, Technology & Gadgetry | 7 | 10-09-08 05:53 PM |
| BSOD w.r.t. igxpdv32.dll | Bheegi Billi | Computer Talk | 2 | 16-08-08 04:48 PM |
| Alot of ppl r falling for this | Fookie | Current Affairs Parlor | 3 | 06-12-07 12:16 AM |
| Thanks Alot | satlover01 | CPUs, Motherboards & Video Cards | 7 | 12-06-07 01:36 AM |
| Auto Show In Lahore [Caution : Alot of big pics inside] | mircTOPGUN | The Garage! | 24 | 02-04-05 04:34 PM |