Windows 10: Newly DIY Built PC with BSOD Issues

My PC was only built about a week ago, and has many different BSODs throughout the week.

I have managed to solve quite a few of them, and currently these are the ones that are still bugging me, mainly ntoskrnl.exe

I have tried memtest and windows memory diagnostic tool to check for ram issues but they both passed.

:)

 

Getting random BSODs on newly built PC

These blue screens come out of no where and usually says scpvbus.sys or kmode exception not handles

 

Getting random BSODs on newly built PC

Please upload no more than three copies
of your dump files that were created during the last 14 days as shared files to your OneDrive with a link here.




Dump files are usually found at c:\windows\minidump. You may need to change your settings in Windows to be able to see the files. To show hidden files select the keyboard shortcut
Win+S, type File Explorer Options in the Search box and click Folder Options in the drop down menu. Select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and
"Hide protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.



What is your computer make and model? If not a branded computer what is your motherboard make and model?



Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please, HTML files are less easy
to work with.

DriverView: Loaded Windows Drivers List



Please provide a copy of your System Information file. To access your System Information file select the keyboard shortcut
Win+R, type msinfo32 and press the ENTER
key. Select File, Export and give the file a name noting where it is located.
Files in the txt file format are preferred. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information
is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here.



For help with OneDrive see paragraph 9.3:

gerrys template

 

Could you also run your system in normal mode and make a new zip and upload it, the current one is from safemode.

Anyway the dumpfiles are
Code: BugCheck 1000007E, {ffffffffc0000005, fffff800df98484d, ffff9880ce4e7ef8, ffff9880ce4e7720} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpCallDriver+7c )[/quote] This points to HID= Human interface devices.( mouse keyboard, gamecontrollers, etc.)

In the msinfo32

In the WER= windows error report

It looks that a connected HID device( probably usb) could be the cause.

Use/start your system as bare as possible only with mouse and keyboard and see if this stops the BSOD.
Then connect one by one the other devices and maybe you can find the guilty one.

 

I just got a few more bsods *Sad heres an updated one

 

All the dumpfiles mention memory corruption.

Did you test your memory according to this tutorial.
How to run "Memtest"
MemTest86+ - Test RAM - Windows 10 Tutorials
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

You can stop the test even if a single error is found during the test.
Otherwise continue the test for 8-10 passes and post a screenshot with next reply.
8 passes is the recommended bare minimum but more passes will give better result.

 

I tried memtest86 (no +) on 1 of the sticks which i think is the functional one, and it gave me this bsod ONLY when i try to stream to twitch and play overwatch, and that happens about 15mins in.

I ran it overnight and it got 8 passes, so im not sure if this bsod is still related to memory corruption.

I am going to try the other stick overnight and see if it is the actual faulty one.

Here is the latest one.

 

