New build, BSoDs... At wits end.

john87 · Feb 5, 2016

I am at my wits end. You guys are my only hope it seems

.

I've wanted a decent gaming system for around 16 years and I finally was able to put one together. The parts are all brand new but when I haven't used my system for hours and turn it on, it blue screen on the Windows loading page. After I restart it, it is fine for the rest of the time I use it and if I turn it off and on within minutes of using it, it is fine. It's cost me a lot of money to build this and it's rattling my nerves every time I use it, I just can't enjoy it until this is fixed.

System:

i5 6600k
Gigabyte B150m-D3H
Corsair 8GB DDR4 Vengeance LPX 2133MHz Memory Kit for Skylake
Gigabyte GTX 970 Twin Turbo OC
1TB TOSHIBA SATA III 7200RPM HDD
120GB Kingston SSDNow V300 Solid State Drive
500W - EVGA 80+ PSU

I have not overclocked and all of my drivers etc seem to be up to date. This was a straight Windows 10 install on to new components.

Here are some .dmp files from recent crashes, I shall attach the newest to a .zip file.
https://drive.google.com/open?id=0B0S97AxQePk-TVlRZUViZzFyLUk
https://drive.google.com/open?id=0B0S97AxQePk-cE8zbE5KNk03SzA
https://drive.google.com/open?id=0B0S97AxQePk-WjlnUlVjc1Y4ajA
https://drive.google.com/open?id=0B0S97AxQePk-Zm44RmZpa01ZSmM

Things I have tried:

- Ran Memory Diagnostic tool, no errors.

- Reinstalled GPU drivers in safe mode.

- Updated BIOS and ran MemTest. 12 passes, 0 errors.

- Checked motherboard pins for damage, none present.

- Removed and re-seated components.

- Reinstalled Windows.

- Ran MalwareBytes, no issues.

I have also been in contact with Aria PC, which is where I purchased my parts. They thought it might have been bent pins on the motherboard but I have checked and sent them a picture and they say it all looks fine. They also asked me to try and use one stick of ram at a time but that didn't reveal the issues.

PLEASE help me!!

jcgriff2 · Feb 6, 2016

Hi. . .

The 5 dumps had 3 different bugchecks (STOP error codes):
(3) 0x7e (0xc0000005,,,) - thread threw an exception; exception error = 0xc5 = memory access violation
(1) 0xc2 (0x7,,,) - current thread attempted to free memory which was already freed
(1) 0xde - driver has corrupted pool memory that is used for holding pages destined for disk

All 5 dumps listed Microsoft drivers as the probable cause, which simply cannot be. They were likely listed as a default or because hardware failure exists.

Usually when we see varying bugchecks, the probable cause of the BSODs is "unknown hardware failure" and very difficult to figure out. The dumps are incapable of telling us which piece of hardware is failing. The purpose of a debugger is to debug software, not hardware. A debugger assumes that the hardware platform is working and stable.

See if Driver Verifier flags any 3rd party drivers - http://www.techsupportforum.com/for...rums/f299/driver-verifier-windows-10-8-1-8-7-and-vista-bsod-related-473665.html

Let Driver Verifier run in the background for 24 hours minimum. It will do checks on 3rd party drivers. If a driver violation is detected, Driver Verifier will force a BSOD immediately.

Regards. . .

jcgriff2

Code:

[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020516-7359-01.dmp][/FONT]
[FONT=lucida console]Built by: 10240.16644.amd64fre.th1.160104-1507[/FONT]
[FONT=lucida console]Debug session time: Thu Feb  4 22:36:03.989 2016 (UTC - 5:00)[/FONT]
[FONT=lucida console]System Uptime: 0 days 4:54:46.637[/FONT]
[FONT=lucida console]Probably caused by : NTFS.sys ( NTFS!FreeContextDataBlock+15 )[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]BUGCHECK_STR:  AV[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  AV_NTFS!FreeContextDataBlock[/FONT]
[FONT=lucida console]Bugcheck code 1000007E[/FONT]
[FONT=lucida console]Arguments ffffffff`c0000005 fffff801`8231639d ffffd000`23e07388 ffffd000`23e06ba0[/FONT]
[FONT=lucida console]BiosVersion = F6e[/FONT]
[FONT=lucida console]BiosReleaseDate = 01/14/2016[/FONT]
[FONT=lucida console]SystemManufacturer = Gigabyte Technology Co., Ltd.[/FONT]
[FONT=lucida console]SystemProductName = To be filled by O.E.M.[/FONT]
[FONT=lucida console]MaxSpeed:     3500[/FONT]
[FONT=lucida console]CurrentSpeed: 3504[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020516-5593-01.dmp][/FONT]
[FONT=lucida console]Built by: 10240.16644.amd64fre.th1.160104-1507[/FONT]
[FONT=lucida console]Debug session time: Fri Feb  5 12:14:32.517 2016 (UTC - 5:00)[/FONT]
[FONT=lucida console]System Uptime: 0 days 6:47:49.165[/FONT]
[FONT=lucida console]Probably caused by : NTFS.sys ( NTFS!NtfsDereferenceQuotaControlBlock+24 )[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]BUGCHECK_STR:  AV[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  AV_NTFS!NtfsDereferenceQuotaControlBlock[/FONT]
[FONT=lucida console]Bugcheck code 1000007E[/FONT]
[FONT=lucida console]Arguments ffffffff`c0000005 fffff801`5a5936f4 ffffd000`21cf8398 ffffd000`21cf7bb0[/FONT]
[FONT=lucida console]BiosVersion = F6e[/FONT]
[FONT=lucida console]BiosReleaseDate = 01/14/2016[/FONT]
[FONT=lucida console]SystemManufacturer = Gigabyte Technology Co., Ltd.[/FONT]
[FONT=lucida console]SystemProductName = To be filled by O.E.M.[/FONT]
[FONT=lucida console]MaxSpeed:     3500[/FONT]
[FONT=lucida console]CurrentSpeed: 3504[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020516-5437-01.dmp][/FONT]
[FONT=lucida console]Built by: 10240.16644.amd64fre.th1.160104-1507[/FONT]
[FONT=lucida console]Debug session time: Fri Feb  5 16:10:08.517 2016 (UTC - 5:00)[/FONT]
[FONT=lucida console]System Uptime: 0 days 3:54:54.164[/FONT]
[FONT=lucida console]Probably caused by : NTFS.sys ( NTFS!NtfsUninitializeNtfsMcb+b6 )[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0xc2_7[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  0xc2_7_NTFS!NtfsUninitializeNtfsMcb[/FONT]
[FONT=lucida console]Bugcheck code 000000C2[/FONT]
[FONT=lucida console]Arguments 00000000`00000007 00000000`00001254 00000000`40000000 ffffc000`c8f58a30[/FONT]
[FONT=lucida console]BiosVersion = F6e[/FONT]
[FONT=lucida console]BiosReleaseDate = 01/14/2016[/FONT]
[FONT=lucida console]SystemManufacturer = Gigabyte Technology Co., Ltd.[/FONT]
[FONT=lucida console]SystemProductName = To be filled by O.E.M.[/FONT]
[FONT=lucida console]MaxSpeed:     3500[/FONT]
[FONT=lucida console]CurrentSpeed: 3504[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020516-5093-01.dmp][/FONT]
[FONT=lucida console]Built by: 10240.16644.amd64fre.th1.160104-1507[/FONT]
[FONT=lucida console]Debug session time: Fri Feb  5 16:52:58.607 2016 (UTC - 5:00)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:00:15.256[/FONT]
[FONT=lucida console]Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+6e )[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]BUGCHECK_STR:  AV[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  AV_nt!RtlDeleteNoSplay[/FONT]
[FONT=lucida console]Bugcheck code 1000007E[/FONT]
[FONT=lucida console]Arguments ffffffff`c0000005 fffff803`6515d69e ffffd000`cdbd7228 ffffd000`cdbd6a40[/FONT]
[FONT=lucida console]BiosVersion = F6e[/FONT]
[FONT=lucida console]BiosReleaseDate = 01/14/2016[/FONT]
[FONT=lucida console]SystemManufacturer = Gigabyte Technology Co., Ltd.[/FONT]
[FONT=lucida console]SystemProductName = To be filled by O.E.M.[/FONT]
[FONT=lucida console]MaxSpeed:     3500[/FONT]
[FONT=lucida console]CurrentSpeed: 3504[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=lucida console]Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020516-10421-01.dmp][/FONT]
[FONT=lucida console]Built by: 10240.16644.amd64fre.th1.160104-1507[/FONT]
[FONT=lucida console]Debug session time: Fri Feb  5 04:46:45.962 2016 (UTC - 5:00)[/FONT]
[FONT=lucida console]System Uptime: 0 days 0:02:08.609[/FONT]
[FONT=lucida console]BugCheck DE, {2, ffffc000572a9a50, ffffc000572a9090, 1772468c0}[/FONT]
[FONT=lucida console]Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+285aa )[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0xDE[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]FAILURE_BUCKET_ID:  0xDE_nt!_??_::FNODOBFM::_string_[/FONT]
[FONT=lucida console]Bugcheck code 000000DE[/FONT]
[FONT=lucida console]Arguments 00000000`00000002 ffffc000`572a9a50 ffffc000`572a9090 00000001`772468c0[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

jcgriff2 · Feb 6, 2016

Also, check Kingston for an SSD firmware upgrade - Download sh100_503fw_win, for sh100s3 | Kingston Technology

SSDs with outdated firmware can absolutely cause BSODs.

For info, 3 of your 5 dumps mentions "NTFS" and/or "ntfs.sys" (Windows file system driver).

Usually/often (not ALWAYS) when "NTFS" is seen in dumps, the hard drive is somehow involved.

Regards. . .

jcgriff2

EDIT:

Also -- run this Intel CPU test - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool-64-bit-

john87 · Feb 6, 2016

Hi there,

I ran the CPU test and everything was fine, it passed. Also, there is no firmware update for my drive, I downloaded the Kingston tool to check.

Next, I will look at running driver verifier for the given time frame.

One thing I do want to note. My RAM is 13-15-15-28 but I noticed in the bio it was running in auto @ 15-15-15-36. As a result, I changed it to what my RAM is manually in hope it helps.

Although first thing today, I received a BSoD again, I have attached the .dmp in a zip.

:banghead:

john87 · Feb 6, 2016

Another blue screen

:banghead:

jcgriff2 · Feb 6, 2016

Hi. . .

The bugchecks on the last 2 dumps -
0x1a - severe memory management error
0x19 (0x3,,,) - bad pool header - [memory] freelist is corrupt

Like with the others, the actual cause is unknown hardware failure - we've added 2 new bugchecks to the mix. Varying bugchecks point to [unknown] hardware failure. Any and all hardware is suspect.

Glad to hear the CPU test passed.

Sorry, but I don't have any idea at this time which piece of hardware is bad. The only possible clue is that the 0x1a dump listed a DirectX component, which may mean that video is involved.

Have you run memtest86+ one stick at a time + alternate the slots?

I am not a hardware expert and don't know much about the RAM timings. I sit squarely on the software side of the fence.

Regards. . .

jcgriff2

`

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020616-5531-01.dmp]
Built by: 10240.16644.amd64fre.th1.160104-1507
Debug session time: Sat Feb  6 11:29:17.792 2016 (UTC - 5:00)
System Uptime: 0 days 2:56:44.440
Probably caused by : dxgmms2.sys ( dxgmms2!VidMmProcessAsyncOperation+155fc )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  0x1a_403_dxgmms2!VidMmProcessAsyncOperation
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`202d1540 88400001`8f0d3867 fffff680`000e0ee0
BiosVersion = F6e
BiosReleaseDate = 01/14/2016
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3504
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020616-5265-01.dmp]
Built by: 10240.16644.amd64fre.th1.160104-1507
Debug session time: Sat Feb  6 08:06:04.081 2016 (UTC - 5:00)
System Uptime: 0 days 11:49:29.729
Probably caused by : Pool_Corruption ( nt!ExFreePool+cb6 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  conhost.exe
FAILURE_BUCKET_ID:  0x19_3_nt!ExFreePool
Bugcheck code 00000019
Arguments 00000000`00000003 ffffc000`a2d30df0 ffffc000`a2d30df0 ffffe000`e92455d0
BiosVersion = F6e
BiosReleaseDate = 01/14/2016
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3504
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

john87 · Feb 8, 2016

Hi there, I had 2 more, do they also point to hardware failure? I researched one of them and read that uninstalling Intel Rapid Storage would help... it didn't

.

jcgriff2 · Feb 9, 2016

Hi. . .

Yes... unfortunately, the probable cause on both dumps list Microsoft drivers, which simply cannot be.

"Unknown hardware failure" is the probable cause.

The dumps are incapable of telling us anything about the exact hardware issue.

Have you thoroughly tested RAM -- one stick at a time; alternate the slots? (memtest86+)

Regards. . .

jcgriff2

`

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020816-5406-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Mon Feb  8 03:02:49.499 2016 (UTC - 5:00)
System Uptime: 0 days 18:05:12.147
Probably caused by : win32kbase.sys ( win32kbase!IsWindowDesktopComposed+12 )
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  0x3B_win32kbase!IsWindowDesktopComposed
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff961`619eb912 ffffd000`23a98b40 00000000`00000000
BiosVersion = F6e
BiosReleaseDate = 01/14/2016
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3504
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020716-5171-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Sun Feb  7 08:31:35.117 2016 (UTC - 5:00)
System Uptime: 0 days 0:28:08.766
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+39 )
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  SearchUI.exe
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID:  AV_nt!MiDemoteCombinedPte
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff801`b519873d ffffd001`bd1b3098 ffffd001`bd1b28b0
BiosVersion = F6e
BiosReleaseDate = 01/14/2016
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3504
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

New build, BSoDs... At wits end.

Attachments

Attachments

Attachments

Attachments

Top Contributors this Month

Recommended Communities