Multiple problems - help!

[Ruggerbugger]

Here's the histoy to the problems I've had tonight.

System froze when trying to download quake 4 demo off id site. Thought it might be a problem related to Steam on my ID (seems to be slowing my boot time lately), so I rebooted and logged on to my Dad's ID and downloaded it from there. I also set Steam not to load on boot from my logon.

Got Q4 working and played through the demo before trying multiplayer. Halfway through mulitplayer I lose sound. Quit the match and try to go back in, but screen goes black before getting to the match, forcing a reset-button restart.

Now I get BIOS errors saying "keyboard error or keyboard not present". I use a USB keyboard plugged into the back of the case (mobo backplane). I eventually got the system to boot with the keyboard plugged into the front USB port of the case, whereupon it said that the integrity of one or more disks needed to be checked. I skipped this and got to the Windows logon where I shut the system down.

Any ideas as to what happened? When I had the case open I made sure each cable was fully pushed home (SATA cables are the old, non-locking type). I'm not reliant on this system (sending this from laptop), but it's a very expensive paperweight otherwise!

Theory: I've been having heat problems of late, could this have temporarily sent the mobo a bit screwy?

[blueball]

Could well be heat related or could be a card that is not quite properly seated.

The cheap first step is to set everything to stock speeds if you have done any overclocking.

If that fails then open the case and try running with the cover off - watch for any fans not working.

If that doesn't work then remove and re-insert all cards in case one has been dislodged during your earlier case opening. Removing and re-inserting will also clean the contacts on the cards if there has been any build of on them.

If that doesn't work do the same with the memory.

How many memory sticks do you have? Try running one at a time in case one is dodgy - admittedly that will slow things down to single channel operation but it will find if one is dodgy.

How many disks do you have? Can you run with one to see if one is dodgy?

[Ruggerbugger]

Thanks, it's booting OK now, but still said "one of your disks needs to be checked for consistency" I'm running two drives, might try removing the second one to see if it makes any difference. Same with the memory sticks.

[teachmech]

If you let it check the disk it could pick up errors from when the system crashed and then you should not see the message again.

[Ruggerbugger]

I'll probably do that later. Both episodes recently have been when playing FPS games, so I'm suspicious of either the 9800 Pro or the Catalysts. Might try upgrading to the latest version later on. By doing a contortionist act earlier on I'm pretty sure the fan on the GFX card is spinning. How long are they supposed to last? Does the heatsink compound wear out eventually or what? The card is getting on for three years old now

I've put it through a 2 1/2 hour virus check without any problems, so it seems fairly stable. Although when I tried checking the drive for errors under the Tools tab, it wouldn't complete Phase 1 (on the C: SATA drive), but would on the PATA drive I salvaged from my old comp.

[Ruggerbugger]

Seems to be OK now, it went through the disk check and fixed about a dozen errors in 2 or three files. Boots into Windows alright, so I guess it's suck it and see.

I can understand how some file corruption might screw up, say, a graphics driver or cause Windows to throw the dollies, but where does the "keyboard not present" error (which has also gone) come from? It's so early in the boot process, I can't see what it has to do with Windows.

[edit] Is there a log file for chkdisk that I can check to see the files it fixed?

[Ruggerbugger]

