[SOLVED] [Win10 x64] Random BSOD over a long time now

M

Mikedabike

Well-known member
Hi thanks for being here to help :)

Win 10 64 bit retail version
installed on new computer, no previous installs.
Just over 1 year old

CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
NVIDIA GeForce GTX 970
16gb ddr4 ram
MB Fatal1ty Z170 Gaming K4
PSU cooler master G750M
NO OVERCLOCK on anything
Desktop made up by a shop not a stock/brand machine

Crashes have only happened during gaming, and can be several weeks as long as 2 months between crashes or it can crash several times in a day.
I ran memtest for 15 hours with no fails a few weeks ago after a few crashes.
I updated bios this week as there were about 7 updates available.
1 crash today since the bios update.
This issue has been off and on for almost the entire life of the comp, and i really would like to get help to fix it. I am not very comp savy so guides will be needed in idiot proof lingo :)
In the past i found re seating the ram seemed to cure the crashes for a reasonably amount of time, the last few crashes this month and one in Feb, did not stop after re seating the ram, they did stop for 5 days after bios update though.
I have included the last 5 mini dmp files in a zip aswell just incase needed.
I would be eternal grateful and very very happy if you can aid me in not having this BSOD hanging over my head every gaming moment.
Many thanks for your time, mike.
 

Attachments

  • SysnativeFileCollectionApp.zip
    3 MB · Views: 16
  • perfmon.rar
    95 KB · Views: 2
  • Dump files.rar
    304.4 KB · Views: 15
Re: Random BSOD over a long time now

Hi Mikedabike. :welcome:


Did you install any special software for onedrive from Microsoft?

You can try to:
  1. remove gigabyte ocguru completely (wait some hours/days and see if that worked)
  2. run a full offline antivirus scan (for example, using Kaspersky rescue disk)
  3. remove peerblock completely (wait some hours/days and see if that worked)
  4. install the new audio drivers by realtek for windows x64 - R2.81 - 2017/1/13 (click). (wait some hours/days and see if that worked)
 
Re: Random BSOD over a long time now

Thanks for your prompt reply. As far as i know i have not installed any special software for one drive, unless it came in updates. I have just installed the new audio drivers as that seems like a good thing to do anyway, although the date of the release is well after many previous Bsod. Is there any more info you could share as to why removing your suggested programs may help? Gigabyte ocguru is the only one that has been on the computer the entire period of time spanning the bsod and does run in background on boot up, peerblock was a more recent addition, and does not run unless started by myself during bittorent sessions, never crashed at those times, it is only during gaming.
I will try the gigabyte removal first as time span would suggest that over peerblock.
 
Re: Random BSOD over a long time now

To speed up any process of help, if i do crash again do you need a fresh copy of syns and perf? Would a fresh copy show anything useful with the first program removed?
 
Re: Random BSOD over a long time now

I do have one drive installed on my comp, is that standard or not? Although i have never ran it.
 
Re: Random BSOD over a long time now

Here's what I see - assessment at the end:
Code: 
// 020817-5437-01.dmp
2: kd> .bugcheck
Bugcheck code 0000000A
Arguments 00000000`00000020 00000000`000000ff 00000000`00000000 fffff802`33b4be04

2: kd> kn
 # Child-SP          RetAddr           Call Site
