BSOD, possibly while using DVBViewer to record

[BobFX]

Before you mentioned testing in safe mode, I started to swap some hardware:

I have 2 PCs, PC1 the one that was crashing and PC2, that both record using an identical Technotrend sat card.

I swapped the 2 cards. PC2 did not start to crash, which seems to rule out a bard card.

However, at first, PC1 was not able to use the PC2 card: it did recognize it and loaded the correct driver, but "the device did not start".

After removing the driver, several times, rebooting, several times, removing physically the card and putting it back, suddenly it started to work. No idea why.

And so far, no more crashes! An overnight recording went without any problem.

I won't be sure that the problem vanished until at least one week of regular usage (although it reached the point where I could never record more than 15 minutes before a crash, so it's anyway better). I'll post here next week to keep you informed.

If I get new crashes, I'll test in safe mode.

 

[BobFX]

Well, it did not last long, it started crashing again.

I tried in safe mode. I did not get any crash, but I can't use the sat card in that mode, since its driver is not loaded.

However, to stress the PC, I ran the Windows version of Memtest.

The standalone Memtest86 version did not show any error, but this one did!

I removed half of the memory, and it stopped showing errors.

I'm retrying to record now, we'll see how it will go.

I find very surprising that Memtest86 (standalone) did not find any error, and that Memtest (Windows) did.

 

[BobFX]

Still crashing, I think that I need an exorcists!

 

[koolkat77]

Sorry for the late response.
Can you upload new reports.

 

[BobFX]

Sorry for the late response.
Can you upload new reports.

I changed the video renderer used by DVBViewer, and so far, it's not crashing anymore.

It probably won't last, I'll upload a report when it will happen again.

Thanks.

 

[BobFX]

Well, no more crashes in a couple of days, I think that I found the culprit.

There were apparently 2 problems: bad memory (not detected by standalone Memtest), and a video renderer not to be used with Win7.

Thanks for your tips, the process of elimination helped.

 

[koolkat77]

Thanks for the update.

Let us know how things are after a week of observation.

 

[BobFX]

Well, the PC does no longer crash when recording, so that's a significant progress.

It does however crash when doing work that does intensive display, like when editing a recording with VideoRedo.

Please note that this PC is used over RDP. I made a few tries directly on the console, and could not trigger a crash. It's not 100% conclusive, I haven't found a way to make a systematic crash, but this could be happening only in an RDP session.

I attach the latest dumps, thanks.

 

[koolkat77]

Caused by Acronis again.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800728b2a8, fffff8800728ab00, fffff80002dd794e}

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

Followup: MachineOwner
---------

