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

Many issues since reinstalling - Blinking Screen!


  • Please log in to reply
21 replies to this topic

#1 trimad22

trimad22

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:05:39 AM

Posted 27 June 2016 - 08:39 AM

I have a Samsung np300e5e - It has been giving me issues lately so I reinstall Windows 7 with SP1 (64 bit).
I was adding the drivers needed and all of a sudden the screen flashes like a strobe light. I don't have much installed on it yet but it is hard on the eyes to get much done.

When I boot in safe mode it doesn't flash, the windows startup screen does not flash nor does the password only when it gets to the desktop does it start.

I am not sure what is the issue but figured maybe someone here could help. In searching most topic were about adobe or conflicting software but I am not sure where to start - No adobe installed.

Any help is appreciated -- thanks :) 



BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 10:02 AM

How did you reinstall Windows 7?  Installation disc?

 

That computer should have a System Recovery Partition which can restore the operating system to the condition it was in when it was first started.  It install all of the drivers as well.

 

If the graphics works in Safe Mode I suspect that you have a graphics driver issue.  Have you gone to the Samsung website to download the drivers for this computer?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 10:32 AM

I should explain that Safe Mode uses a limited number of files and drivers.  It does not use the graphics driver that came with the computer, it uses a Windows graphic driver which is part of the operating system.  Because the  graphics work in Safe Mode but not normally this points to there being a problem with the Samsung graphics driver.  I suspect that if you used a disc or flash drive to install the operating system.  If this is what you have done you will need to either use the System Recovery Partition to reinstall the operating system and the Samsung drivers.  This would be the quickest way to resolve this.  Alternatively, you could go to the Samsung website and download the drivers needed for this computer.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#4 trimad22

trimad22
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:05:39 AM

Posted 27 June 2016 - 10:38 AM

Thanks -- I just uninstalled the graphics driver and it cleared right up! I still need to install one because it is messed up but wanted to get the main issue resolved which is it is not allowing me to do a windows update -- I am getting an error 800B0100 - I have done all that is required in this article but still get the same error -- https://support.microsoft.com/en-us/kb/956702
Should I start a new thread? Seems I have lots of issues :/ 



#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 11:00 AM

I don't see any reason to open another topic, at least at this point.

 

Did you do all of the suggested steps for Windows 7?

 

Run the Update Troubleshooter?

 

Run sfc /scannow?

 

Run the Update Readiness Tool?

 

The Troubleshooter should have listed what was found and repaired.

 

Did the sfc /scannow have any integrity issues found?  

If it did please post the sfc /scannow log.  Use the instructions below.

 

Click on the Start orb rsz_1rsz_1rsz_start_orb_zpshjewtibd.png then type cmd in the Search box. 
 
CMD will appear above the search box, right click on it and select Run as administrator.
 
When the Elevated Command Prompt opens copy and paste the command below, then press Enter.
 
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\Desktop\sfcdetails.txt"
 
This will place a new icon on the desktop titled sfcdetails.  Double click on this icon to open 
the CBS log, copy and paste the log in your topic.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 trimad22

trimad22
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:05:39 AM

Posted 27 June 2016 - 11:21 AM

 

I don't see any reason to open another topic, at least at this point.

 

Did you do all of the suggested steps for Windows 7?

 

Run the Update Troubleshooter?

 

Run sfc /scannow?

 

Run the Update Readiness Tool?

 

The Troubleshooter should have listed what was found and repaired.

 

Did the sfc /scannow have any integrity issues found?  

If it did please post the sfc /scannow log.  Use the instructions below.e a

 

I did all the above steps and no, no integrity issues found

 

Click on the Start orb rsz_1rsz_1rsz_start_orb_zpshjewtibd.png then type cmd in the Search box. 
 
CMD will appear above the search box, right click on it and select Run as administrator.
 
When the Elevated Command Prompt opens copy and paste the command below, then press Enter.
 
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\Desktop\sfcdetails.txt"
 
This will place a new icon on the desktop titled sfcdetails.  Double click on this icon to open 
the CBS log, copy and paste the log in your topic.
 
 
I copied the above link and it created a blank notepad call sfcdetails.
No CBS log though.

 

 

 


Edited by trimad22, 27 June 2016 - 11:34 AM.


#7 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 11:30 AM

There those of us who will not download anything to our computers unless we know exactly what it contains.  Please post the CBS log in your topic.  This may be a large file, if this is the case break it into smaller parts and post them one at a time.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#8 trimad22

trimad22
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:05:39 AM

Posted 27 June 2016 - 11:34 AM

