Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Screen turns black on a specific time.


  • Please log in to reply
1 reply to this topic

#1 ZuluFoxtrot

ZuluFoxtrot

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Philippines
  • Local time:10:42 PM

Posted 26 August 2017 - 03:45 AM

hi everyone!

 

so here is the problem. recently, my laptop screen on a specific time of between 5pm to 7pm since tuesday... the screen blinks a couple of times and then turns black but the cursor is still visible. and when i try to press ctrl+alt+del, then screen then turns gray and the cursor is still visible and moving around it can detect links but nothing happening when i click it. the only thing i can get out of it is manually turning the laptop off (long pressing the power button). i tried doing a check disk (/f /r /x) viewed the log, and i really don't know what i am looking at but this caught my attention (attached screenshots). something have to do with the windows photo app.. do you think this could be the cause? im gonna try to uninstall it and see if the problem is still going to exist.

 

here's the event log of the check disk:

 

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          23/08/2017 7:23:16 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      GHOST
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.                         
 
Stage 1: Examining basic file system structure ...
  162560 file records processed.                                                        
 
File verification completed.
  4910 large file records processed.                                   
 
  0 bad file records processed.                                     
 
 
Stage 2: Examining file name linkage ...
  217258 index entries processed.                                                       
 
Index verification completed.
  0 unindexed files scanned.                                        
 
  0 unindexed files recovered to lost and found.                    
 
 
Stage 3: Examining security descriptors ...
Cleaning up 700 unused index entries from index $SII of file 0x9.
Cleaning up 700 unused index entries from index $SDH of file 0x9.
Cleaning up 700 unused security descriptors.
Security descriptor verification completed.
  27350 data files processed.                                           
 
CHKDSK is verifying Usn Journal...
  39632856 USN bytes processed.                                                           
 
Usn Journal verification completed.
 
Stage 4: Looking for bad clusters in user file data ...
  162544 files processed.                                                               
 
File data verification completed.
 
Stage 5: Looking for bad, free clusters ...
  19135092 free clusters processed.                                                       
 
Free space verification is complete.
 
Windows has scanned the file system and found no problems.
No further action is required.
 
 104857599 KB total disk space.
  27962372 KB in 123814 files.
     81796 KB in 27351 indexes.
         0 KB in bad sectors.
    273059 KB in use by the system.
     65536 KB occupied by the log file.
  76540372 KB available on disk.
 
      4096 bytes in each allocation unit.
  26214399 total allocation units on disk.
  19135093 allocation units available on disk.
 
Internal Info:
00 7b 02 00 41 4e 02 00 d2 69 04 00 00 00 00 00  .{..AN...i......
ef 00 00 00 39 00 00 00 00 00 00 00 00 00 00 00  ....9...........
 
Windows has finished checking your disk.
Please wait while your computer restarts.
 
Event Xml:
  <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="2017-08-23T11:23:16.442200900Z" />
    <EventRecordID>5778</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>GHOST</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.                         
 
Stage 1: Examining basic file system structure ...
  162560 file records processed.                                                        
 
File verification completed.
  4910 large file records processed.                                   
 
  0 bad file records processed.                                     
 
 
Stage 2: Examining file name linkage ...
  217258 index entries processed.                                                       
 
Index verification completed.
  0 unindexed files scanned.                                        
 
  0 unindexed files recovered to lost and found.                    
 
 
Stage 3: Examining security descriptors ...
Cleaning up 700 unused index entries from index $SII of file 0x9.
Cleaning up 700 unused index entries from index $SDH of file 0x9.
Cleaning up 700 unused security descriptors.
Security descriptor verification completed.
  27350 data files processed.                                           
 
CHKDSK is verifying Usn Journal...
  39632856 USN bytes processed.                                                           
 
Usn Journal verification completed.
 
Stage 4: Looking for bad clusters in user file data ...
  162544 files processed.                                                               
 
File data verification completed.
 
Stage 5: Looking for bad, free clusters ...
  19135092 free clusters processed.                                                       
 
Free space verification is complete.
 
Windows has scanned the file system and found no problems.
No further action is required.
 
 104857599 KB total disk space.
  27962372 KB in 123814 files.
     81796 KB in 27351 indexes.
         0 KB in bad sectors.
    273059 KB in use by the system.
     65536 KB occupied by the log file.
  76540372 KB available on disk.
 
      4096 bytes in each allocation unit.
  26214399 total allocation units on disk.
  19135093 allocation units available on disk.
 
Internal Info:
00 7b 02 00 41 4e 02 00 d2 69 04 00 00 00 00 00  .{..AN...i......
ef 00 00 00 39 00 00 00 00 00 00 00 00 00 00 00  ....9...........
 
Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>
 
 

Attached Files

  • Attached File  03.PNG   447.65KB   0 downloads
  • Attached File  02.PNG   436.66KB   0 downloads
  • Attached File  01.PNG   400.59KB   0 downloads


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:42 AM

Posted 26 August 2017 - 06:23 AM

Let's try looking at these 2 sets of reports:

Report Set #1)  Please run this report collecting tool (even though you may not be experiencing BSOD's) so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.

If you have problems with it running it, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

Report Set #2)  Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

While waiting for a reply, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps - if uncertain, please ask.

To make it work (log the temps to a file) you have to do BOTH of the below:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.



 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users