Kindly I ask your attention.
Could you be so kind to update additional information like Operating System, Type (x32 or x64) (Start/My Computer (right click on it and click Backdrop), now a windows will open up with all the data you need, look if a Service Pack is installed), all the hardware information?
Did it happen after an upgrade or Service Pack installation?
Did you create an Restore Signal and/or Organisation Backup before that time?
Did y'all create a Windows Recovery/Rescue Disk?
Do you have the original installation deejay?
Is there an fault bulletin?
Does it happen in Save Mode (printing f8 or and so to get the extended kicking mode) too?
Software to view the problems?
Blue Screen Viewer might assistance.
https
/world wide web.google.nl/#q=Bluish+Screen+Viewer+download&spell=ane
Did you try the next:
Kickoff the Command Prompt ellevated (Start/All Programs/Bureau_Accessoires/Correct click on Command Prompt and click 'Open with Ambassador Rights/Open every bit Administrator'), so copy the next and press Enter:
sfc /scannow
When the plan has beingness done, copy the next line and press Enter:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
When I'm not misstaken, the log file will exist copied to the desktop. Here you tin can open information technology and see what happened.
To view these files, you could also apply Bluish Screen Viewer. You lot can search on the internet for answers and you might be able to find out which commuter information technology could be that's creating the issues.
You could do as well:
Conducting a CHKDSK can accept some time, peculiarly if using the /R parameter, which causes CHKDSK to attempt to recover information, and the results are often not visible, for various reasons. The results of a CHKDSK conducted on restart using Windows 2000 or later operating systems are written to the Application Log, with a "Source" name of Wininit or Winlogon, except on some instances of the Windows 7 operating arrangement, where the events may have a "Source" name of "Chkdsk".
The standard version of CHKDSK supports the following switches:
filename FAT only. Specifies the file or ready of files to check for fragmentation. Wildcard characters (* and ?) are allowed.
path Fatty simply. Specifies the location of a file or gear up of files within the folder construction of the volume.
size NTFS just. Changes the log file size to the specified number of kilobytes. Must be used with the /50 switch.
volume FAT and NTFS (NTFS back up is unofficial, but it works normally). Specifies the drive alphabetic character (followed by a colon), mount signal, or book name.
/c NTFS only. Skips checking of cycles inside the folder structure.
/f Fixes errors on the volume. The volume must be locked. If CHKDSK cannot lock the volume, it offers to bank check it the next time the calculator starts.
/i NTFS only. Performs a less vigorous check of alphabetize entries.
/l[:size] NTFS only. Displays current size of the log file. If size is specified, changes the log file to that size (in kilobytes).
/p Checks disk even if it is not flagged as "dirty" (just bachelor in the Recovery Console).
/r Locates bad sectors and recovers readable information (implies /f and /p). Unreadable information is lost. If CHKDSK cannot lock the volume, it offers to check it the next time the computer starts.
/five On Fatty: Displays the full path and name of every file on the volume. On NTFS: Displays cleanup messages, if any.
/10 NTFS only. Forces the volume to dismount get-go, if necessary. All opened handles to the volume are then invalid (implies /f).
/b NTFS merely, since Windows Vista. Clears the listing of bad clusters on the volume and rescans all clusters for errors (implies /r).
/? Displays the listing of available CHKDSK parameters.
When running CHKDSK from the Recovery Panel the options are different. The /p is not read-only every bit in the standard version but corrects errors :[2]
/p Fixes errors on the volume. Same as the /f option in standard CHKDSK.
/r Locates bad sectors and recovers readable data (implies /f and /p). Takes much longer to run than /p past itself.
CHKDSK requires the bulldoze not to be locked. Therefore, after a command prompt with the syntax
chkdsk [volume]: /[switch] /[switch] ... /[switch]
if the bulldoze cannot be locked, CHKDSK prints:
Chkdsk cannot run considering the volume is in use by another process. Would yous like to schedule this volume to be checked
the next time the system restarts? (Y/N)
If "y" is selected, CHKDSK will run on restart. If information technology does so, information technology prints that a disk check has been scheduled, i.east.
What did all the tests say?
Hopefully I let you known enough, that you volition find the answers y'all seek!
Good luck & have fun doing it!
All-time Regards,
MeneerWitte
Comments
Post a Comment