BSODs about once a day


Joined
Jun 12, 2014
Messages
7
Reaction score
0
Hello guys, for the past 3 months or so I've been having an occasional issue with my 2-year Vaio laptop sometimes getting a BSOD on wakeup (since I usually put it to sleep instead of shutting down); I didn't make too much fuss about it back then, since it only affected the startup sequence and I didn't have the time to troubleshoot it anyway.

In the last two or three weeks however, the issue seems to have gotten a lot worse. I'm getting a random BSOD about once-twice a day now; I didn't update or install anything, it just started to occur on its own. Now I'm mostly worried whether it might be a hardware fault of some sort, since it's been just half a year since my HDD got busted and I had to get it replaced.

Sometimes when I move the laptop or slightly bend it by accident (really flimsy casing on the Vaio) the HDD makes a short "clack" sound and the system freezes for about a second, could that signify anything, like a faulty HDD cable maybe?

The error code I'm getting the most is 0xf4: KERNEL_DATA_INPAGE_ERROR


I'm attaching all the minidumps I have; I have about 10 full memory dumps from May saved too, so if there's a way to compress them somehow I could post them here too. Last two days I've gotten BSODs too, but I didn't get a minidump.
 

Attachments

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
Welcome to the W7Forums.

Looking at the last crash dump file, it looks like you have a Hardware Disk or Disk cabling fault.

You could try running the following from a command prompt as Administrator:
Code:
chkdsk /f /r
Code:
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc4000cbe0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000004d3a8860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800197c5d1, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
 
Ad

Advertisements

Joined
Jun 12, 2014
Messages
7
Reaction score
0
Thanks for the reply. Will run chkdsk tonight and report results.

Also, I ran HDTune about two weeks ago and it found a single damaged block, but once I ran chkdsk afterwards and repaired a bad cluster it disappeared. Right now if I run it everything is green, yet BSOD frequency hasn't changed.
 
Joined
Jun 12, 2014
Messages
7
Reaction score
0
Here are the results:
Code:
Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          15. 6. 2014 5:11:18
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Pete-VAIO
Description:


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)...
  291328 file records processed.                                       

File verification completed.
  6509 large file records processed.                                 

  0 bad file records processed.                                   

  0 EA records processed.                                         

  44 reparse records processed.                                    

CHKDSK is verifying indexes (stage 2 of 5)...
  372448 index entries processed.                                      

Index verification completed.
  0 unindexed files scanned.                                      

  0 unindexed files recovered.                                    

CHKDSK is verifying security descriptors (stage 3 of 5)...
  291328 file SDs/SIDs processed.                                      

Cleaning up 50 unused index entries from index $SII of file 0x9.
Cleaning up 50 unused index entries from index $SDH of file 0x9.
Cleaning up 50 unused security descriptors.
Security descriptor verification completed.
  40561 data files processed.                                         

CHKDSK is verifying Usn Journal...
  36887288 USN bytes processed.                                          

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x32a5e68000 for 0x10000 bytes.
  291312 files processed.                                              

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  2133776 free clusters processed.                                      

Free space verification is complete.
Windows has checked the file system and found no problems.

296441855 KB total disk space.
287322120 KB in 216240 files.
    180224 KB in 40562 indexes.
         8 KB in bad sectors.
    404395 KB in use by the system.
     65536 KB occupied by the log file.
   8535108 KB available on disk.

      4096 bytes in each allocation unit.
  74110463 total allocation units on disk.
   2133777 allocation units available on disk.

Internal Info:
00 72 04 00 2e eb 03 00 dd bf 06 00 00 00 00 00  .r..............
ca 3b 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.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-06-15T03:11:18.000000000Z" />
    <EventRecordID>63451</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Pete-VAIO</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

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)...
  291328 file records processed.                                       

File verification completed.
  6509 large file records processed.                                 

  0 bad file records processed.                                   

  0 EA records processed.                                         

  44 reparse records processed.                                    

CHKDSK is verifying indexes (stage 2 of 5)...
  372448 index entries processed.                                      

Index verification completed.
  0 unindexed files scanned.                                      

  0 unindexed files recovered.                                    

CHKDSK is verifying security descriptors (stage 3 of 5)...
  291328 file SDs/SIDs processed.                                      

Cleaning up 50 unused index entries from index $SII of file 0x9.
Cleaning up 50 unused index entries from index $SDH of file 0x9.
Cleaning up 50 unused security descriptors.
Security descriptor verification completed.
  40561 data files processed.                                         