Here are the errors I've been getting, along with several disk errors going back 3 or 4 weeks, pointing to an error during paging. Some errors also mentioned corruption to the file system.

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 10/08/2006
Time: 00:45:23
User: N/A
Computer: NEIL-EBH6Q7A716
Description:
An error was detected on device \Device\Harddisk1\D during a paging operation.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 33 00 04 80 ....3..?
0010: 2d 01 00 00 00 00 00 00 -.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 43 89 00 00 00 00 00 00 C?......
0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ....
0038: 40 00 00 0e 00 01 00 00 @.......
0040: 09 20 0a 12 42 03 00 40 . ..B..@
0048: 00 00 01 00 0a 00 00 00 ........
0050: 00 00 00 00 30 54 7a 85 ....0Tz?
0058: 00 00 00 00 08 00 8b 86 ......??
0060: 40 51 f0 86 c7 b8 f3 04 @Qð?Ǹó.
0068: 28 00 04 f3 b8 c7 00 00 (..ó¸Ç..
0070: 80 00 00 00 00 00 00 00 ?.......
0078: 00 00 00 00 00 00 00 00 ........
0080: 00 00 00 00 00 00 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

The chkdsk log

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 10/08/2006
Time: 19:42:09
User: N/A
Computer: NEIL-EBH6Q7A716
Description:
Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk.

Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x2b3789 for possibly 0xc clusters.
Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x2b3789 for possibly 0xc clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x1a89a is already in use.
Deleting corrupt attribute record (128, "") from file record segment 108698.

Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x2af523 for possibly 0x4 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x2af523 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1c5b1 is already in use.
Deleting corrupt attribute record (128, "") from file record segment 116145.

Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x548897 for possibly 0x10 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x548897 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1c5d6 is already in use.
Deleting corrupt attribute record (128, "") from file record segment 116182.

Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xc9c7ef for possibly 0x18 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xc9c7ef for possibly 0x18 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1c69f is already in use.
Deleting corrupt attribute record (128, "") from file record segment 116383.

Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xc9c807 for possibly 0x22 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xc9c807 for possibly 0x22 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1c6aa is already in use.
Deleting corrupt attribute record (128, "") from file record segment 116394.

Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xc9c829 for possibly 0x5 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xc9c829 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1c6ab is already in use.
Deleting corrupt attribute record (128, "") from file record segment 116395.

Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x655ac1 for possibly 0x5 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x655ac1 for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1d373 is already in use.
Deleting corrupt attribute record (128, "") from file record segment 119667.

The two index entries of length 0x78 and 0x70 are either identical or appear in the wrong order.
21 1e 00 00 00 00 8f 00 78 00 5a 00 01 00 00 00 !.......x.Z.....
12 01 00 00 00 00 9e 00 22 d0 ae 56 b4 ae c6 01 ........"..V....
cc bf 3b 7a b5 ae c6 01 d8 db 70 48 da b8 c6 01 ..;z......pH....
72 3b e3 bb 0b bc c6 01 00 10 00 00 00 00 00 00 r;..............
00 08 00 00 00 00 00 00 20 20 00 00 00 00 00 00 ........ ......
0c 02 52 00 50 00 35 00 38 00 30 00 34 00 7e 00 ..R.P.5.8.0.4.~.
31 00 2e 00 52 00 45 00 50 00 30 00 30 00 30 00 1...R.E.P.0.0.0.
0b 00 00 00 00 00 00 00 04 00 0c 00 6a 01 08 00 ............j...
ec 13 00 01 60 28 07 00 8e bc 00 00 00 00 00 00 ....`(..........
----------------------------------------------------------------------
31 1f 00 00 00 00 d4 00 70 00 5a 00 00 00 00 00 1.......p.Z.....
12 01 00 00 00 00 9e 00 a2 c0 a9 59 b4 ae c6 01 ...........Y....
94 1b 3a d4 0d bc c6 01 94 1b 3a d4 0d bc c6 01 ..:.......:.....
fc a4 43 d4 0d bc c6 01 00 30 03 00 00 00 00 00 ..C......0......
88 20 03 00 00 00 00 00 20 20 00 00 00 00 00 00 . ...... ......
0c 02 52 00 50 00 30 00 39 00 30 00 34 00 7e 00 ..R.P.0.9.0.4.~.
31 00 2e 00 52 00 45 00 50 00 30 00 30 00 30 00 1...R.E.P.0.0.0.
21 1e 00 00 00 00 90 00 70 00 5a 00 00 00 00 00 !.......p.Z.....
Sorting index $I30 in file 274.

The two index entries of length 0x68 and 0x78 are either identical
or appear in the wrong order.
8d ae 01 00 00 00 0a 00 68 00 58 00 00 00 00 00 ........h.X.....
82 ab 01 00 00 00 0c 00 de c7 fb 2d b1 bb c6 01 ...........-....
de c7 fb 2d b1 bb c6 01 38 2a fe 2d b1 bb c6 01 ...-....8*.-....
de c7 fb 2d b1 bb c6 01 00 10 00 00 00 00 00 00 ...-............
06 07 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ........ .......
0b 01 6d 00 61 00 69 00 6e 00 5b 00 31 00 5d 00 ..m.a.i.n.[.1.].
2e 00 68 00 74 00 6d 00 47 00 00 00 00 00 00 00 ..h.t.m.G.......
67 00 01 00 00 00 07 00 4c 00 41 00 53 00 53 00 g.......L.A.S.S.
----------------------------------------------------------------------
89 bf 01 00 00 00 03 00 78 00 5a 00 01 00 00 00 ........x.Z.....
82 ab 01 00 00 00 0c 00 de e9 29 9d ba bb c6 01 ..........).....
38 4c 2c 9d ba bb c6 01 76 6e 47 a4 ba bb c6 01 8L,.....vnG.....
de e9 29 9d ba bb c6 01 00 10 00 00 00 00 00 00 ..).............
12 0c 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ........ .......
0c 02 4c 00 54 00 4d 00 5f 00 31 00 5f 00 7e 00 ..L.T.M._.1._.~.
31 00 2e 00 4a 00 50 00 47 00 01 00 00 00 0a 00 1...J.P.G.......
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
18 00 00 00 03 00 00 00 5b 00 00 00 00 00 00 00 ........[.......
Sorting index $I30 in file 109442.

The file reference 0x72000000000625 of index entry RptMngBak.i0000 of index $I30 with parent 0x112 is not the same as 0x71000000000625.
Deleting index entry RptMngBak.i0000 in index $I30 of file 274.
The file reference 0xbc0000000006c0 of index entry RptMngBak.i0001 of index $I30 with parent 0x112 is not the same as 0xbb0000000006c0.
Deleting index entry RptMngBak.i0001 in index $I30 of file 274.
The file reference 0xb5000000000958 of index entry RptMngBak.i0100 of index $I30 with parent 0x112 is not the same as 0xb4000000000958.
Deleting index entry RptMngBak.i0100 in index $I30 of file 274.
The file reference 0x478000000000e19 of index entry RptMngBak.i0101 of index $I30 with parent 0x112 is not the same as 0x477000000000e19.
Deleting index entry RptMngBak.i0101 in index $I30 of file 274.
The file reference 0x1bb000000000e1a of index entry RptMngBak.i0200 of index $I30 with parent 0x112 is not the same as 0x1ba000000000e1a.
Deleting index entry RptMngBak.i0200 in index $I30 of file 274.
The file reference 0x30b0000000010ee of index entry RptMngBak.i0201 of index $I30 with parent 0x112 is not the same as 0x30a0000000010ee.
Deleting index entry RptMngBak.i0201 in index $I30 of file 274.
The file reference 0x748000000001309 of index entry RptMngBak.reph of index $I30 with parent 0x112 is not the same as 0x747000000001309.
Deleting index entry RptMngBak.reph in index $I30 of file 274.
The file reference 0x90000000001e21 of index entry RptMngBak.repi of index $I30 with parent 0x112 is not the same as 0x8f000000001e21.
Deleting index entry RptMngBak.repi in index $I30 of file 274.
The file reference 0xd4000000001f31 of index entry RptMngBak.rept of index $I30 with parent 0x112 is not the same as 0xd3000000001f31.

Deleting index entry RptMngBak.rept in index $I30 of file 274. What's happening here?
Index entry LTM_1_~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1bf89.
Deleting index entry LTM_1_~1.JPG in index $I30 of file 109442.
Index entry MA91D2~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1af34.
Deleting index entry MA91D2~1.JPG in index $I30 of file 109442.
Index entry MAA318~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1af43.
Deleting index entry MAA318~1.JPG in index $I30 of file 109442.
Index entry MAA50D~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1af47.
Deleting index entry MAA50D~1.JPG in index $I30 of file 109442.
Index entry MAA70D~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1af4e.
Deleting index entry MAA70D~1.JPG in index $I30 of file 109442.
Index entry MAA908~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1af3e.
Deleting index entry MAA908~1.JPG in index $I30 of file 109442.
Index entry MAAD08~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1af4a.
Deleting index entry MAAD08~1.JPG in index $I30 of file 109442.
Index entry MAAF08~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1ae22.
Deleting index entry MAAF08~1.JPG in index $I30 of file 109442.
Index entry mainbn_01[1].jpg of index $I30 in file 0x1ab82 points to unused file 0x1b124.
Deleting index entry mainbn_01[1].jpg in index $I30 of file 109442.
Index entry mainbn_02[1].jpg of index $I30 in file 0x1ab82 points to unused file 0x1b126.
Deleting index entry mainbn_02[1].jpg in index $I30 of file 109442.
Index entry mainbn_03[1].jpg of index $I30 in file 0x1ab82 points to unused file 0x1b135.
Deleting index entry mainbn_03[1].jpg in index $I30 of file 109442.
Index entry mainbn_04[1].jpg of index $I30 in file 0x1ab82 points to unused file 0x1b138.
Deleting index entry mainbn_04[1].jpg in index $I30 of file 109442.
Index entry MAINBN~1.JPG of index $I30 in file 0x1ab82 points to unused file 0x1b124.
Deleting index entry MAINBN~1.JPG in index $I30 of file 109442.
Index entry MAINBN~2.JPG of index $I30 in file 0x1ab82 points to unused file 0x1b126.
Deleting index entry MAINBN~2.JPG in index $I30 of file 109442.
Index entry MAINBN~3.JPG of index $I30 in file 0x1ab82 points to unused file 0x1b135.
Deleting index entry MAINBN~3.JPG in index $I30 of file 109442.
Index entry MAINBN~4.JPG of index $I30 in file 0x1ab82 points to unused file 0x1b138.
Deleting index entry MAINBN~4.JPG in index $I30 of file 109442.
Index entry main[1].htm of index $I30 in file 0x1ab82 points to unused file 0x1ae8d.
Deleting index entry main[1].htm in index $I30 of file 109442.

Cleaning up minor inconsistencies on the drive.

CHKDSK is recovering lost files.
Recovering orphaned file RptMngBak.i0000 (1573) into directory file 274.
Recovering orphaned file RptMngBak.i0001 (1728) into directory file 274.
Recovering orphaned file RptMngBak.i0100 (2392) into directory file 274.
Recovering orphaned file RptMngBak.i0101 (3609) into directory file 274.
Recovering orphaned file RptMngBak.i0200 (3610) into directory file 274.
Recovering orphaned file RptMngBak.i0201 (4334) into directory file 274.
Recovering orphaned file RptMngBak.reph (4873) into directory file 274.
Recovering orphaned file RptMngBak.repi (7713) into directory file 274.
Recovering orphaned file RptMngBak.rept (7985) into directory file 274.
Recovering orphaned file LOGO-D~1.GIF (116196) into directory file 109442.
Recovering orphaned file logo-devnet[1].gif (116196) into directory file 109442.
Cleaning up 19 unused index entries from index $SII of file 0x9.
Cleaning up 19 unused index entries from index $SDH of file 0x9.
Cleaning up 19 unused security descriptors.
Inserting data attribute into file 108698.
Inserting data attribute into file 116145.
Inserting data attribute into file 116182.
Inserting data attribute into file 116383.
Inserting data attribute into file 116394.
Inserting data attribute into file 116395.
Inserting data attribute into file 119667.
Correcting errors in the Volume Bitmap. What's this?
Windows has made corrections to the file system.

117210208 KB total disk space.
73641592 KB in 102754 files.
37712 KB in 5769 indexes.
4 KB in bad sectors. Is this normal for a 2 1/2 year old drive, regularly used?
191184 KB in use by the system.
65536 KB occupied by the log file.
43339716 KB available on disk.

4096 bytes in each allocation unit.
29302552 total allocation units on disk.
10834929 allocation units available on disk.

Internal Info:
f0 d9 01 00 fb a7 01 00 d0 7d 02 00 00 00 00 00 .........}......
c0 22 00 00 00 00 00 00 d8 03 00 00 00 00 00 00 ."..............
78 9b 2d 05 00 00 00 00 b6 fa d7 6c 00 00 00 00 x.-........l....
34 0f 62 05 00 00 00 00 00 00 00 00 00 00 00 00 4.b.............
00 00 00 00 00 00 00 00 40 1a da 7f 00 00 00 00 ........@.......
99 9e 36 00 00 00 00 00 d8 3c 07 00 62 91 01 00 ..6......<..b...
00 00 00 00 00 e0 b9 8e 11 00 00 00 89 16 00 00 ................

Windows has finished checking your disk.

Do the disk paging errors point towards drive failure, or something else?

[edit]Googling the disk error turns up the following knowledgebase article, which describes the symptoms I've been experiencing (long time logging off etc) and some of the errors (usrenv) that appear in the Event Viewer. I'll probably try the suggested fix tomorrow - and get the backup drive going (a new drive is out of my budget at the moment).

http://support.microsoft.com/kb/837115

[edit]The guys on this site seem to be blaming the Silicon Image SATA controller, which is present on my motherboard. Is there any way of "probing" this to see if it's at fault?

[Ruggerbugger]

Any ideas about what the dump shows guys?