Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows just crashed on me


  • Please log in to reply

#1
RebelGamer137

RebelGamer137

    Member

  • Member
  • PipPipPip
  • 445 posts

My computer shutdown by itself and I got this error.

 

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    7a
  BCP1:    FFFFF6FC4000B0E0
  BCP2:    FFFFFFFFC0000185
  BCP3:    000000000F305860
  BCP4:    FFFFF8800161C4AC
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\021417-37611-01.dmp
  C:\Users\Warhawk\AppData\Local\Temp\WER-108951-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\windows\system32\en-US\erofflps.txt
 

 

Anything I can do to prevent this? I am using a Toshiba Satellite L755D-S5204 with Windows 7. I have had it for years too. Could it just be starting to die? Its hard other problems recently like lagging occasionally and freezing sometimes.


Edited by RebelGamer137, 14 February 2017 - 09:23 PM.

  • 0

Advertisements


#2
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,461 posts

There are many reasons why Blue Screen Of Death (BSOD) error happens only way to know what cause this error is to debug the BSOD memory dump file even then we may not get clear answers to why BSOD error happened. Please place all of the files stored within C:\Windows\Minidump folder into zip archive and attach the zip archive to your next post. 

I would not worry if BSOD happens once a while if it happens all the time then it needs to be dealt with.

 

 

I would like you to check the system integrity of your Windows OS installation.
 

  • Please right click the Windows logo (formerly the start button) at the bottom left of your screen.
  • Please select  "Command Prompt (Admin)"
  • Please type the following command and press the <Enter> key: sfc /scannow  (Please note that there is a space between 'sfc" and "/scannow".)
  • It should take about 20 minutes to run, if there are no serious errors.
  • If the System File Checker reports that some errors were fixed, but some remain; please reboot your computer and run the System File Checker from an Administrator Command Prompt, again.
  • If the System File Checker again reports that some errors were fixed, but some remain, please reboot your computer and run it a third time.
  • If "Resource Integrity Violations" (errors) are reported that could not be corrected, or were not corrected after a third SFC run, then please navigate to the folder: C:\Windows\Logs\CBS and copy the file "cbs.log" to your desktop immediately.  I am asking you do that because that file is dynamic, so I want to be able to examine a copy that is unchanged from the time that the System File Checker was run.
  • If there are errors that couldn't be corrected, let me know and I will provide you with instructions as to how to upload the file

 

 

 

I would also like you to execute Chkdsk  C:  /r  command from Command Prompt. You will be ask to schedule a C: partition error checking at next time you reboot your computer type Y and press Enter key.


Edited by FreeBooter, 15 February 2017 - 02:56 AM.

  • 0

#3
RebelGamer137

RebelGamer137

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 445 posts

Here is my minidump file. Please feel free to take a look.

Attached Files


  • 0

#4
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,461 posts

Make sure to execute chkdsk command.

 

 

 

JcJ91sx.pngGSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:

1.  Download GSmartControl and save it on your Desktop.

2.  Extract the content of the GSmartControl .zip archive and execute gsmartcontrol.exe.

3.  Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name).

4.  Click on the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete).

Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your topic.

Click on the Attributes tab and if you have any entries highlighted in red or pink, copy and paste their name in your next reply (or take a screenshot of the GSmartControl window and attach it in your next reply).

info_failing.png


  • 0

#5
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,547 posts

Here is my minidump file. Please feel free to take a look.

 

rar files are not used here, zip and upload the files requested by FreeBooter using the method below;

 

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.

2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.

3. Upload the zip folder using the More Reply Options tab, Choose File then the Attach This File tab., bottom left of the dialogue input box.


  • 0

#6
RebelGamer137

RebelGamer137

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 445 posts

EDIT: Here it is

Attached Files


Edited by RebelGamer137, 15 February 2017 - 06:56 PM.

  • 0

#7
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,461 posts
Hi RebelGamer137,

Please complete SFC, Chkdsk and GSmartControl requests i have ask you to complete and please report back with results.

Edited by FreeBooter, 15 February 2017 - 10:25 PM.

  • 0

#8
RebelGamer137

RebelGamer137

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 445 posts

It just blue screened again. Should I upload the mini dump again?


  • 0

#9
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,461 posts

Please follow my instructions at post #7.


  • 0

#10
RebelGamer137

RebelGamer137

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 445 posts

It Completed with read failure

 

2hrzkwo.png

 

 

 

 

21buo03.png

 

 

 

Here is the output

