Windows Crashes / Blue screens

[thebluevoice]

Hi!

My Setup hardware:

HP N54L microserver 8GB ram.
6280 dual tuner

Software:

Windows 7 sp1 pro 64bit
Mediaportal standalone tv server 1.6

I get the same crashes in either pcie slot on the N54L and also on a N40L microserver.. (these machines are identical except processor faster clock speed so easy to swap hd from one to the other - this helps as ensures minimal changes)

It ran for several months quite stable, I think I started getting the crashes around the time I updated the TBS driver in nov/dec..

Now it seems to crash every few days or a week randomly, mostly over night when the server is not being accessed to stream live tv.

I've booted a mem check program from usb and left that running 36 hours with no error reports.
Also left prime torture test running for 2 days on it while the tv server was running and had no errors...

Anyone else having problems?

I was wondering as was thinking of purchasing another tuner (either the new dual or new low profile quad dvbt2s) and am I right in assuming that I would need the driver released in nov/dec to support both the new cards and the original 6280? Can both the old 6280 and the new cards be run at the same time?

I ask this as was thinking of trying to rollback to an older version of the tbs driver and see if that stops the crashes?

Partial windows mini-dump as wont allow me to attach ...

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000000fc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003c519ef, address which referenced memory

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002860000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 51a86355

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000000000fc

CURRENT_IRQL: 0

FAULTING_IP:
TBS6280_64+359ef
fffff880`03c519ef 83b9fc00000000 cmp dword ptr [rcx+0FCh],0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff800028d5169 to fffff800028d5bc0



FOLLOWUP_IP:
TBS6280_64+359ef
fffff880`03c519ef 83b9fc00000000 cmp dword ptr [rcx+0FCh],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: TBS6280_64+359ef

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: TBS6280_64

IMAGE_NAME: TBS6280_64.sys

BUCKET_ID: WRONG_SYMBOLS

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

0: kd> lmvm TBS6280_64
start end module name
fffff880`03c1c000 fffff880`03dea480 TBS6280_64 (no symbols)
Loaded symbol image file: TBS6280_64.sys
Image path: \SystemRoot\system32\DRIVERS\TBS6280_64.sys
Image name: TBS6280_64.sys
Timestamp: Fri May 31 09:46:13 2013 (51A86355)
CheckSum: 001D68E3
ImageSize: 001CE480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm TBS6280_64
start end module name
fffff880`03c1c000 fffff880`03dea480 TBS6280_64 (no symbols)
Loaded symbol image file: TBS6280_64.sys
Image path: \SystemRoot\system32\DRIVERS\TBS6280_64.sys
Image name: TBS6280_64.sys
Timestamp: Fri May 31 09:46:13 2013 (51A86355)
CheckSum: 001D68E3
ImageSize: 001CE480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm nt


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000000fc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003c519ef, address which referenced memory



ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002860000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 51a86355

READ_ADDRESS: 00000000000000fc

CURRENT_IRQL: 0