fffff880`0728a378  fffff800`02af2bcb nt!KeQueryCurrentStackInformation+0x4b
fffff880`0728a380  fffff880`0728b2a8
fffff880`0728a388  fffff880`0728ab00
fffff880`0728a390  00000000`00000000
fffff880`0728a398  fffff880`0124ee28 Ntfs!_C_specific_handler
fffff880`0728a3a0  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)
fffff880`0728a3a8  fffff880`012b96b4 Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`0728a3b0  00000000`00000000
fffff880`0728a3b8  fffff800`02af2aed nt!RtlpExecuteHandlerForException+0xd
fffff880`0728a3c0  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a3c8  fffff880`0728b7c0
fffff880`0728a3d0  00000000`00000000
fffff880`0728a3d8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a3e0  fffff880`0728a480
fffff880`0728a3e8  fffff800`02af18c5 nt!RtlDispatchException+0x415
fffff880`0728a3f0  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a3f8  fffff880`0728a438
fffff880`0728a400  fffff880`0728b2a8
fffff880`0728a408  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a410  00000000`00000000
fffff880`0728a418  fffffa80`01e57a00
fffff880`0728a420  fffffa80`02946cb8
fffff880`0728a428  fffffa80`0293bd80
fffff880`0728a430  fffff880`0728b7c0
fffff880`0728a438  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a440  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a448  fffff880`0728a9a0
fffff880`0728a450  00000000`00000000
fffff880`0728a458  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)
fffff880`0728a460  fffff880`0728c000
fffff880`0728a468  fffff880`07284000
fffff880`0728a470  00000000`00000000
fffff880`0728a478  00000000`00000000
fffff880`0728a480  fffff880`012b96b4 Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`0728a488  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a490  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)
fffff880`0728a498  fffff880`0728b7c0
fffff880`0728a4a0  fffffa80`01e57a60
fffff880`0728a4a8  fffff880`0728a4d0
fffff880`0728a4b0  fffff880`0124ee28 Ntfs!_C_specific_handler
fffff880`0728a4b8  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a528  fffff880`01bb65c2Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
 snapman+0x235c2
fffff880`0728a9a8  fffff800`02dd7830 nt!FsRtlNotifyFilterReportChange
fffff880`0728a9b0  fffff880`012b9700 Ntfs!NtfsQueryStreamsInfo
fffff880`0728a9b8  fffff800`02a49000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0728a9c0  fffff800`02ce30d4 nt!BBTBuffer <PERF> (nt+0x29a0d4)
fffff880`0728a9c8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a9d0  fffff880`0129bac8 Ntfs!__PchSym_ <PERF> (Ntfs+0x66ac8)
fffff880`0728a9d8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a9e0  fffff880`0129df88 Ntfs!__PchSym_ <PERF> (Ntfs+0x68f88)
fffff880`0728a9e8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a9f0  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)

And you may need to add more ram to your system.

 

[BobFX]

But, remember, I still had those video related crashes when I removed Acronis!

 

[koolkat77]

Upload a screenshot of your hard disk using CrystalDiskInfo and Summary tab using Speccy:

• CrystalDiskInfo - Software - Crystal Dew World
• Speccy - System Information - Free Download
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

 

[BobFX]

About disks tests, I already tried to move the Windows system from the Samsung SSD to one of the regular hard drives, and that did not change anything.

I think that pretty much rules out the operating system drive.

I ran a check on all drives without any error found.

I also tried to change the drive where DVBViewer writes its recordings, and it did not help either.

That also should rule out the data drive as source of the problem.

Anyway, here are the CrystalDiskInfo cap, and a txt file generated by Speccy.

 

[koolkat77]

Sorry for the late reply.

I've actually run out of ideas.

Please upload fresh BSOD reports.

 

[Vir Gnarus]

I think we should backtrack here and try approaching this again from the beginning.

It looks like you don't have Driver Verifier turned on. Turn it on, restart system, let it BSOD your system some, then go into Safe mode, turn it off, return to normal Windows and then send us the resulting crashdumps.

 

[BobFX]

Unfortunately, turning the Verifier on made Windows unable to start.

An automatic repair was launched, which worked, allowing to go back to the previous state.

Thanks for the suggestion.

I'm thinking now to swap the graphic card, since the problem appears to be display related, and see what happens.

 

[Vir Gnarus]

That means Driver Verifier is doing its job. It's detecting a driver bug in a driver loaded at Windows startup and it is responding by BSODing the system. Typically this appears to a user as a boot loop as the system is set to automatically restart after a BSOD. Hopefully, you may be able to find some new crashdumps in C:\Windows\Minidump, in which case archive those and send them to us for analysis.

 

[BobFX]

Here is the one generated today with Verifier.

 

[Vir Gnarus]

You made sure that when you were at the part to select drivers in Driver Verifier that you only selected drivers that did not have Microsoft Corporation as their vendor, yes?

Unfortunately this minidump has just not enough info in it, but I thiiiink with what little it gives me it may be enough. I've discovered the AverMedia TV Tuner driver to be present within the thread responsible for doing the device I/O that tripped up Driver Verifier. The driver itself is quite old, as in pre-Windows 7 old (June 5 2009). Please find an update for it, and if there isn't, then it may be time to look for a replacement for it, since most likely it has reached its EOL (End of Life).

Analysts:

Driver Verifier found something, but the IRP nor the callstack tells any tales. However, dump the raw stack of the offending thread to find a little devil lurking within:

3: kd> !niemiro.rawstack
dps fffff88003378dc8 fffff88003379d68
fffff880`03378dc8  fffff800`02f523dc nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03378dd0  00000000`000000c9
fffff880`03378dd8  00000000`00000213
fffff880`03378de0  fffff880`04fbdda5 ks!CKsDevice::DispatchPnp+0x5c1
fffff880`03378de8  fffff980`07150cf0

