Multiple unrelated(maybe?)crashes,every 1-2 hours

GioXmen · 24 Apr 2016

THIS IS WAS AN OLD ISSUE THAT HAS BEEN SOLVED, PLEASE READ LATEST REPLY TO THIS THREAD! :)

Hello users/moderators/staff of ten forums!,

I am having issues with windows 10 and this time it is with bluescreens.It seems that it may be driver related since two crashes point to a network/Wi-Fi related driver. The problems started happening out of nowhere while I was browsing the internet and since then I have had 3 different blue screens happen.I have saved both the mini dumps and the 1GB dumps(if you need them),but I will post only what the instructions tell me to post for now.I will also add WhoCrashed analysis reports pictures.

Another thing that might be pointing at the possibility of a network driver related driver is that a week ago and up until now every time I download anything my computer starts slowing down,but once the download finishes the problem goes away.

The only major change I have done to my computer is I installed BitDefender Total Security,but it has been running for a week until now with no problems.

P.S To test any solution/fix it may take up to 2 hours since it is not a frequent crash and I have no way of causing it.It happens to me randomly while I am browsing the internet.

P.S 2# I also think it may be my HDD since it is old,but all diagnostic HDD programs tell me I am fine,perhaps I am just looking for reasons to get rid of it and get a new one :P

Here are the errors in text so that google might pick this thread up:
1.
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Error: MEMORY_MANAGEMENT
2.
This was probably caused by the following module: afd.sys (afd!AfdPoll32+0x3F2)
3.
This was probably caused by the following module: athw10x.sys (0xFFFFF80AFA9C66D4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Attachment 76496 Attachment 76498 Attachment 76497

Attachment 76495

*Please excuse me if I make any horrible grammar mistakes :/

Arc · 24 Apr 2016

Hello @GioXmen.

Do the following things.

First: Update the Wireless network driver from Download Qualcomm Atheros wireless driver for AR938X and 64bit Windows 10

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff80afa9c66d4, ffffcc00ff7941a8, ffffcc00ff7939e0}

Probably caused by : athw10x.sys ( athw10x+d66d4 )

Followup:     MachineOwner
---------

Code:

    Image name: athw10x.sys
    Timestamp:        Fri Aug 14 15:33:30 2015 (55CDBCF2)

Second: As the computer is crashing, stop Overclocking. Set all the hardware components like CPU, RAM and Graphics Card to the default clock speed. It is extremely needed.

Code:

CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3503

Third: You have 22 startup items; which is bad computing. Free up the startup. Windows does not need any other program to auto-start with it; but they can conflict which may cause various issues including randm crashes including BSODs.

Right click on the taskbar and click on "Task Manager" in the context menu.
It will open Task Manager with "Processes" tab selected. Click on the "Startup" tab.
Select them all one by one and click "Disable" at the bottom right corner.
Disable everything there other than the antivirus.

See how it goes. Let us know.

If still you experience BSODs even after doing all these three ....
Fourth: Pay attention to the memory.

Code:

BugCheck 1A, {41201, fffff68000058cf8, e2300000529be867, ffffdd04d3801a00}

Probably caused by : memory_corruption ( nt!MiGetPageProtection+32d )

Followup:     MachineOwner
---------

Test your RAM modules for possible errors.

MemTest86+ - Test RAM

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

GioXmen · 24 Apr 2016

Ok thanks for replying and I believe I may have found a possible solution.

The drivers you have me are outdated sadly(I have 10.0.0.338 --> 10.0.0.329) and I updated them from (10.0.0.326 -->10.0.0.338 )

But the second solution reminded me of something - I have recently done a HDD clone and tried to reboot using the clone(failed btw) ,but when I was in the BIOS I noticed I was on neutral mode(I have 3 presets : power saving,neutral,performance) so I turned on performance mode.I will try turning it on neutral again and see what happens then.

If I continue to have problems I will reply back,most likely tomorrow since it is getting late.

P.S The startup items are mostly disabled,so they shouldn't be causing any problems.

GioXmen · 27 Apr 2016

Ok,
So I have had one more crash before bios change and one after and today my computer has got no crashes.I will mark this as solved if it wont crash in the next 5 days.

Attachment 77060

Attachment 77061

Attachment 77062

GioXmen · 30 Apr 2016

No crashes or BSOD, marking as solved for now, if I have problems I will let you know :P

GioXmen · 18 Jul 2016

I AM HAVING NEW ISSUES AFTER INSIDER 14388 UPDATE IN THE SLOW RING!

Hello users/moderators/staff of ten forums!,

I am having new issues with the latest update, I seem to be having bsod's every hour or so after boot while watching youtube or just regular use (even sitting at the desktop. I am familiar with having driver issues, so I ran driver verifier, after that my system would not boot and driver verifier blue screen showed that it was avc3.sys at fault( which is BitDefender).

I then turned off driver verifier and now it still wouldn't boot,but I got irql_not_less_or_equal BSOD'S every time I boot, so uninstalled BitDefender it in safe mode and disabled driver verifier in it too, now I can boot back into the system, but the same bsod's still happen.

I believe it may be problems with drivers again, or perhaps even faulty RAM modules( BSOD analysis seems to only point to RAM and drivers as the issue)

On Mon 2016-07-18 11:39:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071816-33187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x41792, 0xFFFFF60000080040, 0x8, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 2016-07-18 10:21:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071816-31781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFDB73640, 0x8, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 2016-07-17 21:05:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071816-60906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x41793, 0xFFFFD3000013DFC8, 0x128, 0x127)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 2016-07-17 20:04:28 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071716-33875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x41793, 0xFFFFAB800014A040, 0x9, 0x8)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 2016-07-17 19:32:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071716-35703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x139 (0x3, 0xFFFF89808ADBB530, 0xFFFF89808ADBB488, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 2016-07-17 18:59:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071716-28375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x41792, 0xFFFFFCBFFE5D3440, 0x8, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 2016-07-17 17:47:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071716-29531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x914, 0xCA89DD0, 0xFFFFE0008EF55000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 2016-07-17 17:00:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071716-43515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xBE (0xFFFFFC00003FFF00, 0x4500000CF721025, 0xFFFFDF81BE8B4650, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Here is the full dm log as instructed in posting instructions.

Attachment 90680

GioXmen · 18 Jul 2016

Oh and one thing that has been happening lately is my Firefox tabs tend to crash a lot, and sometimes Firefox itself crashes, I am using the developer edition. Firefox before the update was really reliable and now it crashes a lot.

Arc · 18 Jul 2016

You are having memory errors there.

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800ffcf7141-fffff800ffcf7142  2 bytes - nt!MiResolvePrivateZeroFault+211
    [ 80 f6:00 d3 ]
    fffff800ffcf716a-fffff800ffcf716c  3 bytes - nt!MiResolvePrivateZeroFault+23a (+0x29)
    [ 40 fb f6:80 69 d3 ]
    fffff800ffcf7188-fffff800ffcf7189  2 bytes - nt!MiResolvePrivateZeroFault+258 (+0x1e)
    [ 80 fa:00 ec ]
    fffff800ffd911dd-fffff800ffd911de  2 bytes - nt!MiPurgeZeroList+6d (+0x9a055)
    [ 80 fa:00 ec ]
9 errors : !nt (fffff800ffcf7141-fffff800ffd911de)

Without of any specific module/driver failure.

Do three things, one by one.

► First, as the issue is occurring during boot, Perform a clean boot and disable startup items other than the Antivirus and the third party services. Clean Boot - Perform in Windows 10 to Troubleshoot Software Conflicts - Windows 10 Forums
See how it goes.

► If the issue persists, make it sure that the RAM is not failing actually. Test your RAM modules for possible errors.

MemTest86+ - Test RAM

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

► If RAM is free from errors, please assume that some system corruption has taken place during the upgrade. A repair install will take care of those. Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums

See how it goes. Let us know.
___________________________________________________________________________________________________

Code:

BugCheck 1A, {41792, fffff60000080040, 8, 0}

Probably caused by : memory_corruption

Followup:     memory_corruption
---------

GioXmen · 18 Jul 2016

Ok, once I find anything I will report back!

GioXmen · 18 Jul 2016

It seems that the crashes have stopped during clean boot, I will try to find the driver that is causing this :) Though I have a lot of them ...

Multiple unrelated(maybe?)crashes,every 1-2 hours

Computer BSOD with MEMORY_MANAGMENT after insider update!