Random Laptop Shutdowns (again)

[LauraL]

Hello,

My laptop has begun shutting down. No over-heating, no blue screens, no reboot attempt. Just black screen, laptop is off. This is mostly occurring during heavy use such as playing a heavy full screen game but these have now been occurring randomly as well, seemingly getting gradually more frequent.

I posted with virtually an identical problem to this in May on the following thread: http://www.sevenforums.com/hardware-devices/370489-laptop-shut-downs-possible-hard-drive-issue.html

This issue seemed to have been resolved with a new hard drive and had been working perfectly fine for nearly 4 months.

EventViewer once again is revealing: Level- Error, Source – atapi, EventID – 11, Task – None, Category – The driver detected a controller error on\Device\Ide\IdePort1 at the times of shut downs, where IdePort1 is still my hard drive.

I re-checked the health of my new hard drive using Seatools for Windows. It passes S.M.A.R.T check, ShortDrive Test and Short Generic testing but it fails Long Generic testing. It makes no progress in the Long Generic test, it hangs at full estimated time of 02:24 for about 2-3 minutes before failing the drive.

Searching online as to what this result really means doesn’t really seem to give me a distinct answer so I decided to, once again, search online for what the IdePort1 error may mean and this seems to be generating a lot of ‘check the cables’ responses.

Since the new hard drive’s installation by a technician in a computer repair shop, no one has re-opened the laptop. I have 0 confidence in my ability to open my laptop and check these myself but I am still abroad until early next year and don’t want to trust anyone here to open my laptop again to check any physical connections.

I’m hopeful someone here has an idea as to what this IdePort error + the failed Long Generic hard drive test may mean and what may be causing these random shut downs. Would anyone please be able to suggest something I could try to solve this issue without having to risk another mishap in a shoddy foreign repair shop?

 

[GokAy]

Even though laptops are a pain to open, laptop hard disks are in an easy to reach area and you can check it yourself. Just turn the bottom up and remove the 4-5 screws that hold the compartment cover. Laptops don't have cables for hard disks but it may have moved perhaps. Reseat it in case and close it up.

From what you describe, it may be a temperature issue. Get HWInfo (start with sensors-only) and check the temps that may show. You can try running Intel Burn Test while HWInfo is open. Don't let it go unattended though.

 

[LauraL]

I'm 100% confident this isn't a thermal shutdown and I have been using HWMonitor since the last time this issue occurred. Shut downs can occur at any temperature, ranging from during a disk clean up of the C drive at 45C/113F and 89C/192F running a heavy game.

There are no thermal event errors logged in the Eventviewer, the laptop is cool, it can occur after booting up from being off all night. It simply seems to happen when the laptop is doing something strenuous.

I had forgetten to try a CHKDSK and so ran this last night. The results were kind of alarming actually, I got stuck at 1% at stage 1 for quite some time:



　

Checking file system on C:

The type of the file system is NTFS.

A disk check has been scheduled.

Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...

Read failure with status 0xc0000185 at offset 0xc2036000 for 0x1000 bytes.

File record segment 32984 is unreadable.

Read failure with status 0xc0000185 at offset 0xc2036000 for 0x1000 bytes.

File record segment 32985 is unreadable.

Read failure with status 0xc0000185 at offset 0xc2036000 for 0x1000 bytes.

File record segment 32986 is unreadable.

Read failure with status 0xc0000185 at offset 0xc2036000 for 0x1000 bytes.

File record segment 32987 is unreadable.

Read failure with status 0xc0000185 at offset 0xc2037000 for 0x1000 bytes.

File record segment 32988 is unreadable.

Read failure with status 0xc0000185 at offset 0xc2037000 for 0x1000 bytes.

File record segment 32989 is unreadable.

Read failure with status 0xc0000185 at offset 0xc2037000 for 0x1000 bytes.

File record segment 32990 is unreadable.

Read failure with status 0xc0000185 at offset 0xc2037000 for 0x1000 bytes.

File record segment 32991 is unreadable.

267008 file records processed. File verification completed.

1726 large file records processed. Read failure with status 0xc0000185 at offset 0xc2036c00 for 0x400 bytes.

Read failure with status 0xc0000185 at offset 0xc2037000 for 0x400 bytes.

Read failure with status 0xc0000185 at offset 0xc2037400 for 0x400 bytes.

Read failure with status 0xc0000185 at offset 0xc2037800 for 0x400 bytes.

8 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...

Index entry logtemp.sql of index $I30 in file 0x1838 points to unused file 0x80db.

Deleting index entry logtemp.sql in index $I30 of file 6200.

Index entry IIsConsole.psc1 of index $I30 in file 0x1839 points to unused file 0x80de.

Deleting index entry IIsConsole.psc1 in index $I30 of file 6201.

Index entry IISCON~1.PSC of index $I30 in file 0x1839 points to unused file 0x80de.

Deleting index entry IISCON~1.PSC in index $I30 of file 6201.

Index entry AppHostNavigators.dll of index $I30 in file 0x2961 points to unused file 0x80dc.

Deleting index entry AppHostNavigators.dll in index $I30 of file 10593.

Index entry APPHOS~1.DLL of index $I30 in file 0x2961 points to unused file 0x80dc.

