PC Peripherals PC keeps restarting

Status
Not open for further replies.
try to change slots. also, update the driver for that intex card, it cud ve been corrupted too :) AFAIK, it comes with separate drivers right? in hardware manager, choose the NIC and then the update driver option n reload driver. Else uninstall the driver n install again :)
 
Sorry for bringing this old thread to life again, but I'm facing a lot of problems again.

My config is -

AMD 3800+ X2
ASUS A8N-VM SE
Corsair 512MB X 2 ~ 1 GB RAM
Seagate 160 GB PATA

The same old restarting issue is back. Earlier it only surfaced when I stressed the network.. i.e copying a file, downloading a file @ full bw etc. But now there are random restarts. Though mainly when I'm browsing the net or downloading.

I googled a lot and lots and LOTS of people have the same problems with their ASUS motherboards. So, obviously there was lots of advice on the topic too.

The main error is DRIVER IRQL LESS THAN OR EQUAL. On various forums people suggested that IRQ sharing should be as minimum as possible so turn off unnecessary devices such as floppy drive, parallel ports, onboard audio etc. I turned all these things off and the frequency of restarts has come down to around once every 3 hours from once every 10-15 mins.

Somewhere someone suggested to see the Event viewer in the Adminsitrative tools in Control Panel and see the System Error log. Here I discovered that mainly the issue was caused by "Event 1003, category (102)". Now this was also a widespread problem but searching through google results I could not pinpoint the problem mainly because I'm not being able to understand the technical language :(

UTorrent has not caused any restarts in the past 3 hours.

I ran a chkdsk on my primary partition C: and this is what it showed -
C:\>chkdsk c:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Missing object id index entry or duplicate object id detected
for file record segment 26459.
Correcting error in index $I30 for file 19015.
Correcting error in index $I30 for file 19015.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
Click to expand...

Is the problem with the hard disk? I'm totally confused now as to whether the problem lies with my hard disk or something else...

Please help. :huh: :huh: :( :(
 
I am not sure how to fix ur issue but if something like this happens on my sys the first thing i do is back up my data and wipe the disk and do a clean windows install and see if the problem persists

not the best way but takes out the possibility of bad OS and usually it is something to do with the OS
 
It seems that u have drive error.

Tell me one thing this restart happens when u r copying the file to particular drive or when u try to copy in other drive also.

Try run chkdsk in the command prompt. If there is any error, then

If it happens for a particular drive then fix it
Rightclick drive -> Properties -> Tool -> Check Now -> Check mark the option Automatically fix error, Scan and recover.. -> Startnow

NB: Close the drive if any window is open.

If its the root drive then, i.e. C: or drive where you have install the OS, then restart the PC inserting the OS CD and boot from CD. Enter the repair mode. You will have a command window. Type chkdsk C:/f for repairing without scanning or chkdsk C:/r for repairing after scanning.

After doing these if ur problem is solved then all well, else all thing would be pointing to the RAM. Borrow from ur friend a RAM stick for a day and try to run ur PC with it and see if the machine is stable or not. U will get the answer. :)
 
Okay, will try this. But are you sure it is caused by the hard drive?? Since last night most of the crashes have been happening when I was browsing the web.
 
Sei said:
C:\>chkdsk c:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Missing object id index entry or duplicate object id detected
for file record segment 26459.
Correcting error in index $I30 for file 19015.
Correcting error in index $I30 for file 19015.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
Click to expand...
It shows that there is some error in index. clearly :detect2: . You were not able to fix it because u have run only chkdsk which is read-only mode. You have to give the parameters for other operation with chkdsk. Try what I have said. I hope the error have not spread or there is no error in the track 0, otherwise it will be lot of problem for you.
If the error unrepairable then avoid using the error part of the drive, else it will spread. At that case, I will say look for new HDD, storage parts have gone very cheap :) .
One more thing u can try, which I have done is to use it as a secondary drive and try to detect the error in which drive it have occured and make it unpartition. By that way you will not be using corrupted part of the drive and will be avoiding error spread, while using other parts of the drive for storage. :D
 
^^honest question!!!

can you explain how the error can spread I have heard that from other ppl before but I am not sure how it can spread
 
leo_club said:
^^honest question!!!

can you explain how the error can spread I have heard that from other ppl before but I am not sure how it can spread
Click to expand...

OK! :)

Bad sector are of two types(Physical or inconsistencies in parity)

See the whole mechanism of HDD revolve around the concept of magnet. All our data are stored in the magnetic surface of the HDD. (I am not going into the details how data are encoded into the disk). When you get a bad sector it means that a sector on the disk where data cannot be written or read due to a physical damage or inconsistencies of parity checking bits on disk.

When the bad sector is caused by parity problem it is most likely of be repaired and recovered, but not in the case of physical damage.

How does it spread ?
Bad sector are mainly due to the magnetic weakning of the domain and mechanical faults. Over the time the magnetic area of the disk lose its magnetism and hence its inability to retain data. Such bad sectors have the tendency to spread and are usually non-repairable. Mechanical faults include physical shocks to the disk, abrupt power shutdowns and disruptions during read/write operations. Head crash can also cause bad sectors and lead to permanent loss on the disk.
 
Thanks for the reply
Just a confusion
Bad sector are mainly due to the magnetic weakning of the domain and mechanical faults. Over the time the magnetic area of the disk lose its magnetism and hence its inability to retain data. Such bad sectors have the tendency to spread and are usually non-repairable.
Click to expand...

I still don't understand how it can spread when i am using the bad sector if its caused by the disk losing its magnetism.
 
Status
Not open for further replies.
Top Bottom