Various BSOD's just after startup

LaserChild9 · 07 Oct 2016

Hi all,

So I started getting BSOD's about a month ago, starting with Bad_Pool_Caller. I installed WhoCrashed which confirmed what I suspected, the crashes were caused by a ramdisk driver that my motherboard had recently installed. I uninstalled this software and the BSOD's stopped, for a few days at least. I have started getting Page Fault BSOD's regularly now and they only ever happen just after startup and only once, never during extended use. When I try to check what is causing them with WhoCrashed I get a message saying that crash dumps are enabled but no valid crash dumps are on my computer.

I have been trying to solve this with the folks over @ Toms Hardware but they recommended that I come here so I will detail what I have already done with them to save some time:

I have checked that the Page file system is setup correctly.
I have tried running driver verifier, but still no Mini-dump files.
I have run memtest (no errors)
I have run chkdsk after which I had a few days with no BSOD's but when I did have one a mini dump was written, though no mini dump files have been written since.

The Errors that I am getting are BAD_POOL_CALLER and Page Fault in Non Paged Area.

**axe0** · 08 Oct 2016

Hi LaserChild9,

Welcome to the 7forums :)

Is there any driver mentioned in the BSOD screen?

Does the BSOD process go properly? Is below in the screen no error displayed about something that went wrong?
Please make a photo of the BSOD screen and post the photo, to ensure that you will have enough time I would recommend to disable the auto restart option in the recovery options.
Attachment 392534
Dump Files - Configure Windows to Create on BSOD

torchwood · 08 Oct 2016

Hi LaserChild9,

Are you overclocking?
I see alot of services included that point towards this

As a side point you appear to have a problem with
Peer Networking connections in regard to your user profile

@Axe0
DxDiag Previously: Crashed in system information (stage 4) & Direct3D (stage 3) & DirectSound (stage 3) & DirectInput (stage 1) & DirectShow (stage 1). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information

Roy

BorisTheAnimal · 08 Oct 2016

I can't comprehend how the both of you missed the dump file.

Anyway hello LaserChild9.

The BSOD was caused by amifldrv64.sys which is the driver for the MSI Live Updater, I would recommend that you uninstall through the control panel!

Code:

*** WARNING: Unable to verify timestamp for amifldrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for amifldrv64.sys
Probably caused by : amifldrv64.sys ( amifldrv64+1a04 )

And torchwood he ain't overclocking:

Code:

2: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500

Cheers, Boris :)

**axe0** · 09 Oct 2016

@Boris, that dump is an old one...

BorisTheAnimal · 09 Oct 2016

axe0 said:

@Boris, that dump is an old one...

It says 092716, if that's not shortened for 27th of September 2016, then what?

**axe0** · 09 Oct 2016

That is, but I personally don't find it worthy to check on dumps that are about 2 weeks or more old.

BorisTheAnimal · 09 Oct 2016

axe0 said:

That is, but I personally don't find it worthy to check on dumps that are about 2 weeks or more old.

Well the service was still running so I just thought that it would mean troubles for him.

LaserChild9 · 18 Oct 2016

Hi all, sorry for the dely, the PC has been behaving for the most part, so another BSOD today, again no dump filebut I did get a pic of it as requested:

Hope this is useful.

**axe0** · 18 Oct 2016

What memory test did you run?