Deleting index entry APPHOS~1.DLL in index $I30 of file 10593.

Index entry IIsConsole.psc1 of index $I30 in file 0x2961 points to unused file 0x80dd.

Deleting index entry IIsConsole.psc1 in index $I30 of file 10593.

Index entry IISCON~1.PSC of index $I30 in file 0x2961 points to unused file 0x80dd.

Deleting index entry IISCON~1.PSC in index $I30 of file 10593.

327098 index entries processed. Index verification completed.

CHKDSK is scanning unindexed files for reconnect to their original directory.

4 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...

267008 file SDs/SIDs processed. Cleaning up 274 unused index entries from index $SII of file 0x9.

Cleaning up 274 unused index entries from index $SDH of file 0x9.

Cleaning up 274 unused security descriptors.

Security descriptor verification completed.

30046 data files processed. CHKDSK is verifying Usn Journal...

34577896 USN bytes processed. Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)...

Read failure with status 0xc0000185 at offset 0xb31792000 for 0x10000 bytes.

Read failure with status 0xc0000185 at offset 0xb3179d000 for 0x1000 bytes.

Read failure with status 0xc0000185 at offset 0xb3179e000 for 0x10000 bytes.

Read failure with status 0xc0000185 at offset 0xb3179e000 for 0x1000 bytes.

Windows replaced bad clusters in file 10648

of name \PROGRA~2\TERA\Client\S1Game\CookedPC\Art_Data\Packages\CH\PC\CA943D~1.GPK.

Read failure with status 0xc0000185 at offset 0xb5b88f000 for 0x10000 bytes.

Read failure with status 0xc0000185 at offset 0xb5b892000 for 0x1000 bytes.

Read failure with status 0xc0000185 at offset 0xb5b893000 for 0x10000 bytes.

Read failure with status 0xc0000185 at offset 0xb5b893000 for 0x1000 bytes.

Windows replaced bad clusters in file 74614

of name \PROGRA~2\TERA\Client\S1Game\CookedPC\Art_Data\Packages\BG\EXTENS~1\Theme\Balder\EX01_B~2.GPK.

Read failure with status 0xc0000185 at offset 0x6cce86000 for 0x10000 bytes.

Read failure with status 0xc0000185 at offset 0x6cce91000 for 0x1000 bytes.

Read failure with status 0xc0000185 at offset 0x6cce92000 for 0x10000 bytes.

Read failure with status 0xc0000185 at offset 0x6cce92000 for 0x1000 bytes.

Read failure with status 0xc0000185 at offset 0x6cce93000 for 0x10000 bytes.

Read failure with status 0xc0000185 at offset 0x6cce93000 for 0x1000 bytes.

Windows replaced bad clusters in file 239487

of name \Windows\winsxs\MSIL_S~3.177\System.dll.

266992 files processed. File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...

33543840 free clusters processed. Free space verification is complete.

Adding 9 bad clusters to the Bad Clusters File.

Correcting errors in the master file table's (MFT) DATA attribute.

CHKDSK discovered free space marked as allocated in the

master file table (MFT) bitmap.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

249786616 KB total disk space.

115130324 KB in 134220 files.

103060 KB in 30047 indexes.

36 KB in bad sectors.

377836 KB in use by the system.

65536 KB occupied by the log file.

134175360 KB available on disk.

4096 bytes in each allocation unit.

62446654 total allocation units on disk.

33543840 allocation units available on disk.

Internal Info:

00 13 04 00 b6 81 02 00 a6 cd 04 00 00 00 00 00 ................

9a 87 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........

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 decided to re-run Seatools for Windows to see if the Long Generic test had failed due to the presence of bad clusters, hoping now that CHKDSK had seen to them it would pass the drive. Unfortunately, not only does it still fail the Long Generic test, it is now failing the Short Drive Test which it hadn't done before the CHKDSK:

I decided to re-install CrystalDisk info which was recommended to me on these forums the last time I had this issue and here are the results of that:

What am I looking at here? Is this hard drive damaged and/or failing after only 3.5 months and causing my laptop to shut down again? :shock:

 

[GokAy]

Since it is failing these tests, I will say it is failing. Apparently it is getting worse. You should RMA that drive and backup any data as soon as possible.

 

[LauraL]

What could cause a hard drive to go into failure in just 3.5 months? I play heavy games on it but I really don't want to believe that can destroy a drive, though everyone else seems to blame it on this.

It might be worth mentioning that this laptop originally had 2 hard drives, one failed 1.5yrs ago (around the time I moved abroad to a very hot, very sandy/dusty country I might add), the other failed 3.5 months ago but considering the age of the laptop I just figured this was their life expectancy. But now a third, new one has failed.

I've never opened my laptop and I never had problems with hard drive failure prior to moving here. Am I somehow causing these failures through heavy use or is it possibly the new climate I live in or was I just unlucky and bought a faulty new drive? I'd really like to have some idea what's causing this because I really don't want to get a fourth and find myself having the same issue another 3.5 months from now :shock:

 

[Mellon Head]

I think it's very possible that you just got a bad drive. Laptop drives tend not to last as long as a desktop drive anyway, due to the bumps and knocks endured by a laptop in general use.

As GoKay suggested, I would back up your data and RMA that drive. It should still be under warranty.