Corrupt Files, should I just reformat?

PLGhost187

Honorable
Dec 25, 2013
22
0
10,510
Hello All,

I have been having a few issues within the last 3 weeks that culminated, or so it seems, in a BSOD earlier today. The first issue was losing signal to my monitor while gaming (Dragon Age Inquisition) but the system stays on which occurred a few times. I then experienced a one-time issue where my pc rebooted to the user login screen without the system actually rebooting. Today, while playing GTA V, I got the BSOD shown in this pic by another member with the same issue http://postimg.org/image/q1ojgcyq3/ and have since learned that it is suspected to be a driver issue or a corrupted file issue. I ran sfc.exe /scannow and corrupted files were found but not fixed so my question is should I just reformat? Is it possible that there are other issues as well? Is there an easier option than reformatting? Thanks for the help in advance.

Regards,

Travis
 
Sorry my mistake, I should have made it clear that the error code may not be the exact same as the one in the pic. I was unable to write it down fully/get a pic in time and just used this pic just to illustrate the type of screen I got, not the exact error code. I am not sure what the part in the brackets was but I do know it was shorter than the one in the linked picture. Sorry for the confusion.

As for drivers, I had the newest driver when I was getting the signal loss. I reverted to two drivers previous a few days ago and got this BSOD today on my first GTA V gaming session. I still experience crashes from Dragon Age Inquisition.
 
On Sat 2015-06-06 11:02:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060615-3484-01.dmp
This was probably caused by the following module: ks.sys (ks+0x1F44E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800C517844E, 0xFFFFD00021CDAD00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 2015-06-06 11:02:39 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ladfgscamd64.sys (ladfGSCamd64!SBLMShutDownEngine+0x11E1B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800C517844E, 0xFFFFD00021CDAD00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ladfgscamd64.sys
product: Logitech GSeries Headset
company: Logitech
description: Capture Filter Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ladfgscamd64.sys (Capture Filter Driver, Logitech).
Google query: Logitech SYSTEM_SERVICE_EXCEPTION
 
Hello,

I just had another BSOD. This time it was a NTFS File System (ntfs.sys) error that occurred while playing GTA V. I made sure my mother board drivers, gfx card drivers, and windows were completely updated and tried GTA V again and got this error.
 
Here are the dump files for today's BSOD.

On Sun 2015-06-07 3:09:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060715-6453-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD00022B26A28, 0xFFFFD00022B26230, 0xFFFFF8016D2F3453)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 2015-06-07 3:09:11 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31EEC)
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD00022B26A28, 0xFFFFD00022B26230, 0xFFFFF8016D2F3453)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
I'm beginning to think you either have a memory stick thats flakey, or a CPU heat problem. Get a program that logs system temperatures in the background, so that you can come back after gaming and see what the highest temps were. If your CPU is getting close to 80c or hotter you have a problem. The heat problem could be a dirty fan, dirty heat block, fan not spinning fast enough, or it might be that the heatsink needs to be removed from the CPU and the thermal paste cleaned off, and everything re-done.

Once you know your computer is NOT over heating, I would also open up my computer, remove all but 1 stick of memory, and run MemTest on it. You can download that free program at the link below. Download the ISO image, and burn it to disc. Then boot your computer from that disc. Test each stick of memory for a lot of hours. I try to recommend 10 hours minimum, so probably set it up before going to bed, and then after you have woke up, let it go a few more hours. Do one stick a night until done. If any stick has errors, you will either see that info on the screen, or the computer might just lock up.
 
Hello Mark,

Thanks for your help. Any suggestion on which program I should use to monitor CPU temps that will allow me to check them after the crash? Also, I did a quick windows memory test and it found nothing. I recognize it is not as extensive as the memtest but can anything be assumed from the passing of that test? Thanks again.
 
Next time you go playing and it crashes, check that again. All I am trying to figure out right now is if the crash is temperature related. If its not, then you can move on to the next step.

This might take time, but we will isolate down what is causing this. One step at a time.
 
you have windows 8, run cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

this will attempt to fix corrupted file by getting clean copies from the microsoft update server.
reboot then run cmd.exe as an admin again and run
sfc.exe /scannow
and see if it completes without errors.
if it gets errors run a malwarebytes scan

also, update your ethernet driver if you have not already done so.

if you copy the memory .dmp file from c:\windows\minidump
to a server and post a link I can use the windows debugger and get a better idea of your systems problem.
more than the 0xc0000005 error code was caused by a bad memory address used by a device driver.

(various causes for that, overclocking drivers, memory corruption caused by bad drivers, actual problems with RAM timings in BIOS or physical RAM problems. run memtest86 to confirm memory timings are ok.)

for the file system bugchecks 0x24 ignore them for now but update your ethernet drivers.
 
Hello John,

Thanks for your reply, however I refreshed my pc a few days ago using the disc and that seems to have fixed the issue. I no longer have any corrupted files and have had a few gaming sessions with no BSOD. If the issue should reoccur I will post back here, thanks for the help from everyone.
 
Well, not everything, or possibly anything, was fixed by the refresh. While I did not get a BSOD, I did get the original issue where my monitor says "no signal" and goes to sleep but the audio from the game is still on. Where should I start?
 
No. But you should go into your BIOS and turn on XMP for the memory. That will let the motherboard read the memory chip on the memory stick so that it knows what settings to use with that memory.

I'm real late with this, HWinfo is a utility that will log temperatures while you use your system. When you run it, setup what you want it to monitor on the sensors tab, and let it run. Go play a game or something, and then when it crashes, you can go back and see if any of the temps were high or not.
 
I enabled XMP then ran memtest86 last night, no errors were found. Also, for the monitoring, how can I go back and check the temps if the crashes force me to restart my PC, or with the BSOD do it automatically? I'm familiar with monitoring temps but the crashes I experience, or the loss of signal to the monitor, are only corrected by rebooting and there is no point after the crash that I can check temps as the display is lost, or the BSOD is displayed then my comp shuts down.