BSOD using FreemakeVideoConverter Page_Fault_ other frequent BSOD

[jeanpierregeorg]

Today Page_Fault_in_Nonpaged_Area when using Freemakevideoconverter
7 minutes later no BSOD but no response for the same file conversion
For the last 3 months several BSOD with irql_not_less_or_equal
or system_service_exception 0X0000003B
once Bad_Pool_Header 0X00000019

 

[essenbe]

Hello jeanpierregeorg, welcome to Seven Forums, I will attempt to assist you if I can. I have looked at your files you submitted, but there were no dump files in them. If you would, please re run the BSOD Posting Instructions, just to make sure. Please use option 2 this time and click the 'Grab All' button and give it time to do it's file collection then upload it with your next post. (http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html) The dump files are what we use to debug a system and it is quite difficult without them. I may also suggest you make sure your computer is configured for Small Memory Dumps. (http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html) Please check in C:/Windows and make sure there is a folder there named Minidump. If there is not one there, please create one.

Also, just for your information, if you make a new post in this thread, I will be notified of the new post. If you edit an older post to add information, I will not be notified. I only tell you this so you will make a new post to add information that will help me assist you. You mention that you have the problems when using Freemake. Is that the only program that causes you problems? If there are other programs or activities that cause you problems, please let me know. If there are other thing that may aid me in figuring out your problem, please advise me.

 

[essenbe]

jeanpierregeorg, in looking at some of the documents that were submitted, I did notice quite a few errors in GoPro Importer.EXE. Am I correct that it is a camera program to import digital images from the camera to your computer? I would assume that it would be used in conjunction with Freemake Video Converter. Am I correct in that assumption? If I am, I would first suggest that you see if there is an updated GoPro program or drivers and do the same for Freemake.

 

[jeanpierregeorg]

BSOD other occurences idle for example

Essenbe thank you very much for looking at my problem.
For the moment I have no minidump file and just configured yesterday to get them in C:\windows\minidump
I shall upload them as soon as I get one.
GoPro software : in fact I downloaded it recently and never used it (I have no Gopro at the moment).
THe BSOD with FreemakeVideoConverter happened yesterday while transposing and joining 7 very small video clips from mov to apple mp4.
A second try failed again but without BSOD and the computer just froze and I had to switch off and reboot
Later in the afternoon it did work without any bug.
I would say, without certainty that some BSOD arrive when I am idle and perhaps mostly at the beginning of a session.
Freezing also happens frequently at the beginning of a session (first ten minutes) or when idle.
It might happen also in relation with the screen saver (slide show mode).
Freezing happens also when using MediaPlayer Home cinema and trying to move too quickly in the movie.

I shall try to use the second option with Grab All.

 

[jeanpierregeorg]

BSOD the GRAB files

I have uploaded the zip file of the "GRAB all"

 

[essenbe]

jeanpierregeorg, it seems to me that most of what you mentioned were high GPU, CPU usage and High Ram usage. I would like you to get some programs, if you don't already have some that will monitor your CPU and GPU temps. I use Core Temp (Core Temp) and my graphics card comes with Precision x (EVGA Utility). I set mine up to where the CPU temp and GPU temp always shows in the system tray. That way I can look down at any time and know what my temps are. If your card does not come with such a Utility, you can check with your card manufacturer and see if they have one. If not, you can also use MSI Afterburner (MSI Afterburner). It is basically an overclocking program, which I do not recommend you use, but in the settings it has some very good monitoring features, such as temp, you can set a custom fan profile to keep your card cooler and such as that and more. I would use it for that. I would like to know your CPU temps and GPU temps when using Freemake Video Converter. I have that program too, although I rarely use it. I use Handbrake a lot, but it is pretty brutal on your system, but can do almost anything. Your system better be very stable before you even start it up. But, please install some reliable program that will monitor your system temps and let me know how they are running while using them. Excessive heat will cause your system to BSOD. Another problem you may have is Dell is not a fan of fans (no pun intended) in their cases. The more fans you can put in bringing fresh air in your case the better off you are, as well as cleaning the dust out of your case with a can of compressed air. Dust can clog up the CPU Cooler and the GPU cooling on any system. You should clean it out frequently. Once you have monitoring programs we can test your GPU and see how it does. With Dell, I am sure you have the stock CPU cooler, which is not very efficient, especially with a hot running CPU like you have. That sort of leaves out a stress test of the CPU. But we can monitor the temps while you are encoding a video and see what it does. If those don't seem to be a problem, we can test the ram and stress out your drivers to see if you have a faulty one.

