Welcome to the Spiceworks Community. The community is home to millions of IT Pros in small-to-medium businesses. Are you an IT Pro? Creating your account only takes a few minutes. Yeah, I was playing earlier and having the normal horrid lag and high ping. Two times I was logged out to the log-in screen. I closed the client and updated my video driver as well as a couple windows 10 updates then rebooted.

Code: RTCore64.sys Wed May 25 02: (42941D90) - Riva Tuner - Real Temps monitoring tool/ EVGA overclocking utility, Lycosa.sys Wed Sep 30 00: (4AC2E27E) - Razer Tarantula Keyboard Driver - lvrs64.sys Wed Oct 07 04: (4ACC510F) - Logitech Quickcam - lvuvc64.sys Wed Oct 07 04: (4ACC513C) - Logitech Quickcam - LVPr2M64.sys Wed Oct 07 04: (4ACC50CA) - Logitech Quickcam - Logitech Quickcam - Riva Tuner - Razer Tarantula Keyboard Driver - Avast also named probable cause. Remove it - Avast Removal Tool - Reboot upon completion. Install MSE - One of the dumps was corrupted and listed a 0xc0000005 exception code = memory access violation. Code: Event[3255]: Log Name: System Source: Ntfs Date: 2010-09-27T20:04:25.377 Event ID: 55 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Gieryic-PC Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Device HarddiskVolume2. Event[3102]: Log Name: System Source: Disk Date: 2010-09-27T21:19:05.954 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Gieryic-PC Description: The driver detected a controller error on Device Harddisk1 DR1.That's definitely referring to your Windows partition - the System Reserved space would be Device HarddiskVolume1 and Device Harddisk1 DR0 respectively, I believe.

Definitely run the chkdsk /r /f as John suggested and let us know if it finds anything. Quote: To see the Chkdsk log follow these steps: Open The Event Log. Control Panel (Classic View) -> Administrative Tools -> Event Viewer (3rd choice) The ChkDsk Log is found in. Windows Logs (2nd choice on left) -> Application (1st sub-choice) This will display a number of information logs in the center pane, many of them from the most recent Windows startup.

You will notice the 1-2 hour time difference in events if you rebooted to scan (time spend runnign chkdsk). This should help you identify the startup events after the scan.

About half way down the list of logs, look for the item Wininit in the source column. This will contain the log data for the ChkDsk scan prior to the boot. Hope this information is helpful Find the log then copy/paste its contents to your next post.

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. CHKDSK is verifying files (stage 1 of 5). 249088 file records processed. File verification completed. 111 large file records processed.

0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5).

320740 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5). 249088 file SDs/SIDs processed. Cleaning up 149 unused index entries from index $SII of file 0x9. Cleaning up 149 unused index entries from index $SDH of file 0x9. Cleaning up 149 unused security descriptors. Security descriptor verification completed. 35827 data files processed.