Ah gotcha -- there are 3 files -- CBS, CheckSUR and CheckSUR.persist -- Here is the CBS if the others are needed I can post those too:
2016-06-27 12:02:11, Info                  CBS    Starting TrustedInstaller initialization.
2016-06-27 12:02:11, Info                  CBS    Loaded Servicing Stack v6.1.7601.17514 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\cbscore.dll
2016-06-27 12:02:13, Info                  CSI    00000001@2016/6/27:16:02:13.391 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7feeb7be94d @0x7fef7149839 @0x7fef71134d3 @0xff2be97c @0xff2bd799 @0xff2bdb2f)
2016-06-27 12:02:13, Info                  CSI    00000002@2016/6/27:16:02:13.391 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7feeb7be94d @0x7fef7196806 @0x7fef7162a9c @0x7fef71135a9 @0xff2be97c @0xff2bd799)
2016-06-27 12:02:13, Info                  CSI    00000003@2016/6/27:16:02:13.391 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7feeb7be94d @0x7fefa5d8728 @0x7fefa5d8856 @0xff2be474 @0xff2bd7de @0xff2bdb2f)
2016-06-27 12:02:13, Info                  CBS    Ending TrustedInstaller initialization.
2016-06-27 12:02:13, Info                  CBS    Starting the TrustedInstaller main loop.
2016-06-27 12:02:13, Info                  CBS    TrustedInstaller service starts successfully.
2016-06-27 12:02:13, Info                  CBS    SQM: Initializing online with Windows opt-in: False
2016-06-27 12:02:13, Info                  CBS    SQM: Cleaning up report files older than 10 days.
2016-06-27 12:02:13, Info                  CBS    SQM: Requesting upload of all unsent reports.
2016-06-27 12:02:13, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2016-06-27 12:02:13, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2016-06-27 12:02:13, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2016-06-27 12:02:13, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2016-06-27 12:02:13, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
2016-06-27 12:02:13, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
2016-06-27 12:02:13, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x114fb90
2016-06-27 12:02:13, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
2016-06-27 12:02:13, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x204
2016-06-27 12:02:13, Info                  CSI    00000007@2016/6/27:16:02:13.407 CSI perf trace:
CSIPERF:TXCOMMIT;319
2016-06-27 12:02:13, Info                  CBS    NonStart: Success, startup processing not required as expected.
2016-06-27 12:02:13, Info                  CBS    Startup processing thread terminated normally
2016-06-27 12:02:13, Info                  CSI    00000008 CSI Store 4087632 (0x00000000003e5f50) initialized
2016-06-27 12:02:13, Info                  CBS    Session: 30527629_1154652009 initialized by client WindowsUpdateAgent.
2016-06-27 12:02:13, Info                  CBS    Read out cached package applicability for package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320, ApplicableState: 80, CurrentState:64
2016-06-27 12:02:13, Info                  CBS    Session: 30527629_1154652010 initialized by client WindowsUpdateAgent.
2016-06-27 12:02:13, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Info                  CBS    Mark store corruption flag because of package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Info                  CBS    Failed to initialize package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320, from path: \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320.mum, existing package: 1 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Info                  CBS    Failed to resolve package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Info                  CBS    Failed to populate children. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Info                  CBS    Failed to initialize internal package for package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Info                  CBS    Delay load failed for package: WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:13, Error                 CBS    Delay Initialization Failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:17, Info                  CBS    Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20160627160211.cab.
2016-06-27 12:02:47, Info                  CBS    Session: 30527629_1498788613 initialized by client WindowsUpdateAgent.
2016-06-27 12:02:47, Info                  CBS    Read out cached package applicability for package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320, ApplicableState: 80, CurrentState:64
2016-06-27 12:02:47, Info                  CBS    Session: 30527629_1498788614 initialized by client WindowsUpdateAgent.
2016-06-27 12:02:47, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Info                  CBS    Mark store corruption flag because of package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Info                  CBS    Failed to initialize package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320, from path: \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320.mum, existing package: 1 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Info                  CBS    Failed to resolve package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Info                  CBS    Failed to populate children. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Info                  CBS    Failed to initialize internal package for package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Info                  CBS    Delay load failed for package: WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:47, Error                 CBS    Delay Initialization Failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Info                  CBS    Session: 30527629_1507212628 initialized by client WindowsUpdateAgent.
2016-06-27 12:02:48, Info                  CBS    Read out cached package applicability for package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320, ApplicableState: 80, CurrentState:64
2016-06-27 12:02:48, Info                  CBS    Session: 30527629_1507212629 initialized by client WindowsUpdateAgent.
2016-06-27 12:02:48, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Info                  CBS    Mark store corruption flag because of package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Info                  CBS    Failed to initialize package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320, from path: \\?\C:\Windows\Servicing\Packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~fr-FR~7.6.7600.320.mum, existing package: 1 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Info                  CBS    Failed to resolve package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Info                  CBS    Failed to populate children. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Info                  CBS    Failed to initialize internal package for package: WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Info                  CBS    Delay load failed for package: WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2016-06-27 12:02:48, Error                 CBS    Delay Initialization Failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]


 