FAULTING_IP:
TBS6280_64+359ef
fffff880`03c519ef 83b9fc00000000 cmp dword ptr [rcx+0FCh],0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff800028d5169 to fffff800028d5bc0

STACK_TEXT:
fffff880`0844a278 fffff800`028d5169 : 00000000`0000000a 00000000`000000fc 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0844a280 fffff800`028d3de0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`069fc9d0 : nt!KeSynchronizeExecution+0x3d39
fffff880`0844a3c0 fffff880`03c519ef : fffffa80`069fc9d0 fffffa80`069fc9d0 00000002`1e614000 00000000`00000000 : nt!KeSynchronizeExecution+0x29b0
fffff880`0844a550 fffff880`03c3016b : fffffa80`098a5230 fffffa80`06a1db08 fffffa80`0b85bb00 00000000`00000000 : TBS6280_64+0x359ef
fffff880`0844a5e0 fffff880`04848cef : fffffa80`07b92e00 00000000`00000000 fffffa80`06734900 fffffa80`07d23700 : TBS6280_64+0x1416b
fffff880`0844a610 fffff880`04848e8c : fffffa80`06a1db08 00000000`00000000 fffffa80`09cd7c00 fffffa80`0b85bb00 : ks+0x2cef
fffff880`0844a660 fffff880`04848487 : fffffa80`0b85ba30 fffffa80`09cd7c00 fffffa80`0a16ea50 fffffa80`0b85ba30 : ks!KsGetPinFromIrp+0xe4
fffff880`0844a690 fffff880`048481d1 : fffffa80`0b85ba30 fffffa80`09cd7c18 fffffa80`09cd7980 fffffa80`0a16ea50 : ks+0x2487
fffff880`0844a6d0 fffff880`0486126f : 00000000`00000000 00000000`00000000 fffff880`0844a7d0 fffffa80`0a3d3d18 : ks+0x21d1
fffff880`0844a760 fffff880`048607bb : fffffa80`079e6010 00000000`00000000 fffff6fc`40049fd8 fffffa80`07c9b550 : ks!KsProbeStreamIrp+0x6ff
fffff880`0844a7c0 fffff880`04847560 : 00000000`00000000 6874734b`00000000 fffffa80`0aa4deb0 00000000`0000000d : ks!KsDispatchIrp+0xdb
fffff880`0844a7f0 fffff880`03c1f592 : fffffa80`079e33a0 fffffa80`0a3d3cd0 ecc00001`1d9a3867 00000000`00000000 : ks+0x1560
fffff880`0844a830 fffff880`03c1c419 : fffffa80`079e33a0 00000000`00000000 fffffa80`0724aa60 fffff880`0844aa20 : TBS6280_64+0x3592
fffff880`0844a860 fffff880`03df32b9 : fffffa80`0acae010 fffffa80`0acae010 fffffa80`00000001 00000000`000007ff : TBS6280_64+0x419
fffff880`0844a890 fffff880`03df029e : fffffa80`07c9b550 fffffa80`00000000 00000000`00000000 fffff880`0844aa20 : ksthunk+0x42b9
fffff880`0844a950 fffff880`03defa01 : fffffa80`0acae010 fffffa80`07c7a150 00000000`00000000 00000000`00000cc0 : ksthunk+0x129e
fffff880`0844a980 fffff880`03def79b : 00000000`00000001 fffffa80`0acae290 fffffa80`07c7a150 fffffa80`0acae010 : ksthunk+0xa01
fffff880`0844a9b0 fffff800`02bf23a7 : fffffa80`06a9df20 fffff880`0844aca0 fffffa80`00000000 fffffa80`06a9df20 : ksthunk+0x79b
fffff880`0844aa10 fffff800`02bf2c06 : 00000000`093ee5d8 00000000`00000e38 00000000`00000001 00000000`059854b4 : nt!NtMapViewOfSection+0x15a7
fffff880`0844ab40 fffff800`028d4e53 : fffffa80`069d4a00 00000000`093ee578 fffff880`0844abc8 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`0844abb0 00000000`73962e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x3a23
00000000`093eee88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73962e09


STACK_COMMAND: kb

FOLLOWUP_IP:
TBS6280_64+359ef
fffff880`03c519ef 83b9fc00000000 cmp dword ptr [rcx+0FCh],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: TBS6280_64+359ef

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: TBS6280_64

IMAGE_NAME: TBS6280_64.sys

BUCKET_ID: WRONG_SYMBOLS

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

0: kd> lmvm nt
start end module name
fffff800`02860000 fffff800`02e45000 nt (export symbols) ntkrnlmp.exe
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Thu Aug 29 02:13:25 2013 (521EA035)
CheckSum: 0054CBB3
ImageSize: 005E5000
File version: 6.1.7601.18247
Product version: 6.1.7601.18247
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7601.18247
FileVersion: 6.1.7601.18247 (win7sp1_gdr.130828-1532)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

0: kd> lmvm TBS6280_64
start end module name
fffff880`03c1c000 fffff880`03dea480 TBS6280_64 (no symbols)
Loaded symbol image file: TBS6280_64.sys
Image path: \SystemRoot\system32\DRIVERS\TBS6280_64.sys
Image name: TBS6280_64.sys
Timestamp: Fri May 31 09:46:13 2013 (51A86355)
CheckSum: 001D68E3
ImageSize: 001CE480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

[thebluevoice]

Hmm.

I've tried different ram and a different machine.

Still getting blue screens the same every few days.

Could it be the 6280 card itself has gone faulty?

[steven]

Hi thebluevoice

so strange.

as you have said that your older driver is ok?

