BSOD using FreemakeVideoConverter Page_Fault_ other frequent BSOD

[jeanpierregeorg]

near similar pb found on the web ?

Found on Windows 7 crash error 116 - Games - Graphics & Displays
"I'm repeatedly getting a crash at not quite random intervals:
Occasionally about 5 minutes after first turning the pc on for the day, wont happen again.
After certain game titles, but not others. Graphical intensity doesn't seem to be a factor, as some intensive games run without causing the crash.

It doesn't go to BSOD - the pc crashes or freezes, and I have to power down the pc manually then turn it back on. Tips?

EDIT: Here's my latest minidump, if that helps - https://www.dropbox.com/s/r69t2im0pevm4zw/062014-10576-..."
----------------
Except that I am also getting BSOD since 2 months, but my initial problems were similar (unstead of games the BSOD happening after the first hour were due mainly to Freemake)
I attach another jpeg of drivers to verify. nvstreamkms.sys seems cto come from nvidia and has some bad reviews ? see www.carrona.org

 

[essenbe]

I didn't find anything about nvstreamkms on that page, but it does come from Nvidia. I believe it is part of GEforce experience. It is used to stream to the Nvidia Shield, I believe. I don't use it, but I know others do and have no trouble. I think it causes a few people problems but not others. Most of the problems with it happen in Windows 8.1.

The response at Toms was basically the same as the point of the NVidia tutorial. Do a custom install and just install the PhysX and display driver. The GEforce experience was just added because most people like it. I don't install it. http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

 

[essenbe]

Have you considered doing a clean startup? (http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html) it basically loads windows only, which should not cause a BSOD without hardware problems or corrupted files. Once you determine you are BSOD free, start up 1 program at a time and test it, if all goes well start another until you find the one causing you problems.

Either that or a clean install with just Windows installed and tested, then install 1 program at a time until you find the one causing the problems.

 

[jeanpierregeorg]

BSOD while DriverVerifier runs

First BSOD with driververifier on . BSOD after 15 minutes of computer on. Graball seemed a little longer (9 minutes) than usual. May be it contains more infos ?

 

[essenbe]

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff800029a100f, fffff88009857f80, 0}
[COLOR=red]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption

How many times have you run memtest?

Later on I found this which may be a victim of the memory or it's possibly the Graphics card memory.

fffff880`098575b8  fffff880`038b285eUnable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: [COLOR=red]Unable to verify timestamp for nvlddmkm.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x21785e

If you haven't done it before I would like you to download ad install CPU-Z CPUID - System & hardware benchmark, monitoring, reporting Please post screenshots (http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html) of the memory tab and the SPD tab. You can select each dimm slot on the SPD tab. I would like every one with ram in it. It is not necessary to post the empty one. Do it even if you have done it before please.

I would also like you to run Heaven Benchmark | Unigine: real-time 3D engine (game, simulation, visualization and VR) Ungine Heaven. When it first opens up, you can set the configuration you want. In the second slot select Extreme from the dropdown and nothing else, then push run. Another screen will open, as soon as it starts moving push benchmark in the top left. When done, please post a screenshot of the score. The first screen where you set the configuration should look like this. Please keep track of your GPU temps and stop the test if they get too hot

View attachment 346329

 

[jeanpierregeorg]

New BSOD but crashdump not completed

memory_management 0X0000001A after some updates (computer idle or on screen saver diaporama)
crashdump not completed
I had to plug out and plug in before restart
I shall try heaven benchmark and then CPU-Z CPUID

 

[jeanpierregeorg]

CPU-Z reports

just had a new freeze of mouse when sending screen captures, changed my wireless mouse for a dell mouse... could that be one of the problems ?

 

[jeanpierregeorg]

hardware problem

2 BSOD this morning "memory_management"
second one when trying to load HeavenBenchmark.
Windows suggested running a memory test, I ran the windows mem test which detected "hardware problem" and stopped at 22 % after 44% of phase 1. Could not get the Log .
Reboot and stopped DriverVerifier because it seems the problem might be in memories. I shall do again the mem test ( last time 9 pass 18 hours).
I plan to run Heaven Benchmark
then the memtest this night.
The Microsoft wireless mouse seems HS since yesterday.
I also stopped the MySecurity Center and run without spyware.
I attach the grab file and a Bdlog because updated just before or during the Windows memtest

 

[jeanpierregeorg]

results of Heaven Benchmark

I stopped when it got to 105 °

 

[essenbe]

OK, maybe I shouldn't have had you run the extreme. Do you have a GPU Monitoring tool? which one? On most of them it will allow you to set a fan profile You can set an aggressive fan profile which will make your card run cooler. Do you game any? What are your temps when you do whatever is the most stressful thing you do with the graphics card?

 

[essenbe]