#9 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 11:42 AM

You still have not answered my questions in post #2.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#10 trimad22

trimad22
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:05:39 AM

Posted 27 June 2016 - 11:48 AM

How did you reinstall Windows 7?  Installation disc?

 

 

That computer should have a System Recovery Partition which can restore the operating system to the condition it was in when it was first started.  It install all of the drivers as well.

 

If the graphics works in Safe Mode I suspect that you have a graphics driver issue.  Have you gone to the Samsung website to download the drivers for this computer?

 

 

Installation DVD is what was used and  I am not sure how to answer the rest as it was my husband who actually installed it. He just left me with the mess!
Drivers I got off Samsung website.

 

 

Sorry it was related to graphics so I wasn't ignoring the question just missed it



#11 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 12:15 PM

<_< You still have not answered my question.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#12 trimad22

trimad22
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:05:39 AM

Posted 27 June 2016 - 12:21 PM

<_< You still have not answered my question.

 

I am sorry - Which question did I miss?



#13 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 01:07 PM

How did you reinstall Windows 7?  Installation disc?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#14 trimad22

trimad22
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Local time:05:39 AM

Posted 27 June 2016 - 01:40 PM

In post #11 I did respond with the following --

 

Installation DVD is what was used and  I am not sure how to answer the rest as it was my husband who actually installed it. He just left me with the mess!
Drivers I got off Samsung website.

 

 

Sorry it was related to graphics so I wasn't ignoring the question just missed it



#15 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:39 AM

Posted 27 June 2016 - 01:49 PM

Please use the instructions below to perform a Repair Installation.  This is poorly named as it is not an installation, but has options in the System Recovery Options which include a Startup Repair which should repair the corrupt files seen in the sfc /scannow.

 

Repair Installation Instructions
 
Attention:  In order to boot from the installation disc you may need to change the boot order in the BIOS so that the optical driver is the first device in the boot order, and the HDD/SSD is the second devcice.
 
1.  Place the installation disc in the tray of the CD/DVD drive, close the tray and restart the computer.
 
2.  You will be prompted to press any key to start the installation, do so.
 
At this point the setup process will load files, this will take several minutes.
 
3.  You will now need to choose the  Language, Time and currency format, and Keyboard or input method that you'd like to use.
 
After this is done click on Next.
 
w71_zps6dbda47e.png
 
4.  Click on the Repair your computer link at the bottom-left of the Install Windows window.
 
This link will begin the Windows 7 System Recovery Options.
 
w72_zps2a656a0c.png
 
5.  System Recovery Options will now search your hard drive(s) for any Windows 7 installations.  This will take several minutes.
 
No participation is required on your part at this time, wait till it has finished and the next window opens.
 
w73_zpsd5483f05.png
 
6.  Choose the Windows 7 installation that you'd like to perform the Startup Repair on, then click on Next
 
w74_zps490f9a17.png
 
7.  Click on the Startup Repair link from list of recovery tools in System Recovery Options.
 
w75_zps9941e858.png
 
For a future reference, there are several other diagnostic and recovery tools available in the Windows 7 System Recovery Options including System Restore, System Image Recovery, Windows Memory Diagnostic, and Command Prompt.
 
8.  The Startup Repair tool will now search for problems in the system files.
 
If Startup Repair finds a problem with any system files the tool may suggest a solution which you will need to confirm, or may solve the problem automatically.
 
w76_zps3dd75d83.png
 
9.  Startup Repair will now attempt to repair whatever problems it found with system files.  
 
Note:  If Startup Repair did not find any problems with system files you won't see this step.
 
w77_zpsd8be95eb.png
 
Important: Your computer may or may not restart several times during this repair process.  This is normal, you should allow it to continue until you see the Restart your computer to complete the repairs window. 
 
10.  Click on Finish, this will restart your computer.
 
w78_zpsd49257fb.png
 
It is possible that the Startup Repair will not be able to fix the problem.  If the Startup Repair tool determines this, it may automatically run the the repair after your computer restarts.  If it does not automatically run the repair but you are still having problems with Windows 7 repeat these steps to run Startup Repair again manually.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users