...

fffff880`033790e0  fffff980`07150cf0
fffff880`033790e8  00000000`00000002
fffff880`033790f0  fffff880`04fae560 ks!WPP_ThisDir_CTLGUID_AvStream+0xb0
[COLOR=Red]fffff880`033790f8  fffff880`04e53764*** WARNING: Unable to verify timestamp for AVerBDA716x_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for AVerBDA716x_x64.sys
 AVerBDA716x_x64+0x764[/COLOR]
fffff880`03379100  00000000`00000000
fffff880`03379108  fffffa80`039bdb90

...

3: kd> lmvm AVerBDA716x_x64
start             end                 module name
fffff880`04e53000 fffff880`04f9dc80   AVerBDA716x_x64 T (no symbols)           
    Loaded symbol image file: AVerBDA716x_x64.sys
    Image path: \SystemRoot\system32\DRIVERS\AVerBDA716x_x64.sys
    Image name: AVerBDA716x_x64.sys
    Timestamp:        [COLOR=Red]Fri Jun 05 05:58:38 2009 [/COLOR](4A28EC4E)
    CheckSum:         00157483
    ImageSize:        0014AC80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[BobFX]

The Avermedia driver is actually the latest one available, and is cited by Aver like being compatible with W7x64.

This PC uses 2 tuner cards: the Aver one, which just never made the PC crash, and a Technotrend one used with DVBViewer.

It's using DVBViewer that was making the PC crash, until I changed the display renderer for it. And I get crashes now only when using display applications like VideoRedo or VLC.

The Aver app does not display anything, it just records, and as I said, it just never crashed when used alone.

I don't doubt that it made the PC crash when using it in Verifier mode since you spotted it, but I really don't think it's the cause of my problems, unless it's for some reason interacting with the video drivers. I do get crashes when the Aver card is not in use.

Anyway, I just can't update it, and I need it!

I'll see this week if I can swap the graphic card, and report about it.

And yes, I did check out all the Microsoft drivers.

Thank you for your help.

 

[Vir Gnarus]

I just cannot believe their statement that it's compatible if the driver predates Windows 7 RTM. In fact, it is definitely evident from Driver Verifier that the driver has a serious bug in it. It is trying to manipulate I/O that it has absolutely no reason fiddling with.

Driver Verifier does I/O checks for drivers by sending fake erroneous I/O to drivers. By Windows driver conventions, if a driver does not understand an I/O passed to it, it is required to pass it down the line so that something that does understand will receive and operate accordingly. The Aver driver is not doing this, which means it is attempting to interact and manipulate I/O it has no business dealing with. If it will do it with the fake DV I/O, then it will do it with normal I/O.

This is especially true if the two TV Tuner cards sit in the same driver stack (very likely). If I/O is being passed down that stack that caters to the Technotrend card, the Aver card will still try to mess with it, which will cause a whole sort of issues once it reaches the Technotrend card driver - or, if it's after the Technotrend driver, it's manipulating the results of that driver, which in turn will change the total outcome of the I/O, again causing unexpected results. The Aver card may be compatible with Windows 7 (doubt it), but for sure it probably isn't compatible with the other tuner card.

I would love to present more concrete evidence to show you, but I cannot access it because minidumps do not retain that information. I would need at least the kernel dump (MEMORY.DMP in Windows folder). Rest assured, though, that there is very little chance this is a false positive, but rather that Driver Verifier is doing its job and is finding a driver operating in an unstable and unexpected manner, which so happens to be the Aver driver. The fault given by it coincides with your description of the symptoms as well as the previous crashes.

Either the driver itself needs to be updated, which appears that may not be an option, or you need to change your usage of the system to adjust to the limitations of the bug present in that driver, which means disabling the Aver TV tuner card while the Technotrend one is running, and vice versa. If your work requires both cards, then you need to see about getting updated models or brands, because the bug will still continue to be present in the Aver driver. You will either need to remove the bug by installing an updated driver or replace/remove the card or work around the bug.