• Clicking noises in game, then BSOD
    4 replies, posted
This problem has recently started happening but whenever I am in a game of League of Legends I will start to hear a clicking noise which I presume to be the hard drive? The game screen will freeze up for a few seconds every few clicking noises and then eventually the screen will completely glitch up and go into a BSOD. This does not happen every game but it has done it 2 times randomly now after booting into a match. I'm not too computer savy so I have no clue what I am exactly dealing with here but I think one of the reasons is it's safe to assume that my hard drive is probably getting too old. (I bought the prebuilt computer in 2009 roughly so...) Anyways here is what the program WhoCrashed gave me: [B]On Mon 7/27/2015 11:05:47 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\072715-34382-01.dmp This was probably caused by the following module: storport.sys (storport+0x55C80) Bugcheck code: 0x7A (0xFFFFF6FC40008818, 0xFFFFFFFFC000009D, 0x9EA38860, 0xFFFFF88001103C80) Error: KERNEL_DATA_INPAGE_ERROR file path: C:\Windows\system32\drivers\storport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Storage Port Driver Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Thu 7/23/2015 10:32:26 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\072315-29218-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800039601D9, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/B] Any possible causes or solutions for these errors? Will provide more info as needed.
Are you sure the clicking is from a hard drive and not your speakers? The latter generally indicates a resource conflict. Mind you, if the Storage Port driver is bitching out that can be a pretty good indication that it's running into data access errors. When is the last time you did a surface scan?
Even if you're not sure, if there's room to believe the clicking noises were from the HDD make sure to backup your files in order of importance [I]right now[/I]. Clicking noises means mechanical problems, which usually kills the HDD for good in little to no time.
[QUOTE=pentium;48309614]Are you sure the clicking is from a hard drive and not your speakers? The latter generally indicates a resource conflict. Mind you, if the Storage Port driver is bitching out that can be a pretty good indication that it's running into data access errors. When is the last time you did a surface scan?[/QUOTE] I am quite sure. The sound itself comes from the tower, same noise it makes upon turning off the computer. The first crash it automatically did a disk check I believe upon startup. Which did resolve it I think because it kept happening up until the disk check. I suppose that would explain the difference between the 2 crashes. [QUOTE=JohnnyOnFlame;48309623]Even if you're not sure, if there's room to believe the clicking noises were from the HDD make sure to backup your files in order of importance [I]right now[/I]. Clicking noises means mechanical problems, which usually kills the HDD for good in little to no time.[/QUOTE] Gonna get on that shortly. I do have most of my important files stored on an external HD plus a relatively old backup but I guess it's time to update that.
Ran a disk check last night, took all night compared to the first one. [I]Checking file system on C: The type of the file system is NTFS. Volume label is OS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x26108b4 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x7ae0a is already in use. Deleting corrupt attribute record (128, "") from file record segment 503306. 1226496 file records processed. File verification completed. 10826 large file records processed. 0 bad file records processed. 0 EA records processed. 63 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 1569402 index entries processed. Index verification completed. CHKDSK is scanning unindexed files for reconnect to their original directory. 1 unindexed files scanned. CHKDSK is recovering remaining unindexed files. 1 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 1226496 file SDs/SIDs processed. Cleaning up 63 unused index entries from index $SII of file 0x9. Cleaning up 63 unused index entries from index $SDH of file 0x9. Cleaning up 63 unused security descriptors. Security descriptor verification completed. Inserting data attribute into file 503306. 171455 data files processed. CHKDSK is verifying Usn Journal... The remaining of an USN page at offset 0x8f4885c60 in file 0x13fb3 should be filled with zeros. Repairing Usn Journal file record segment. 37520248 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Windows replaced bad clusters in file 146921 of name \Users\Nick\AppData\Local\MICROS~1\Windows\WER\REPORT~2\AP7D24~1.EXE\Report.wer. 1226480 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 7727250 free clusters processed. Free space verification is complete. Correcting errors in the master file table's (MFT) BITMAP attribute. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. 962772991 KB total disk space. 929974392 KB in 987570 files. 522932 KB in 171456 indexes. 0 KB in bad sectors. 1366667 KB in use by the system. 65536 KB occupied by the log file. 30909000 KB available on disk. 4096 bytes in each allocation unit. 240693247 total allocation units on disk. 7727250 allocation units available on disk. Internal Info: 00 b7 12 00 7d af 11 00 6a 22 1f 00 00 00 00 00 ....}...j"...... d7 54 00 00 3f 00 00 00 00 00 00 00 00 00 00 00 .T..?........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.[/I] Whatever it was, it appears to be okay and working now.
Sorry, you need to Log In to post a reply to this thread.