00 ffffda01`dfc87498 fffff802`33bd4829 nt!KeBugCheckEx
01 ffffda01`dfc874a0 fffff802`33bd2e07 nt!KiBugCheckDispatch+0x69
02 ffffda01`dfc875e0 fffff802`33b4be04 nt!KiPageFault+0x247
03 ffffda01`dfc87770 ffff9f04`cbdff420 nt!PpmUpdatePerformanceFeedback+0x84
04 ffffda01`dfc87800 00000000`00000046 0xffff9f04`cbdff420
05 ffffda01`dfc87808 fffff802`33b4b7cb 0x46
06 ffffda01`dfc87810 fffff802`33b4b13a nt!PpmIdleExecuteTransition+0x4db
07 ffffda01`dfc87a80 fffff802`33bcc74c nt!PoIdle+0x33a
08 ffffda01`dfc87be0 00000000`00000000 nt!KiIdleLoop+0x2c

2: kd> ub fffff802`33b4b7cb
nt!PpmIdleExecuteTransition+0x4b9:
fffff802`33b4b7a9 4c858668620000  test    qword ptr [rsi+6268h],r8
fffff802`33b4b7b0 0f85442b0d00    jne     nt! ?? ::FNODOBFM::`string'+0x4576a (fffff802`33c1e2fa)
fffff802`33b4b7b6 41b101          mov     r9b,1
fffff802`33b4b7b9 4c89742420      mov     qword ptr [rsp+20h],r14
fffff802`33b4b7be 4533c0          xor     r8d,r8d
fffff802`33b4b7c1 33d2            xor     edx,edx
fffff802`33b4b7c3 488bce          mov     rcx,rsi
fffff802`33b4b7c6 e8b5050000      call    nt!PpmUpdatePerformanceFeedback (fffff802`33b4bd80)


2: kd> ub fffff802`33b4be04
nt!PpmUpdatePerformanceFeedback+0x66:
fffff802`33b4bde6 0f84ca010000    je      nt!PpmUpdatePerformanceFeedback+0x236 (fffff802`33b4bfb6)
fffff802`33b4bdec 4532c9          xor     r9b,r9b
fffff802`33b4bdef 488d4b18        lea     rcx,[rbx+18h]
fffff802`33b4bdf3 41ba02000000    mov     r10d,2
fffff802`33b4bdf9 418bc7          mov     eax,r15d
fffff802`33b4bdfc 488b11          mov     rdx,qword ptr [rcx]
fffff802`33b4bdff 4885d2          test    rdx,rdx
fffff802`33b4be02 7424            je      nt!PpmUpdatePerformanceFeedback+0xa8 (fffff802`33b4be28)

2: kd> ln fffff80233b4be04
(fffff802`33b4bd80)   nt!PpmUpdatePerformanceFeedback+0x84   |  (fffff802`33b4c070)   nt!PpmIdlePrepare
// 020817-5437-01.dmp
Processor is attempting to enter Idle, and fails on the check due to being above dispatch IRQL - something has crapped in the sandbox here, but it's really hard to say what...


Code: 
// 031917-6031-01.dmp
2: kd> .bugcheck
Bugcheck code 00000124    <-- Uh oh... hardware error reported by the CPU!!!!
Arguments 00000000`00000000 ffffac08`65ec2028 00000000`bf800000 00000000`00000124

2: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 2  6,94,3 GenuineIntel 4008 0000004900000000                   3d1b3fff
                      Cached Update Signature 0000004900000000
                     Initial Update Signature 0000004900000000

2: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 4008
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 94 Stepping 3
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 4900000000

// Error record indicates it came from Proc 2:
Proc. Info 0  @ ffffac0865ec2240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffac0865ec2138
Section       @ ffffac0865ec22c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 2 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x000000046a0cb4c0
  Misc.       : 0x0000000000000086
// 031917-6031-01.dmp
The CPU does not appear overclocked (that i7 is a 4.0GHz part), and yet your CPU threw a L0 cache error. Not good.


Code: 
// 031917-6031-011.dmp
3: kd> .bugcheck
Bugcheck code 0000003D    <-- Uh oh - 3Ds are incredibly uncommon, and are usually tracked back to memory corruption...
Arguments ffffe400`8ad5c508 ffffe400`8ad5bd30 00000000`00000000 00000000`00000000

3: kd> dc ffffe400`8ad5c508 L1
ffffe400`8ad5c508  c000001d                             ....

3: kd> !error c000001d
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

3: kd> lmvm dxgmms2
Browse full module list
start             end                 module name
fffff808`c1e60000 fffff808`c1f07000   dxgmms2    (pdb symbols)          C:\ProgramData\dbg\sym\dxgmms2.pdb\1147EA8FF979406CA49BD69536A6A5531\dxgmms2.pdb
    Loaded symbol image file: dxgmms2.sys
    Mapped memory image file: C:\ProgramData\dbg\sym\dxgmms2.sys\58BA5E7Ea7000\dxgmms2.sys
    Image path: dxgmms2.sys
    Image name: dxgmms2.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar  3 22:28:14 2017 (58BA5E7E)
    CheckSum:         000A6365
    ImageSize:        000A7000
    File version:     10.0.14393.953
    Product version:  10.0.14393.953
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms2.sys
    OriginalFilename: dxgmms2.sys
    ProductVersion:   10.0.14393.953
    FileVersion:      10.0.14393.953 (rs1_release_inmarket.170303-1614)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
// 031917-6031-011.dmp
This one is interesting - it would appear to be a video subsystem error, but so far it's the only one pointing to anything in the display stack at all. Although, assuming that's on PCIE lanes to the CPU, it could still be a failure of the CPU...


Code: 
// 031917-6218-01.dmp
2: kd> .bugcheck
Bugcheck code 00000124   <-- Another hardware error...
Arguments 00000000`00000000 ffffde05`240e3028 00000000`be000000 00000000`00200135

