mysterious bluescreens (its no solved)

[fraham]

Hello,

I had search a german TBS-forum but not found...
sorry for my broken english. (so are some passages translate by Google translator)


Serval times a week or a day i get a bluescreen, if the Q-Box S2 is connectet to the Computer and to the working power supply. But there are also times (days, weeks, mounth) without bluescreens or hanger System.

It does no matter whether i wath TV (Q-Box in use) or not (Q-Box not in use).
It also does no matter if the Computer works around the Day or i use the standby-Modus and wake it from standby or i shutdown the PC an boot new, if i make "work breaks".

It also does no matter, which OS (Windows XP, Windows 7 or Linux Mint) and which Driver Versions i use.
Also, there seems to be no matter what hardware I use... (before and after the PC get completly new components: Mainboard, CPU, RAM, graphics - only external devices ans internal drives are the old same)

I only watch TV on evening. Therefore, it irritates me, that i get bluescreens even during the day, where i not wath TV. (green LED is off)

if i reboot the PC after a bluescreen and the USB-connections or the power-connection from the Q-Box was not disconnectet, the PC hang up in the BIOS by checking the USB.

I can disconnect all other USB-devices, but the PC does not boot. Only if the Q-Box was disconnect on USB or powersupply the PC will boot.


For me, the situation is as if the Q-Box hangs himself and thus entrains the PC.


Has anyone had a same or similar Problem or does anyone knows a solution?


Thanks for helpfull answers!

[fraham]

OK, i think i have fixed my problem...

The USB ports gets permanently +5V to the USB connected Hardware whether the Computer is in use, in hipernate or switched of by power-button.
Only switch off the power Switch from the powersupply or disconnect the power cord gets the effect, that the +5V USB voltage shut off. (My Computer need by diconnect the power cord far more then 10 secunds to discharge the capacitors, so the +5V USB voltage will be reach to 0V. If the +5V USB voltage not cmpletly gets the 0V, so will the USB-Port not reset/disconnect the communication to the Q-Box)

Since i switch the USB +5V power Jumper for this USB Port to "OFF", i had no further problems in Windows and also problems under LINUX.

I hope it will remain so in the future!

----


If you also have a semilar Problem, so check the setting for the +5V USB power. => If the Setting set to "OFF" the USB-communication between Computer and Q-Box S2 will be disconnectet/resetted, if the Computer will be switched to hipernate or "OFF" (by Power-Button)

[fraham]

Sorry, the problem is not solved...

There are 4 days without problems after i had set the Jumper for the USB-Ports to power off the +5V USB voltage. That's why I thought that the problem ist fixed and i can post my solution. But:

Just 2 hours after send my last post with the imaginary solution has the computer hung up again with a bluescreen under windows...


The Q-BOX S2 is frozen again and crashed the Computer, so that the Computer thinks the USB is broken or there is a driver Problem

bluescreen says: DRIVER_POWER_STATE_FAILURE


after reboot the Computer the same problem: hang up in BIOS by initialize the USB ports
=> unplug the power cord of the Q-Box (and new plug in) and the Computer continues to boot.


I just do not know what I could check or test everything...

- the energy settings for the USB are not set to "save energy"
- if the Computer goes to power off (by button) or to hipernate, the +5V USB power Switch off
- after bluescreen the power cord from the Q-BOX must unpluged, so that the Computer does not hang in the BIOS by initialize the USB ports




PS:
Let's see how often the Q-Box will hang up in the future with the current USB settings yet.

I will report ...

[fraham]

Now there was the day before yesterday an renewed Crash with the new Settings...

Yesterday I then flashed the latest BIOS update.

Let's see what happens next. I will Report...

[fraham]

Now I just had a blue screen again and again the Q-BOX is frozen ...

So the BIOS update has also brought no change.

I'm desperate. What could I even check?

[fraham]

on 02-19-2014 a new Bluescreen...

in the last time i search for Debugging Tools and found "Windows Debugger"

Here the Output:

Code: Select All Code

