PDA

View Full Version : BSOD Win10 Custom Built PC



Andrewma
09-17-2015,
Hi guys,
If anyone could help or point me in the right direction I would be very grateful.

I have a custom built PC about a few years old and it has recently started crashing on me pretty consistently.

I'm a video editor and this machine is mainly used for rendering video files. This problem comes and goes but I usually find it happens whilst rendering a video. The system is overclocked (not by myself, the computer company scan.co.uk did it for me) and I believe this may be the cause of the issue?

System Info:
Win10 64bit
nvidia gtx 670
intel core i7 3930k @ 3.2ghz
Corsair 32gb DDR3 RAM
Asus Sabertooth x79

I have attached my minidump file in a .txt file for you to see.

Any help would be greatly appreciated
Thanks
Matt
Attached Files

http://www.bleepingcomputer.com/forums/public/style_extra/mime_types/txt.gif (http://www.bleepingcomputer.com/forums/index.php?app=core&module=attach&section=attach&attach_id=183147) minidump-crash.txt (http://www.bleepingcomputer.com/forums/index.php?app=core&module=attach&section=attach&attach_id=183147) 6.08KB

AndrewKn
09-19-2015,
More info on the STOP 0x101 errors can be found here: http://www.carrona.org/bsodindx.html#0x00000101
While this error is not solely hardware or software, it involves hardware often enough that I suggest starting with these free diagnostics: http://www.carrona.org/hwdiag.html


Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum) http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE: On problem systems it can take up to 20 minutes for the log files to complete. Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link): https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

AndrewHogy
09-21-2015,
Hi Usasma,
Thanks so much for the reply.

I've attached my perfmon + sysnative file. I'll look into the other links you sent me
Thanks
Matt
Attached Files



http://www.bleepingcomputer.com/forums/public/style_extra/mime_types/zip.gif (http://www.bleepingcomputer.com/forums/index.php?app=core&module=attach&section=attach&attach_id=183151) perfmon.zip (http://www.bleepingcomputer.com/forums/index.php?app=core&module=attach&section=attach&attach_id=183151) 174.56KB
http://www.bleepingcomputer.com/forums/public/style_extra/mime_types/zip.gif (http://www.bleepingcomputer.com/forums/index.php?app=core&module=attach&section=attach&attach_id=183152) SysnativeFileCollectionApp.zip (http://www.bleepingcomputer.com/forums/index.php?app=core&module=attach&section=attach&attach_id=183152) 547.7KB

AndrewHige
09-22-2015,
What is on your D: drive?

Perfmon shows that the dirty bit is set on your D: drive
This means that you must run CHKDKS /R /F in order to try and fix it.
Run it from an elevated (Run as administrator) Command Prompt (switch to the D: drive, then run "chkdsk /r /f" (without the quotes)

If this doesn't fix it, then the only way to fix it is with a format.

Your UEFI/BIOS (version 4210) dates from 2013. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 6 Windows Update hotfixes installed. Most build 10586 (TH2/1511) systems have more than this. Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important. Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

The WER section of MSINFO32 gives us a hint that this might be associated with video drivers or the video card.
But it's just a hint, nothing definite.

In addition to the diagnostics that I suggested in my previous post, I'd also suggest that you run Driver Verifier according to these instructions: http://www.carrona.org/verifier.html