Proc. Info 0  @ ffffde05240e3240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffde05240e3138
Section       @ ffffde05240e32c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 2 Bank 3)
  Status      : 0xbe00000000200135
  Address     : 0x0000000002254ce0
  Misc.       : 0x0000000000122285
// 031917-6218-01.dmp
Proc 2 again throwing the error in L1 cache this time...


Code: 
// 032317-4281-01.dmp
3: kd> .bugcheck
Bugcheck code 000000F7   <-- Driver loaded in kernel failed a security check (usually buffer overrun here)
Arguments 00000000`00000000 000008c1`7c079ace fffff73e`83f86531 00000000`00000000

3: kd> kn
 # Child-SP          RetAddr           Call Site
00 ffffc301`282be7c8 fffff800`233bbd51 nt!KeBugCheckEx
01 ffffc301`282be7d0 fffff800`2323174b nt!_report_gsfailure+0x25
02 ffffc301`282be810 fffff800`23230c2a nt!PpmIdleExecuteTransition+0x96b
03 ffffc301`282bea80 fffff800`2335f81c nt!PoIdle+0x33a
04 ffffc301`282bebe0 00000000`00000000 nt!KiIdleLoop+0x2c
// 032317-4281-01.dmp
Again, the CPU is attempting to enter Idle and fails, similar to the first bugcheck in this list. That's.... bad.


Given everything here, I would remove any overclocking utilities or drivers you have installed (as these are the only software packages I've ever seen cause this), and make certain your system firmware (BIOS/UEFI) and drivers are up to date (especially for your graphics card). If possible, set your BIOS/UEFI to some sort of "safe default" option, and then try to make it happen again. If the problem continues, I would conclude that one of the cores on your CPU is causing errors - you could try undervolting and downclocking, or try to get it analyzed and repaired by the motherboard OEM or Intel support at that point.
 
Last edited:
Re: Random BSOD over a long time now

cluberti said:
Here's what I see - assessment at the end:



Given everything here, I would remove any overclocking utilities or drivers you have installed (as these are the only software packages I've ever seen cause this), and make certain your system firmware (BIOS/UEFI) and drivers are up to date (especially for your graphics card). If possible, set your BIOS/UEFI to some sort of "safe default" option, and then try to make it happen again. If the problem continues, I would conclude that one of the cores on your CPU is causing errors - you could try undervolting and downclocking, or try to get it analyzed and repaired by the motherboard OEM or Intel support at that point.
Click to expand...

Thanks for taking the time to look for me, i have removed the gigabyte ocguru program as recommended earlier, that's the only overclocking prog that came already loaded on the comp since new. I have never tried overclocking anything on this comp. Bios is fully updated. Graphics driver was up to date at time of posting and is updated often as new releases are available within a week or 2 of their release.
Is it possible for software to be causing this issue then? I have been bsod free since removing the 2 programs listed in first response, but then i have gone several months free in the past. If cpu failure was the cause, would i not expect it to be more often? and get more frequent as time went by?? I am a user not a tech, i really have no idea, nor really want to if honest, but living along the Thai/Burmese border, tech are in a short supply here. Much appreciate your help.
 
Re: Random BSOD over a long time now

It's possible if it's an OC utility, as I and others have seen that sort of behavior in the past. However, you'll have to be vigilant and pay attention to see if the errors return within the next 4-6 weeks.
 
Re: Random BSOD over a long time now

Just had 2 bsod in a row, last one was not even in gmae, i was trying to add this post when the 2nd one occured, this is the first time i have had a crash outside of gaming
 

Attachments

  • perf report.rar
    95.3 KB · Views: 1
  • SysnativeFileCollectionApp.zip
    3 MB · Views: 1
  • 040217-4406-02.rar
    45.4 KB · Views: 4
  • 040217-4406-01.rar
    46.8 KB · Views: 4
Re: Random BSOD over a long time now

I saw the new dumps but I can't "extract" anything relevant from them.
I hope we'll see experts here.

By the way, I saw "axtudrv.sys" (sysnative driver reference table says "Most likely part of the AsRock Extreme Tuner").
I can't see that program in msinfo32, but I can see fatal1ty utility\f-stream tuning: maybe you can try to uninstall also that one.

If that still won't help, try to remove AVG (you can always reinstall it later, is this correct?) and use ms defender only as antivirus.
 
Re: Random BSOD over a long time now

Thanks for your time truely appreciated :) The F-stream tuning i can remove and try, would also like to hear from any other experts too who may have further info to help track this really anoying bsod cause down.
Thanks again
 
Re: Random BSOD over a long time now

Just had 3 more crashes in a row after starting computer, attached are the BSOD dumps, do you need another perf and stuff doing this quick before another crash maybe? crashed another time loading it all please help
 

Attachments

  • BSOD.rar
    166.6 KB · Views: 4
  • 041017-4312-01.rar
    49.4 KB · Views: 3
  • SysnativeFileCollectionApp.zip
    3 MB · Views: 4
  • reprt.rar
    95.7 KB · Views: 1
Did you try an offline antivirus scan (with Kaspersky rescue disk or another similar tool: for example, avg rescue cd also exists)?
Have you seated your memory sticks in the red slots? If yes, try the black slots.
Try to replace your path (Control Panel\System and Security\System, advanced system settings, environment variables, system variables, path) with this:
c:\windows;C:\WINDOWS\system32;c:\windows\system32\wbem;c:\windows\system32\windowspowershell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
Click to expand...
I'm not sure you should have intel paths in your Env.Var. Path... Maybe you could try to install (or reinstall) Intel Management Engine driver ver:11.6.0.1126 from your motherboard manufacturer website (click).
Try also to uninstall Malwarebytes and AVG, use/enable MS defender: if the BSODs disappear after these actions, try to reinstall AVG and see if BSODs start to reappear again.

The new dumps show (I tried to show only relevant things...):
Read More:
The first suggests (to my imagination... I'm not a BSOD expert) that something bad happened with NetworkManager (i.e. something malicious in your connection)?
The second suggests there could be problems with the cpu (GenuineIntel_PROCESSOR_CACHE).

I'm not sure if I ever tried to stress test the CPU, but I read something about Prime95 (on mersenne.org)
And I have now found there's an Intel Processor Diagnostic Tool (current version 4.0.0.29), but it seems your CPU isn't supported by it.
 
Last edited:
Ok thanks again, I have just completed an offline scan with Kaspersky rescue disk, 2 hrs or there abouts with all devices and boxes ticked. Results clean. Memory i have reseated and previously i did swap to black, and then again back to orange, crashes happened in both cases. This has been going on for about 1 year now. After the crashes i posted yesterday i removed AVG as you requested. Since then no crashes but this seems to be the way throughout this problem. It crashes a few times and then just stops and runs fine for a few days a week etc. then crashes a few times again... repeat. I am not very comp savy, replacing path seems scary to me as i do not really know what i am doing, the path you show is a little different to what i think is the location so do not want to blindly stab in the dark with my limited abilities. I ran the Intel Management Engine driver ver:11.6.0.1126 in repair mode.
MS defender is now running, and not really sure why you suggest removing malwarebytes? i Quite like it??

As you claim to not be a BSOD expert, is it poss to drag someone into this who is? I mean no disrespect here at all and i totally appreciate your help to date, just wondering if someone with their skill set in the bsod area may be of help here?

I will see if AVG and intel manager do anything, and await the next crash with sinking heart.

Thanks for your help to date
Mike.
 
Mikedabike said:
replacing path seems scary to me as i do not really know what i am doing, the path you show is a little different to what i think is the location so do not want to blindly stab in the dark with my limited abilities.
...not really sure why you suggest removing malwarebytes? i Quite like it??
As you claim to not be a BSOD expert, is it poss to drag someone into this who is?
Click to expand...
This is your original path:
Read More:
How you can see, I just removed the doublets.
The last entry is in another variable (user path, instead of system path).

Malwarebytes (like many other antiviruses) can sometimes cause bsods (especially if it's the paid version), that's why I'd try to see how things go without it (and without AVG)... Even though nothing relevant about it seems to appear in your minidumps.

For the BSOD experts: I can not drag them here. ;-)
I'll try to leave a message for them, by the way.

Post scriptum:
I've re-read cluberti's post and he already said your CPU could be the problem.
Maybe you should really do some CPU tests.
 
Last edited:
xilolee said:
Post scriptum:
I've re-read cluberti's post and he already said your CPU could be the problem.
Maybe you should really do some CPU tests.
Click to expand...

Yes, i am not ignoring that info, just hoping it is still a software issue over an expense of a new CPU 1 year old, that route is getting closer, with more reports pinning it down to that can only help right? As i mentiond, 3 shops with tech support in this town did not even know what a .dmp was, so handing it into a shop for trouble shooting is my last resort. I would have gone that road already if i had a trustworthy source.

I am happy with the copy paste path route you supplied now, that you mentioned in previouse posts and i will replace that if crashes again since AVG is uninstalled since last crash, trying one thing at a time to check it all.
One thought, could dirty power be a cause of this particular problem? My power source is mostly ok but it does have occasional flickering lights or brown outs?? Been trying to source a decent sized UPS but got to order in and they are very expensive here as there is a 300% import tax on luxury goods. Trying to source a local made one that is worth the cash.
Again thanks for your time, it truely is appreciated.
Mike
 
Re: Random BSOD over a long time now

Mikedabike said:
Just had 3 more crashes in a row after starting computer, attached are the BSOD dumps, do you need another perf and stuff doing this quick before another crash maybe? crashed another time loading it all please help
Click to expand...

There are no dump files in the SysnativeFileCollectionApp.zip attachment. Do you have dump files in c:\windows\minidump?

From the 3 dumps in the BSOD.rar attachment (The 041017-4312-01.rar attachment is corrupted):

Bugchecks:
- 0xa - driver attempted to improperly access memory. The NT kernel listed as probable cause. This is simply a default. Actual cause unknown.
- 0x124 - Machine Check Exception - unknown hardware failure
- 0xf7 - driver has overrun a stack-based buffer

I have little doubt that we're dealing with unknown hardware failure, especially in light of the 0x124 BSOD.

0x124 BSODs are notoriously difficult to solve because the cause is simply "unknown hardware failure".

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

All I can really do here is to give you some hardware diagnostic programs to run.

The problem may also be with other hardware parts such as the motherboard or PSU for which there are no software tests.

Regards. . .

jcgriff2
 
Many thanks for your input, much obliged. Will get to testing stuff, i did do a 15 hour pass with memtest before with no faults. Prime 95 and furmark i already had downloaded, i am a little concerned abouty using prime 95 as my location is in tropics and summer so stress testing gets extra hot as air temps are 40 degrees up, what is considered a danger temp i should stop at? Whilst heavy gaming my cpu max temp i have seen recently was 76 degrees the one time i used Prime 95 i saw it go to 97 and shut it off at that point. Is it safe to let it run itself at those temps?? I have had no heat issues while heavy gaming for hours, but stressing is way above that.. advise please?

SeaTools for DOS - Hard Drive (HDD) Diagnostics is there a way to bur this for usb use as i have no optical drive fitted?
 
jcgriff2 said:
There are no dump files in the SysnativeFileCollectionApp.zip attachment. Do you have dump files in c:\windows\minidump?
Click to expand...

I do not have that folder in that location. I made my mini dump path to my desktop, would that be why i don't have any dump files in the SysnativeFileCollectionApp? If so do i need to make a folder in the location you asked about... c:\windows\minidump ?
 
Last edited by a moderator:
Mikedabike said:
Many thanks for your input, much obliged. Will get to testing stuff, i did do a 15 hour pass with memtest before with no faults. Prime 95 and furmark i already had downloaded, i am a little concerned abouty using prime 95 as my location is in tropics and summer so stress testing gets extra hot as air temps are 40 degrees up, what is considered a danger temp i should stop at? Whilst heavy gaming my cpu max temp i have seen recently was 76 degrees the one time i used Prime 95 i saw it go to 97 and shut it off at that point. Is it safe to let it run itself at those temps?? I have had no heat issues while heavy gaming for hours, but stressing is way above that.. advise please?
Click to expand...

Yes, 97 C is way too high. You should be staying below 80 C ideally.
T_junction Max is the maximum temperature the cores can reach before thermal throttling is activated. Thermal throttling happens when the processor exceeds the maximum temperature. The processor shuts itself off in order to prevent permanent damage. T_junction Max (T_j Max) is also referred to as TCC Activation Temperature in certain processor datasheets.
Click to expand...

T_j is 80 C, which is what I base my 80 C guideline on. T_j Max is 100 C from page 93 of Datasheet, Vol. 1 : 6th Generation Intel® Core™ Processor Family Datasheet, Vol. 1

Mikedabike said:
SeaTools for DOS - Hard Drive (HDD) Diagnostics is there a way to bur this for usb use as i have no optical drive fitted?
Click to expand...

You can probably put it on a USB using Rufus:
SeaTools | Seagate -> click on the ISO SeaTools for DOS
Rufus

Mikedabike said:
There are no dump files in the SysnativeFileCollectionApp.zip attachment. Do you have dump files in c:\windows\minidump?

I do not have that folder in that location. I made my mini dump path to my desktop, would that be why i don't have any dump files in the SysnativeFileCollectionApp? If so do i need to make a folder in the location you asked about... c:\windows\minidump ?
Click to expand...
If you have the minidumps on your desktop, you could zip them up and upload them here.
 
Back
Top