I tell you all of this to let you know, we have just begun and have a lot of options, to help detect and correct whatever problem you have. So, don't give up yet. Please let me know which programs you decide to use, and advise me of the temps you are seeing at idle, during normal usage and while using freemake. It may give us an indication of which way to go.

 

[essenbe]

There are still no dump files in the dump. Did you set the system for Small Memory Dumps? and did you confirm that you have a folder in C:/Windows named minidump? if you do not have that folder, create it. Create a new folder and name it Minidump. You should only get dump files when you have a BSOD.

 

[jeanpierregeorg]

New BSOD "STOP 0x0000007F" Freemake Video Converter

using Freemake Video Converter new BSOD I shall try to upload files.
Thank you again Essenbe.
After rebooting :
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036


Informations supplémentaires sur le problème :
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002A6D212
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


Fichiers aidant à décrire le problème :
C:\Windows\Minidump\120514-12979-01.dmp
C:\Users\jp\AppData\Local\Temp\WER-25646-0.sysdata.xml
I am uploading the new files of SF


Essenbe I shall try to get the programs you suggest to monitor CPU and GPU

 

[jeanpierregeorg]

after BSOD using Core Temp

I join Core temp file
first one only Firefox and Core Temp
second one Firefox core temp and Freemake

 

[essenbe]

I'm sorry I really can't read the Core temp dump report. Can you tell me what the hottest core was? however, I can read the dump file. This is what it is blaming

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80002a6d212}
[COLOR=red]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption

I hate to ask this as it will take tou quite a few hours to run it. One of my other machines has 8 GB of Ram and it takes it 9.5-10 hours to run it, but it is the best test we know of, so please download it from the linl in the below instructions. If you have any questions, feel free to ask.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[jeanpierregeorg]

Thank you Essenbe, I have downloaded the iso memtest and burned a cd, but I do not remember how to boot on the CD;
is it some key F2 or F12 and when do I press it ? Or configure the boot order but how ?
I already tested the memory with the Microsoft utilities but it was very short (may be 20 minutes) no failure.

 

[essenbe]

This is the best test we have, but takes quite a while. Just from memory, I believe with Dell, it is F12. Guring boot up when you see the Dell Logo strt tapping F12. You only have a couple of seconds, if you are too late, you will boot into your OS. If it works, you will see a list of every hard drive, CD/DVD drive or USB Flash drive attached to your computer. Use the up and down keys to highlight the device you want to boot from, hit enter and it should boot from that device. If you downloaded the version 5.01, when it starts it will say hit some F key or some other key if you have a multicore CPU. DO NOT HIT ANYTHING, the test will begin in a couple of seconds and will continue to run until you stop it. Let it run for a full 8 passes. It will tell you how many passes it has done and how many errors. If it finds even 1 error, stop the test, your ram has failed and there is no reason to continue.

Just so you understand. We are not asking you to run the same test 8 times. Each pass tests a different thing. I think there are 10 tests in each pass they test different things also, So it takes 8 consecutive passes, all at the same time to fully test the ram, if you stop it and start it back, it will start over at the beginning. So, 8 passes all at the same time.

If, for some reason, you cannot get to the boot menu from the F12 key, try F11 or some other key. If that does not work, make sure your CD is in the CD/DVD burner and boot into bios, go to the boot selection part of the bios and set the CD/DVD as 1st boot device and the Hard drive as 2nd boot device, save and exit, you should boot right into the test. After the test, you can either leave it that way or boot into bios and change the boot order. many people set theirs with the CD/DVD as 1 st boot device normally. Dell's used to be shipped that way. The purpose is to alleviate this problem in case the computer won't boot. Just put a repair disk in and boot up, the repair disk will be recognized before the DVD. If you do not have a bootable boot device in the DVD drive, the computer will automatically look to the 2nd boot device, your hard drive. So, either way, or you may be lucky and have to do nothing. just reboot.

 