Loading Dump File [C:\Windows\Minidump\021914-19609-01 - Kopie.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0a84fc32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
Symbol search path is: SRV*C:\Symbole\x64*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03250000 PsLoadedModuleList = 0xfffff800`034936d0
Debug session time: Wed Feb 19 16:32:47.969 2014 (UTC + 1:00)
System Uptime: 0 days 5:42:06.515
Loading Kernel Symbols
...............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 9F, {3, fffffa8008d4d060, fffff80000b9c3d8, fffffa80098325d0}
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8008d4d060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa80098325d0, The blocked IRP
 
Debugging Details:
------------------
 
 
DRVPOWERSTATE_SUBCODE:  3
 
IRP_ADDRESS:  fffffa80098325d0
 
DEVICE_OBJECT: fffffa8008dd5e10
 
DRIVER_OBJECT: 0000000100000001
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0x9F
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  2
 
STACK_TEXT: 
fffff800`00b9c388 fffff800`033358d2 : 00000000`0000009f 00000000`00000003 fffffa80`08d4d060 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`032d085c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`032d06f6 : fffffa80`08cc1a30 fffffa80`08cc1a30 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`032d05de : 0000002f`cac1a4a8 fffff800`00b9cb18 00000000`001413d1 fffff800`03444ca8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`032d03c7 : 00000010`e0c387c5 00000010`001413d1 00000010`e0c38725 00000000`000000d1 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`032bd8ca : fffff800`03440e80 fffff800`0344ecc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
 
 
STACK_COMMAND:  kb
 
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: Unknown_Module
 
IMAGE_NAME:  Unknown_Image
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE
 
BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE
 
Followup: MachineOwner
---------
 

I hope I interpret this output correctly:

a device is blocking an Irp for to long time...

This should coincide with my observation that the Q-BOX freezes itself when a blue screen is displayed.


what I forgot to specify - My computer hardware:

Board: Asus M5A78L/USB3 ; Chipset: AMD 760G (780L)/SB710
CPU: AMD FX(TM)-4100 Qaud-Core mit 3,6GHz
RAM: 8GB (2x4GB; I think it's Infinion)
Grafik: Gainward GeForce 210 512MB “SilentFX” (Chipset: NVIDIA GeForce 210) on PCIe 2.0 x16

[fraham]

Helo,

Since 02/19/2014 I had dry weather and no more problems with my Q-BOX.
But on 27.02.2014, there were again some rain showers and promptly gave some rain also once again a blue screen.

Should it be about a weather-dependent problem? (in certain circumstances any current leakages?)
OK, now I had suspected something like that, because it in time to the frequent blue screens was indeed quite humid weather.
But I was not so sure ...

Should the last blue screen on this rainy day as confirm my guess or was it just an unfortunate coincidence?

So I examined the plug on the ingress of moisture on the quad LNB. => No moisture in the plugs!
But where there seems to be no moisture, then it should be no gives current leakage, right?!

I also could not see any damage to the flat antenna and the mounted quad LNB...

very mysterious!

So where the disturbances come from and why apparently only in humid weather?

-----

That reminds me yet again just one, at that time I even had problems with the CB radio: On the day I had many faults and these faults were worse so, the more moist the Gambles was ... (strong noise)
But I have given up the hobby of CB radio years ago.


I know that in front of my house in the ground runs a 15kV power line.

Should there give about relationships?
(Maybe disorders that are caused by the power line)

-----

But why is it only disturbs the Q-box and not the other 3 receivers? => very mysterious!

[fraham]

OK, it's not a rain-Problem...
LNB and connectors are dry.

But the last days are also dry and i got crashes again...

...and a relationships with the 15kV power line is also likely to retire => Why did I have in the time before no crashes with the Q-Box?


But what can also cause crashes? Why can freeze the Q-box and block an interrupt for too long time?

? thermal Problems with the Q-Box ?
? Problems in order with the Mainboard chipset ?
? Interference in the antenna line, such as voltage fluctuations, if on another receiver, the programs are switched => Quad-LNB) ?

[xite]

I have the same issue with my TV Software. After using the Q-Box for an hour or two the program freezes.
First i thought, it must be an software issue. I updated all the drivers and the TV software. Nothing helped.

Then, after a nother crash, i restart the PC an put an ice bag on the box. Everything works fine.
So in my opinion, the Q-Box 2 have an termal issue. Today i opened the housing of the box. Hope that will help against the overheat. Next step will be to but an heat sink on the TV chip.

[fraham]

my issue is not the tv Software. the issue comes from the the Q-BOX: Bluescreen and than a frozen USB communication between Q-BOX and Computer. after reset the Computer hangs when booting on the point "intitialize USB ports". either i pull out the USB cable or i pull out the Power cord from the Q-Box... hardly any of this plugs was pulled, boot the computer on immediately.
(Evaluation of the log says: IRQ blocked for to long time)
The issue seems to be related to the wakeup from standby...
Most days there are no problems. But in any one day there after a random time then a blue Screen...

a thermal issue - that was also one of my thoughts...

=> the one chip is really very hot, if the Q-Box hangs up
the heat from this Chip is transferred via the board itself onto the housing. Because there is no airflow to the outside, so the air in the housing also heats up...

If it really is a temperature problem, you will not have to try:
- provide a beter air circulation to the outside
- provide for better heat dissipation to the housing and larger cooling surface for the housing


A operation with open housing unfortunately brought no improvement. (Even using a fan without a heatsink)
So I think it is probably less of a heat Problem...


My currently safe working solution:
The USB cable and power management will only be connected to the Q-Box if I want to watch TV or listen to the radio.