Various BSOD's just after startup

[LaserChild9]

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]

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.
View attachment 392534
Dump Files - Configure Windows to Create on BSOD

 

[torchwood]

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]

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!

*** 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:

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

Cheers, Boris

 

[axe0]

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

 

[BorisTheAnimal]

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

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

 

[axe0]

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

 

[BorisTheAnimal]

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]

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]

What memory test did you run?

 

[LaserChild9]

I ran memtest86 overnight (15-16 hours). Is this saying there's a memory issue then?

 

[axe0]

I can't say, but the usual situation is invalid memory being referenced which can go from 2 sides (memory and drivers)

I would recommend to run MemTest86+ which is a better test compared to MemTest86 (and the built-in feature)

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

[LaserChild9]

Hi guys, sorry for the delay, ran memtest86 last night, 0 errors:



What next?

 

[axe0]

I would like you to upload a new zip file, just in case there are relevant events, and please check the recovery settings.

Dump Files - Configure Windows to Create on BSOD

 

[LaserChild9]

I have double checked that my system is configured to create dump files and it is, WhoCrashed states:

Crash dumps are enabled but no valid crash dumps have been found. In case you are experiencing system crashes, it may be that crash dumps are prevented from being written out. Check out the following article for possible causes: If crash dumps are not written out.

I have read the article and checked everything there, the system is configured to write dumps, it has a page fil, the page file is large enough, I have over 80Gb space on my drive and the page file is managed by the system.

 

[axe0]

Is there any error displayed about the process of gathering information (or something) failed?

 

[LaserChild9]

Is there any error displayed about the process of gathering information (or something) failed?

Nothing that I was made aware of. Is something missing then?

 

[axe0]

A bit lack of information for me for proper troubleshooting

 

[axe0]

That means, either I'm missing something or I need to gather more information about the process of the BSOD of your system.

 

[LaserChild9]

Ok, so what can I do next to figure this out?