New
#21
Please check in the event logs for chkdsk and let us know what chkdsk reported
Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
Please check in the event logs for chkdsk and let us know what chkdsk reported
Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
Here is the chkdsk report:
Code: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 ... 153344 file records processed. File verification completed. 3378 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 242814 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 614 unused index entries from index $SII of file 0x9. Cleaning up 614 unused index entries from index $SDH of file 0x9. Cleaning up 614 unused security descriptors. Security descriptor verification completed. 44736 data files processed. CHKDSK is verifying Usn Journal... 41408328 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 153328 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 236815830 free clusters processed. Free space verification is complete. Adding 1 bad clusters to the Bad Clusters File. Windows has made corrections to the file system. No further action is required. 976247807 KB total disk space. 28614892 KB in 101496 files. 78392 KB in 44737 indexes. 4 KB in bad sectors. 291199 KB in use by the system. 65536 KB occupied by the log file. 947263320 KB available on disk. 4096 bytes in each allocation unit. 244061951 total allocation units on disk. 236815830 allocation units available on disk. Internal Info: 00 57 02 00 44 3b 02 00 7c 59 04 00 00 00 00 00 .W..D;..|Y...... 3e 00 00 00 10 08 00 00 00 00 00 00 00 00 00 00 >............... Windows has finished checking your disk. Please wait while your computer restarts.
The hard drive itself should be fine now.
Code:Adding 1 bad clusters to the Bad Clusters File. Windows has made corrections to the file system. No further action is required.
With the quote below from your OP yes it does, however there are quite some things to try that can possibly cause it.
It would be helpful if you could provide us with a zip from the BSOD Posting Instructions, the data it contains (nothing personal) could be relevant to find the cause(s).I have done a fresh install of Windows 10 (wiping the previous partitions) and it's lagging even before I install any drivers.
Please read BSOD Posting Instructions & How to upload files
If you can't, no problem then we'll try a few hardware tests :)
Was your USB network adapter connected when you reinstalled Windows?
Please make sure the mouse drivers and keyboard drivers are up to date.
The keyboard drivers couldn't load proper.Code:+++ WER9 +++: Fault bucket , type 0 Event Name: PnPRequestAdditionalSoftware Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: USB\Vid_1532&Pid_0016&Rev_0100 // red marked is the PNP device ID on which you can search in msinfo32 to find what device it is. P3: 10.0.0.0 P4: 0409 P5: input.inf P6: * P7: P8: P9: P10: +++ WER5 +++: Fault bucket , type 0 Event Name: PnPRequestAdditionalSoftware Response: Not available Cab Id: 0 Problem signature: P1: x64 P2: USB\VID_045E&PID_0768&REV_0150&MI_01 P3: 10.0.0.0 P4: 0409 P5: input.inf P6: * P7: P8: P9: P10:
Code:Event[939]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2016-01-28T16:03:31.535 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-0NM01UQ Description: The driver \Driver\usbccgp failed to load for the device USB\VID_045E&PID_0768\6&3ae11b61&0&3.
I installed Razer Synapse for the mouse and Microsoft Keyboard Centre for the keyboard. I then restarted the computer and it shut down. Upon starting it up again, it did one long beep and one short beep and then crashed again. According to the motherboard manual, that means "motherboard or memory issues".