CHKDSK is verifying Usn Journal...
  36887288 USN bytes processed.                                          

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x32a5e68000 for 0x10000 bytes.
  291312 files processed.                                              

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  2133776 free clusters processed.                                      

Free space verification is complete.
Windows has checked the file system and found no problems.

296441855 KB total disk space.
287322120 KB in 216240 files.
    180224 KB in 40562 indexes.
         8 KB in bad sectors.
    404395 KB in use by the system.
     65536 KB occupied by the log file.
   8535108 KB available on disk.

      4096 bytes in each allocation unit.
  74110463 total allocation units on disk.
   2133777 allocation units available on disk.

Internal Info:
00 72 04 00 2e eb 03 00 dd bf 06 00 00 00 00 00  .r..............
ca 3b 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.
</Data>
  </EventData>
</Event>
 

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
Mate,

I would strongly suggest that you back up your data somewhere and purchase new hard disk soon!

Once you have bad Sectors, it only gets worse.
296441855 KB total disk space.
287322120 KB in 216240 files.
180224 KB in 40562 indexes.
8 KB in bad sectors.
404395 KB in use by the system.
65536 KB occupied by the log file.
8535108 KB available on disk.
 
Joined
Jun 12, 2014
Messages
7
Reaction score
0
Hm, I think it should still be covered by warranty... are a bunch of bad sectors a sufficient enough reason for them to replace it?

Beyond the hard drive however, is there a possibility of a cabling defect in addition to that? Because the previous time the HDD was dying on me, it wasn't acting like this at all, there wasn't a single BSOD, just Windows freezing up for no reason.
 

clifford_cooley

VIP Member
Joined
Mar 8, 2009
Messages
5,059
Reaction score
1,184
are a bunch of bad sectors a sufficient enough reason for them to replace it?
Yes!

Bad sectors are hardware issues, with storage media that can make a machine unusable in a short period of time. If you are covered under warranty, they have no choice but to replace the drive. If they are not a service center, they will likely swap out the whole machine.
 
Ad

Advertisements

Joined
Jun 12, 2014
Messages
7
Reaction score
0
Okay then, I'll see what I can do after my exam period is over.

On another note, after a few days of working fine, no BSODs, one just suddenly happened right now. I just put down the computer while I went away for a sec, and when I returned, bam there it was. This time, when I tried to reboot Windows, the first time I even got a "disk read error: press ctrl+alt+del" instead. Seems like it's all going downhill fast?

Attaching the minidump that came out of it.

EDIT: Unrelated(?) to BSOD but maybe related to HDD - I've been getting these "Reset to device, \Device\RaidPort0, was issued." IastorA errors completely randomly, sometimes even two or three in a row. I've tried searching for what might that be caused by, updated my Intel Rapid Storage Technology two months ago, deactivated Link Power Management both in power settings and the program itself, and it still keeps occuring. This was happening even at the old harddrive, and it's just plain irritating and work disrupting. Any other possibilities on how to fix this? Might it have relation to the BSOD?
 

Attachments

Last edited:

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
Mate,

My apologies for my late responce.

You need to change the faulty disk. Because if the bad sectors are under the page file, when data is written to disk the data will become corrupt and cause crashes.

Let us know when you have changed the disk.

Bad sectors just get worse. I hope that your data is backed up.
 
Joined
Jun 12, 2014
Messages
7
Reaction score
0
Okay, thank you, I will do that soonish. However, I still want to ask, can it be related to anything else but the disk itself? Like RAM (even though several cycles of memtest came out fine) I ask because it seems that even multiple seasons of chkdsk didn't really reduce the frequency of BSODs much, if at all. I don't really want to send my laptop to repairs for a month only to discover that there's more busted hardware in it.
 

clifford_cooley

VIP Member
Joined
Mar 8, 2009
Messages
5,059
Reaction score
1,184
Many components can can trash data on the drive, causing data errors. But when the drive is reporting bad sectors, that is because the drive is having trouble reading/writing those sectors. It is a disk error not a data error. Data errors can be fixed, on the other hand disk errors are usually not serviceable (at least not by a common technician).
 
Ad

Advertisements

Shintaro

Moderator
Joined
Mar 1, 2012
Messages
2,137
Reaction score
252
If the VAIO is under warranty, get it repaired. Sony should check everything else, if not ask them to when you return it under warranty.
"A month"? I would find that strange amount of time for Sony to repair their laptops. That would destroy their reputation.
If it is not under warranty, then it normally no big deal to change a hard drive. Normally a couple of screws and a cable.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top