=== START OF INFORMATION SECTION ===
Device Model:     TOSHIBA MK6475GSX
Serial Number:    Y14GFEJ3S
LU WWN Device Id: 5 000039 3a6f012a1
Firmware Version: GT001M
User Capacity:    640,135,028,736 bytes [640 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Feb 23 05:42:59 2017 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 112)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline
data collection:         (  120) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 209) minutes.
SCT capabilities:            (0x003d)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       2084
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4047
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       1968
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   038   038   000    Old_age   Always       -       25036
 10 Spin_Retry_Count        0x0033   180   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       3953
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       105
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       21
193 Load_Cycle_Count        0x0032   082   082   000    Old_age   Always       -       184956
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       36 (Min/Max 15/47)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       125
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       8223
222 Loaded_Hours            0x0032   080   080   000    Old_age   Always       -       8216
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       358
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 7212 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 7212 occurred at disk power-on lifetime: 25023 hours (1042 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 1a 48 9e 1c 64  Error: WP at LBA = 0x041c9e48 = 68984392

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 48 30 09 59 40 00      00:21:10.418  WRITE FPDMA QUEUED
  61 08 38 88 81 3b 40 00      00:21:10.418  WRITE FPDMA QUEUED
  61 08 30 58 63 8e 40 00      00:21:10.417  WRITE FPDMA QUEUED
  60 68 e0 b0 da e4 40 00      00:21:10.404  READ FPDMA QUEUED
  61 08 b8 b0 56 8a 40 00      00:21:10.404  WRITE FPDMA QUEUED

Error 7211 occurred at disk power-on lifetime: 25023 hours (1042 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 5a 48 9e 1c 64  Error: WP at LBA = 0x041c9e48 = 68984392

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 80 a8 4a 3b 40 00      00:21:06.142  WRITE FPDMA QUEUED
  61 08 90 f0 ff 58 40 00      00:21:06.142  WRITE FPDMA QUEUED
  61 08 78 f0 59 8e 40 00      00:21:06.141  WRITE FPDMA QUEUED
  61 08 38 b8 56 8a 40 00      00:21:06.141  WRITE FPDMA QUEUED
  61 10 80 38 40 3b 40 00      00:21:06.141  WRITE FPDMA QUEUED

Error 7210 occurred at disk power-on lifetime: 25023 hours (1042 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 52 48 9e 1c 64  Error: WP at LBA = 0x041c9e48 = 68984392

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 d8 30 2c 3b 40 00      00:21:01.767  WRITE FPDMA QUEUED
  61 08 c8 58 f3 58 40 00      00:21:01.767  WRITE FPDMA QUEUED
  61 08 a0 e0 19 30 40 00      00:21:01.767  WRITE FPDMA QUEUED
  61 08 d8 88 2b 3b 40 00      00:21:01.767  WRITE FPDMA QUEUED
  61 08 c8 f8 d9 58 40 00      00:21:01.766  WRITE FPDMA QUEUED

Error 7209 occurred at disk power-on lifetime: 25023 hours (1042 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 4a 48 9e 1c 64  Error: WP at LBA = 0x041c9e48 = 68984392

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 e8 c8 1e 3b 40 00      00:20:57.465  WRITE FPDMA QUEUED
  61 08 f8 e0 19 30 40 00      00:20:57.465  WRITE FPDMA QUEUED
  61 08 e8 d0 11 3b 40 00      00:20:57.465  WRITE FPDMA QUEUED
  61 08 f8 d8 63 4b 40 00      00:20:57.464  WRITE FPDMA QUEUED
  61 08 e8 30 10 3b 40 00      00:20:57.464  WRITE FPDMA QUEUED

Error 7208 occurred at disk power-on lifetime: 25023 hours (1042 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 32 48 9e 1c 64  Error: WP at LBA = 0x041c9e48 = 68984392

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 e8 a0 0f 3b 40 00      00:20:53.143  WRITE FPDMA QUEUED
  61 08 d8 00 e1 7e 40 00      00:20:53.143  WRITE FPDMA QUEUED
  61 08 c8 70 dc 7e 40 00      00:20:53.143  WRITE FPDMA QUEUED
  61 08 a8 f8 d5 7e 40 00      00:20:53.143  WRITE FPDMA QUEUED
  61 08 a0 d0 cf 7e 40 00      00:20:53.143  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       00%     25036         68984392
# 2  Short offline       Completed without error       00%         3         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

 


  • 0

#11
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,461 posts

Hi RebelGamer137,

 

 

 

Can please backup your personal data to a different storage media as this hard disk is failing you need to purchase new hard disk drive.


  • 0

#12
RebelGamer137

RebelGamer137

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 445 posts

My laptop IS five years old so it might be a good idea to get another one.


  • 0

#13
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,461 posts

That is your choice but yes its a old laptop.


  • 0

#14
RebelGamer137

RebelGamer137

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 445 posts

I also have had this same computer freeze frequently when left idol. It has always done this occasionally but has been doing this more often is there a connection or is that unrelated.


  • 0

#15
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,461 posts

Not sure tell you the true but there is a chance its happening because hard disk is dying.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP