Windows 10: Multiple BSODS with different errors, caused by ntoskrnl.exe

I've always had issues with BSOD's with this computer however the last 6 months or so I have had no issues.

I had a single crash 4 days ago, and then nothing until today in which I have had 3 crashes and a freeze. The erros are either Page fault in nonpaged area, memory management or system service exception. After the first 2 BDOS's and the freeze ( all within an hour or so) I thought temperatures might be an issue (which has been an issue before), so I gave my PC a good clean out and it was fine for 8 hours or so. It is worth noting these BSOD's usually happen when the PC is not under much stress, and the PC usually works fine when playing games ETC, leading me to doubt heat as an issue.

I have updated all the drivers I can think of, and now I am lost as for what to do. I believe the next step is to test my RAM?

If you need any logs or dumps provided let me know and I will do so ASAP.

So what should I do?

Thanks

EDIT: the log collector zip file is attached in a reply

:)

 

Multiple BSODs with differen't errors

The computer has crashed a few more times today without error logs or minidumps. On one occasion I got a partially printed blue screen and a minidump. It has been attached below.

New DMP1407

Thanks,

Lewis

 

Multiple BSODs with differen't errors

@ZigZag

Log Name: System

Source: Microsoft-Windows-WER-SystemErrorReporting

Date: 11/07/2016 13:26:42

Event ID: 1001

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-THMDJ0V

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe0017d9e28f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\071116-6296-01.dmp. Report Id: 491f6cdb-5e60-4b75-928b-532baa88009e.

 

Follow the direction in the Attention box at the top of this thread and of the forum:

Attachment 121335

 

My bad, have attached them now *Smile

 

I'm not seeing anything useful in the dumps unfortunately. I do see some really old drivers in drivers.txt though:

2006/09/05 08:10:02 \??\C:\Windows\GVTDrv64.sys
Driver Description: Gigabyte Easy Tune 6 driver (known BSOD issues w/Win7)
Driver Update Site: http://www.gigabyte.us/support-downl...lity.aspx?cg=2

2009/03/13 03:22:29 \??\C:\Windows\gdrv.sys
Driver Description: Gigabyte Easy Saver - mobo power utility driver
Driver Update Site: 主機板 - GIGABYTE - Motherboard , Graphics Card , Laptop ,Tablet , Mini-PC , Server , PC Peripherals and more

2009/03/20 02:59:06 \??\C:\Windows\etdrv.sys
Driver Description: Generic Port I/O
May be part of Gigabyte Tools Easy Tune 6 (incompatible with Win7)

2009/11/18 17:39:04 C:\WINDOWS\system32\drivers\jnprvamgr.sys
Driver Description: Juniper Network Agent Virtual Adapter Manager driver
Driver Update Site: Download Software - Support - Juniper Networks

2010/02/18 15:17:53 C:\WINDOWS\system32\drivers\amdiox64.sys
Driver Description: AMD IO Driver
Driver Update Site: Uncertain if currently used/needed, if so: Support & Drivers
If not, rename to amdiox64.BAK and see if that fixes the problem.

2012/05/03 20:56:17 C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys
Driver Description: CD-ROM Class Filter Driver by Gear Software. Also comes with iTunes
Driver Update Site: GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering

Update or remove the software they belong to if you can. See if that helps.

Definitely need to test your RAM:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

If none of this helps then we can try Driver Verifier:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.
===================================================4

 

Ok, so I was running memtest last night and got 5 passes without fail, I had to stop it this morning to use the PC, but will run for the full 8 passes tonight.

I am in the process of updating those drivers, and I will get back to you on next crash / once memtest runs for 8 passes *Smile

Thanks for the help, its really appreciated <3

 

Ok I have now updated Easy Tune 6.
I couldn't find an update for Easy saver with my motherboard and windows 10 64 bit, I also could not find anyway to remove it. Any ideas?
I removed Juniper.
I renamed the AMD IO driver.
I have updated iTunes (and hopefully the GEAR driver).

I will get back to you when/if it crashes again *Smile

 

The pc just froze randomly about 10 mins after starting to use it, any ideas on what I should do now?

 

And after I turned it on it BSOD'd again with error UNEXPECTED_KERNEL_MODE_TRAP with no dump file created

 

Did you run memtest86+ for 8 passes yet. If so and no problem then try Driver Verifier as I described.

 

So I dug deeper and found those drivers were not properly installed/updated/removed so I fixed that. Since memtest passed with flying colors, I ran driver verifier for a day and a half but it did not crash. I am now going to wait until next crash (if there is one) and then turn it back on, however I think the issue is fixed. Thanks so much for the help <3

 

You're welcome. Hope the problem is resolved.

 

Ok so my computer randomly shutdown (like cable pulled shutdown), turned itself back on and as soon as it got to the windows log in screen it BSOD'd. I have attached the log collector thing, should I turn verifier back on?

 

No new dumps unfortunately.

I see this in the evnet viewer log:
Code: Event[11488]: Log Name: System Source: volmgr Date: 2017-02-22T10:58:44.179 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: EthanHome-PC Description: Crash dump initialization failed![/quote] Have you changed or disabled the pagefile in Windows 10? That would cause this as crash dump needs a pagefile at least the size of your RAM. The best way for this to be set is to let the system manage it, don't try to control the size.