The first BSOD, I could not find anything useful in it. The second BSOD, everything looked like the hard drive or file system. Here is a small excerpt of what I found, but the blame was on the filter Manager, which is a Windows update needed for the hard drive. NTFS is the file system used for Windows.

  fffff880`0143eaa0 Ntfs!_C_specific_handler
fffff880`0257c730  fffff880`0149143c Ntfs!__PchSym_ <PERF> (Ntfs+0x6d43c)
fffff880`0257c738  fffff880`01512d32 Ntfs!NtfsFspCloseInternal+0x186
fffff880`0257c740  00000000`00000000
fffff880`0257c748  fffff800`02708a4d nt!RtlpExecuteHandlerForException+0xd
fffff880`0257c750  fffff880`014790ec Ntfs!NtfsStatusQueue+0x555c
fffff880`0257c758  fffff880`0257dbe0
fffff880`0257c760  00000000`00000000
fffff880`0257c768  fffff880`01424000 Ntfs!RtlULongLongToULong <PERF> (Ntfs+0x0)
fffff880`0257c770  fffff880`0257c810
fffff880`0257c778  fffff800`02707825 nt!RtlDispatchException+0x415
fffff880`0257c780  fffff880`014790ec Ntfs!NtfsStatusQueue+0x555c
fffff880`0257c788  fffff880`0257c7c8
fffff880`0257c790  fffff880`0257d638
fffff880`0257c798  fffff880`01424000 Ntfs!RtlULongLongToULong <PERF> (Ntfs+0x0)
fffff880`0257c7a0  00000000`00000000
fffff880`0257c7a8  00000000`00000000
fffff880`0257c7b0  00000000`00000000
fffff880`0257c7b8  00000000`00000000
fffff880`0257c7c0  fffff880`0257dbe0
fffff880`0257c7c8  fffff880`01424000 Ntfs!RtlULongLongToULong <PERF> (Ntfs+0x0)
fffff880`0257c7d0  fffff880`014790ec Ntfs!NtfsStatusQueue+0x555c
fffff880`0257c7d8  fffff880`0257cd30
fffff880`0257c7e0  00000000`00000000
fffff880`0257c7e8  fffff880`0149143c Ntfs!__PchSym_ <PERF> (Ntfs+0x6d43c)
fffff880`0257c7f0  fffff880`0257e000
fffff880`0257c7f8  fffff880`02578000
fffff880`0257c800  00000000`00000000
fffff880`0257c808  fffff980`131daaf0
fffff880`0257c810  fffff880`01512d32 Ntfs!NtfsFspCloseInternal+0x186
fffff880`0257c818  fffff880`01424000 Ntfs!RtlULongLongToULong <PERF> (Ntfs+0x0)
fffff880`0257c820  fffff880`0149143c Ntfs!__PchSym_ <PERF> (Ntfs+0x6d43c)
fffff880`0257c828  fffff880`0257dbe0
fffff880`0257c830  000004e8`fffffb30
fffff880`0257c838  fffff880`0257c860
fffff880`0257c840  fffff880`0143eaa0 Ntfs!_C_specific_handler
fffff880`0257c848  fffff880`014790ec Ntfs!NtfsStatusQueue+0x555c

 

[jeanpierregeorg]

No GPU monitoring, no gaming. Usually I don't check temperature. Probably the most stressfull for the card would be Freemake Video converter. Windows , when running diagnosis of mem in standard mode (still with driver verifier on) detected a hardware problem , would it be in the 6 Go memories or in the graphic card or elsewere ?

 

[essenbe]

If you received errors while running memtest, it was the ram. Is that what you are saying?

 

[jeanpierregeorg]

Windows Memory Diagnostics

I ran Windows Memory Diagnostics (in standard) with the driver verifier still on. Windows announced a hardware problem and the test did not seem to end. I was not running the Memtest which is more stressfull !
I planned to run again the memtest you advice this night, will I obtain with this test more precisions about what chips are failing ?

 

[jeanpierregeorg]

CPU-Z reports slot 1

I attach results of slot 1 I forgot yesterday

 

[essenbe]

When did this happen? You may find this helpful http://www.sevenforums.com/tutorials/95368-memory-diagnostics-tool-read-event-viewer-log.html

 

[jeanpierregeorg]

Event log

I attach some extracts from the events log

 

[essenbe]

Windows memory diagnostic tests only memory, as far as I am aware. If it said you have hardwareproblems, I am fairly certain it is memory.

 

[jeanpierregeorg]

events log, so many errors but no log of mem test

Thank you Essenbe. This screen of Windows (SDC1149hardwarejpg) while testing memory was explicit about hardware fault, but I could not find any log about this Mem test which in fact was not completed and stopped at 40 % of first pass. I had to unplug and reboot. So the problem ,as you say, most probably lies in the memory chips or the memory card slots. Which implies that I should use again memtest x86 (last time 16 hours for 8 or 9 passes !) and probably try separately every chip and every slot 4 x 4 possibilities ?). I suppose that testing 2 Go is shorter than testing 6 Go but the amount of time is astounding (16 trials ).
Any other possibility to shorten this mem test ?
Another bad point is the number of errors with disk and with NTFS which are more numerous than BSOD.
Some errors also with the Broadcom.
Could there be other bugs ? (the microsoft mouse not responding was due to batteries, wish everything would be as simple)
I attach some views of the logs around 15/01 when the memtest failed.

 

[essenbe]

The problem is that, to me, memory is the worst error you can have. From a debugging perspective, the debugger does not usually pick up a memory error. What normally happens is if the memory faults, or errors out and causes the system to crash, the debugger has to blame something and normally blames the driver that is being used the most at that time. If there are memory problems that means, to me, that the information in the debugger is not reliable information. Unfortunately, memtest86+ is the best memory test we have and as a general rule, the only one most BSOD people will trust. That does not mean it is 100% accurate, but that is the best test we have.