The last dumpfile is
Code: Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff801a231ff5e, ffff99013dde0a10, 0} Probably caused by : hardware ( nt!FsRtlpOplockFsctrlInternal+6 ) Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff801a231ff5e, Address of the instruction which caused the bugcheck Arg3: ffff99013dde0a10, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%p verwijst naar geheugen op 0x%p. Het geheugen kan niet worden %s. FAULTING_IP: nt!FsRtlpOplockFsctrlInternal+6 fffff801`a231ff5e 20448940 and byte ptr [rcx+rcx*4+40h],al CONTEXT: ffff99013dde0a10 -- (.cxr 0xffff99013dde0a10;r) rax=ffff99013dde1428 rbx=0000000000000000 rcx=ffffd789f3879928 rdx=ffff880e24008b80 rsi=0000000000090240 rdi=ffffd789f38798d0 rip=fffff801a231ff5e rsp=ffff99013dde1428 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=ffff99013dde14c8 r11=ffff99013dde1440 r12=ffffd789f3879790 r13=0000000000090268 r14=ffff880e2aeb6b58 r15=0000000000000001 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!FsRtlpOplockFsctrlInternal+0x6: fffff801`a231ff5e 20448940 and byte ptr [rcx+rcx*4+40h],al ds:002b:ffff35b1`c1a5fe08=?? Last set context: rax=ffff99013dde1428 rbx=0000000000000000 rcx=ffffd789f3879928 rdx=ffff880e24008b80 rsi=0000000000090240 rdi=ffffd789f38798d0 rip=fffff801a231ff5e rsp=ffff99013dde1428 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=ffff99013dde14c8 r11=ffff99013dde1440 r12=ffffd789f3879790 r13=0000000000090268 r14=ffff880e2aeb6b58 r15=0000000000000001 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!FsRtlpOplockFsctrlInternal+0x6: fffff801`a231ff5e 20448940 and byte ptr [rcx+rcx*4+40h],al ds:002b:ffff35b1`c1a5fe08=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre MISALIGNED_IP: nt!FsRtlpOplockFsctrlInternal+6 fffff801`a231ff5e 20448940 and byte ptr [rcx+rcx*4+40h],al LAST_CONTROL_TRANSFER: from fffff801a231ff51 to fffff801a231ff5e STACK_TEXT: ffff9901`3dde1428 fffff801`a231ff51 : 00000000`00000000 ffff880e`2b6755f0 00000000`00000001 ffff880e`2aeb6b58 : nt!FsRtlpOplockFsctrlInternal+0x6 ffff9901`3dde1430 fffff808`0e0bc5d1 : ffff880e`2aeb6b58 ffffd789`f3879790 00000000`00000000 00000000`00090240 : nt!FsRtlOplockFsctrlEx+0x11 ffff9901`3dde1470 fffff808`0e0f46bb : ffff880e`2aeb6b58 ffff880e`24008b80 ffff880e`00000000 ffff880e`00000000 : NTFS!NtfsOplockRequest+0x20d ffff9901`3dde1520 fffff808`0e0f4c37 : ffff880e`2aeb6b58 ffff880e`24008b80 ffff880e`24008b80 00000000`00000000 : NTFS!NtfsUserFsRequest+0x25b ffff9901`3dde15a0 fffff808`0d405206 : ffff880e`2c447c00 fffff808`0d403386 ffff880e`24008b80 ffff880e`24008f68 : NTFS!NtfsFsdFileSystemControl+0x117 ffff9901`3dde16b0 fffff808`0d4335a0 : ffff880e`22ee17c0 00000000`00000040 000000ad`caa7f400 ffff880e`248aec00 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a6 ffff9901`3dde1740 fffff801`a2318cd0 : ffff880e`2b675650 00000000`00000002 00000000`00000000 ffff880e`00000000 : FLTMGR!FltpFsControl+0x110 ffff9901`3dde17a0 fffff801`a2317bb4 : ffff9901`00000001 ffff880e`2b675604 00000000`00000000 ffff9901`3dde1b00 : nt!IopSynchronousServiceTail+0x1a0 ffff9901`3dde1860 fffff801`a232524a : 00000000`00000000 00000000`00000000 00000000`00000000 00007ffc`7bbec668 : nt!IopXxxControlFile+0x674 ffff9901`3dde19a0 fffff801`a1fdf393 : 00000000`00000102 00000000`00000001 00000000`00000000 ffff880e`00000002 : nt!NtFsControlFile+0x56 ffff9901`3dde1a10 00007ffc`8e3467f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 000000ad`caa7f368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`8e3467f4[/quote] Advice also test your Harddisk and SSD.

 

So now i memtested both sticks and they both got above 8 passes, i have no clue what is actually wrong now.

 

Ok so im now using both the sticks of ram and they only give me this error time to time, this should be the final error if im right

 

Where there any errors when you tested your memory with Memtest 86+.
Any red lines in the test.
Could you make a foto and upload it.

 

I just turned it off after arnd 8hrs of testing for each stick and they had 8-10 passes each with no red lines.

But is it possible that my motherboard does not support the ram according to the manufacturer's website as they did not list out my corsair vengeance LED 3200mhz 16gb white (CMU16GX4M2C3200C16)? i could only find the 3000mhz. If thats the case, can I underclock my ram to match that?

 

According to the Memory list no 3200 mhz modules is supported at all, but i am not a hardware guy to advice you about your question.
My advice would be to go to the tweaktown supportforum of gigabyte and ask your question there see under sticky welcome to gigabyte technical support here GIGABYTE

Or at Corsair here https://corsair.secure.force.com/home/home.jsp

Did you already checked/test your Harddisk and/or SSD because in the last dumpfile i analysed in the stacktext NTFS
was named a few times.

 

When u mean to check the disks does that mean check for errors? Which is i right click both the disks and use the tool for error checking?

 

see this tutorial Drive Error Checking in Windows 10