[jeanpierregeorg]

Thank you Essenbe. In fact the key for set-up was F2. This night I ran the test for a little more than 8 passes (14 hours) and no error. The temperature was constantly 74 or 75 Celsius. So I suppose that the problem does not come from the ram, this is rather good news. I suspect something related to the graphic card or drivers for the Hard drives because I begun to get my computer freezing after changing the hard drive 4 months ago and installing the SSD Samsung. There might be 2 different causes, one for freezing and one for BSOD.

 

[jeanpierregeorg]

Older BSOD and sysdata

I just found 3 files I saved from previous BSOD, I have also 2 older dmp files but I don't know how to read or upload them. I have a sysdata that I cannot upload.

 

[essenbe]

The easiest way is to run the BSD Posting instructions again,
www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2. Use option #2 and press the 'Grab All' button and five it time to do it's collection. Then upload it in your next post.

Please download Core temp and watch your CPU temps. They should have nit been 74C.

 

[jeanpierregeorg]

New Grab results - results of Core-Temp

Essenbe, I ran again SF and Grab all , I attach the results and also a screen capture of Core Temp.
min Temp is 47 C max is 75, most of the time is 51 C. It was 74 C when running memtest.

 

[jeanpierregeorg]

new BSOD stop 0x0000001E saving openoffice to disk

saving a file to disk F new BSOD
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036


Informations supplémentaires sur le problème :
BCCode: 1e
BCP1: FFFFFFFFC0000028
BCP2: FFFFF8000270A7FC
BCP3: FFFFFA8005ACCF60
BCP4: FFFFFA80054AFEA0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
using then Who crashed (home edition) to read and analyse the dump file : drivers accused

 

[essenbe]

jeanpierregeorg, what you uploaded was the instructions for Who Crashed. I need the results from
http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html I don't use Who Crashed.

 

[jeanpierregeorg]

Sorry, here are the "grab all " results

 

[essenbe]

Sorry, I didn't answer the above question. I believe Dell is the F12 key, and use the arrow keys to select the device you want to boot from. Some Dell computers come with the CD/DVD as the 1st boot device which means you don't have to do anything to boot from the DVD, just restart. it will ask if you want to boot from DVD press any key. Do it quickly, I think you only have a couple of seconds.

Here is what the dump file says is the cause

 aswSnx
start             end                 module name
fffff880`0305d000 fffff880`03161000   aswSnx   T (no symbols)           
    Loaded symbol image file: aswSnx.sys
    Image path: aswSnx.sys
    Image name: aswSnx.sys
    Timestamp:        Fri Nov 21 05:17:12 2014 (546F1F38)
    CheckSum:         00102CB2
    ImageSize:        00104000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is the avast! Virtualization Driver

and

aswMonFlt
start             end                 module name
fffff880`070e2000 fffff880`07104000   aswMonFlt T (no symbols)           
    Loaded symbol image file: aswMonFlt.sys
    Image path: aswMonFlt.sys
    Image name: aswMonFlt.sys
    Timestamp:        Thu Nov 06 06:53:07 2014 (545B6F33)
    CheckSum:         0001B7AA
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is the avast! File System Minifilter Driver

I believe I would, at least for the time being, uninstall Avast usint their removal tool (Avast Uninstall Utility | Download aswClear for Avast Removal) and replacing it with Microsoft security essentials https://www.microsoft.com/en-us/download/details.aspx?id=5201

After that, Create a restore point before doing anything. The link to do that is below. Use the computer as normal for at least 24 hours of actual use. it will seem rather sluggish, which is normal. Just be sure when setting it up, to sort the drivers by provider and select all of the non Microsoft drivers.

   Warning

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.