Do you have tried to use the older driver,is it the same or ok ?

Thanks

Kind Regards

steven

[thebluevoice]

Hi Steven,

Well I tried a fresh windows install and used the older drive but still had the same problems.

I'm going to try a 6281 and see if that works reliably - then a t least I can rule out the card.
I've already tried different RAM, pcie clots and an entirely different machine lol

Thanks anyway

[infi]

Hi Steven,

Well I tried a fresh windows install and used the older drive but still had the same problems.

I'm going to try a 6281 and see if that works reliably - then a t least I can rule out the card.
I've already tried different RAM, pcie clots and an entirely different machine lol

Thanks anyway

Out of curiosity, did you ever get the 6280 stable on your N54L? I only ask as I've been plagued with random BSOD's on mine too running WHS 2011. There's an update in the Windows Action Centre with a solution that mentions the 6280, but in seemingly typical Microsoft form of late when it comes to identifying issues, the solution won't display - it just keeps telling me I'm not connected to the internet, which I clearly am as everything else works and I'm running an email & web server on that box.

I'm currently trying the previous driver to see if that makes a difference, but I'm not holding my breath.

[thebluevoice]

Hi infi.

It kept doing it and eventually got shipped a new replacement card the 6285.

Seems to have been quite stable but still had 1 or 2 bsods - attributed to the same bug check in the tbs driver...

Thanks for the info about MS - I'll start looking at it too if you could point me in the right direction?

Cheers!

[infi]

Hi infi.

It kept doing it and eventually got shipped a new replacement card the 6285.

Seems to have been quite stable but still had 1 or 2 bsods - attributed to the same bug check in the tbs driver...

Thanks for the info about MS - I'll start looking at it too if you could point me in the right direction?

Cheers!

Hi thebluevoice,

I still can't tell you exactly what the MS solution is as my fully functioning email & web server apparently still isn't connected to the internet

All I can say is that I used the Action Center to check for solutions and when I looked back there the other week, it said it had found one for the BSoDs.

The technical detail looks similar to part of your original post:

Source
Windows

Summary
Shut down unexpectedly

Date
‎02/‎10/‎2014 21:11

Status
Solution available

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.33040.34
Locale ID: 2057

Extra information about the problem
BCCode: d1
BCP1: 00000000000000FC
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880056579EF
OS Version: 6_1_7601
Service Pack: 1_0
Product: 33040_3
Bucket ID: X64_0xD1_TBS6280_64+359ef
Server information: 925a9528-d15a-4d11-a160-1f2e1941696b

Note the bucket ID which names the TBS 6280.

I'm still keeping an eye on the server to see if it BSoDs with the older driver. It hasn't so far (famous last words) but I had to reboot it midweek to install the 'Patch Tuesday' updates.

[infi]

Mini update from me.

I've been testing the 1.0.1.1 driver now for 3 or 4 weeks, and I haven't had a single BSoD! (long may it continue)

I'm not sure what all the changes were in the 1.0.1.2 driver, but the 1.0.1.1 driver seems to be working without any notable problems at this end.

I have been speaking with TBS support (very responsive they are too ), and I've made them aware of my current status with the 1.0.1.1 driver. Whether a newer driver appears or not, time will tell, but I guess they'll need to work out exactly what's causing the BSoD first.

[infi]

Further update to my previous post.

It's been three months since I last posted, and my HP Microserver has only blue screened once in that time, so I'd say there's absolutely no doubt at all that the 1.0.1.2 driver most definitely has problems that the 1.0.1.1 doesn't.

Much as I'd like to see a new driver that addresses the issues introduced in the 1.0.1.2 driver, I'm just happy I'm no longer getting weekly BSoDs.

[infi]

Final update on this thread (hopefully ).

The day after I made my last post, the server Blue Screened (typical!).

I decided I was fed up with Microsoft and their inability to provide support for their products (they wanted to charge me £60 to tell me what the Action Center message said), so I downloaded some debugging tools and ran the dump file through it.

I emailed support with the resulting output, and a day later they sent me a new test driver, which I've now been running for nearly 3 weeks without issue (tempting fate again ). I note that since I emailed them a couple of days ago, they've updated that new driver (1.0.1.3) onto the site, so if anyone else is experiencing BSoDs on the 6280, hopefully the new driver will resolve it for them.