Solved

Blue screen when trying to connect USB DVB-s module (s2400 Technotrend)

Posted on 2007-04-05
11
300 Views
Last Modified: 2013-11-17
Some background:
ACER ASPIRE 5601 awlmi
1024 mb ram, 100 gb hdd, x1300 graphic card, logitech webcam
OS: windows xp sp2
DRIVERS: updated

I just bought an USB DVB-s module for satellite TV. When I am connecting it to the computer the computer keeps rebooting  (give a blue screen for a very short period of time and reboots - with a message i cant read case everything is happening very fast. Only 2 things I could read some address was 0x0,0x0,0x0 and a message IRQ_NOT_LESS_OR_EQUAL).

I tryed stoping some periferals from bios but this phonix bios does let me do anything. Everything is locked.
0
Comment
Question by:giulio1979
  • 5
  • 4
  • 2
11 Comments
 
LVL 29

Accepted Solution

by:
Alan Huseyin Kayahan earned 500 total points
Comment Utility
0
 

Author Comment

by:giulio1979
Comment Utility
I am still at work for the next 5 hours ... I see there are many things to be done there ... I will try them all in the evening.

To bad my bios sucks and I wont be able to free resources from there. Maybe you knowa way to change settings in phoenix bios using some software. I think my bios is customized by Acer specially to lock that option.
0
 
LVL 29

Expert Comment

by:Alan Huseyin Kayahan
Comment Utility
              Trying to change locked settings of BIOS may corrupt the CMOS. Make sure that you enter BIOS with supervisor password/privileges. When you have it, change IRQ of USB if it is a USB device.
               If there is a setting called "PNP OS Installed" set it to yes.
               Try a different USB port.
0
 

Author Comment

by:giulio1979
Comment Utility
I never used password to enter bios. I just press F2 to enter and thats it. It will only let me to change boot order and setup passwords .... nothing else.
0
 
LVL 32

Expert Comment

by:Mark
Comment Utility
To make that BSOD stay on the screen in order to read it you will have to deisable tha Auto restart option.
Left click -->START-->right click MY COMPUTER-->left click PROPERTIES
Left click the ADVANCED tab, then the startup and recovery SETTINGS button
in the system failure section, uncheck the box next to AUTOMATICALLY RESTART
then click OK and OK again until you are back to the desktop.
Now when you plug in the device the BSOD will stay on screen and you can post the message here.
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 32

Expert Comment

by:Mark
Comment Utility
In order to restart the computer after the BSOD, just hold the power button in until it shuts down. then you can remove the usb device and start up normally.
0
 

Author Comment

by:giulio1979
Comment Utility
I disabled Orbicam and the module worked fine. after one reboot it worked fine. at second reboot i got again bsod. the problem is i dont get same message every time. irql_not_less or_equal is just one of them. the addresses change on each reboot.
0
 
LVL 32

Expert Comment

by:Mark
Comment Utility
Have you tried a powered USB hub on this port and then plugged in the USB device.
0
 
LVL 32

Expert Comment

by:Mark
Comment Utility
It would still be helpful to post the BSOD, just the error and the hex code that goes with it would be sufficient. It may also indicate the file also.
0
 

Author Comment

by:giulio1979
Comment Utility
i opened the dmp file with the debugger. maybe this will give more info.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  438e7b21

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!IoBuildSynchronousFsdRequest+46
804f12ba 897304          mov     dword ptr [ebx+4],esi

TRAP_FRAME:  80550088 -- (.trap ffffffff80550088)
ErrCode = 00000002
eax=00000002 ebx=00000000 ecx=0000003d edx=8055b050 esi=8542f950 edi=8542f940
eip=804f12ba esp=805500fc ebp=80550108 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
nt!IoBuildSynchronousFsdRequest+0x46:
804f12ba 897304          mov     dword ptr [ebx+4],esi ds:0023:00000004=????????
Resetting default scope

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from f6f11782 to 8052a8fa

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
80550108 ec62a304 0000001b 852f6030 00000000 nt!IoBuildSynchronousFsdRequest+0x46
80550188 ec62babf 805501f4 80550200 853d501c LVUSBSta+0x2304
805501d4 ec62bebe 854283a8 805501f4 80550200 LVUSBSta+0x3abf
80550210 ec62b7c8 854283a8 85428463 854283a8 LVUSBSta+0x3ebe
80550248 ec62b469 853bb888 853bb888 80550288 LVUSBSta+0x37c8
80550258 804f13f6 85a80928 854283a8 853bb888 LVUSBSta+0x3469
80550288 f6f02090 865e80ec 805502bc f6f050f3 nt!IoCancelIrp+0x120
80550294 f6f050f3 85a24030 854283a8 c000009d USBPORT+0x2090
805502bc f6f05650 865e8028 41427063 f6f054ec USBPORT+0x50f3
805502e0 80501557 865e870c 865e8028 0a0e4ce6 USBPORT+0x5650
805503fc 80501673 8055b0a0 ffdff9c0 ffdff000 nt!ZwYieldExecution+0xeeb
80550428 80544e6f 8055b4a0 00000000 0000350e nt!ZwYieldExecution+0x1007
80550450 80544d54 00000000 0000000e 00000000 nt!KiDispatchInterrupt+0x4bf
8055ae40 00000000 8055ae48 8055ae48 8055ae50 nt!KiDispatchInterrupt+0x3a4


STACK_COMMAND:  .trap 0xffffffff80550088 ; kb

FOLLOWUP_IP:
LVUSBSta+2304
ec62a304 8945fc          mov     dword ptr [ebp-4],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  LVUSBSta+2304

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: LVUSBSta

IMAGE_NAME:  LVUSBSta.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
0
 

Author Comment

by:giulio1979
Comment Utility

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe -
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.050301-1521
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Apr  5 22:03:04.484 2007 (GMT+3)
System Uptime: 0 days 0:03:32.234
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
..................................................................................................................
Loading User Symbols

Loading unloaded module list
....................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 804f12ba, 80550088, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*** ERROR: Module load completed but symbols could not be loaded for LVUSBSta.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS -
Probably caused by : LVUSBSta.sys ( LVUSBSta+2304 )

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

1: kd> g
       ^ No runnable debuggees error in 'g'
1: kd> !
No export  found
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804f12ba, The address that the exception occurred at
Arg3: 80550088, Trap Frame
Arg4: 00000000
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
HP Pavilion dv8t laptop 20 56
Help with AMIDuOS program 3 61
MAC Laptop - No Boot Loader 5 76
Event ID: 1202 / Source: SceCli 6 43
For some time some of our users experienced package loss on a couple of our Lenovo Thinkpad S531 machines running Windows 8 or Windows 8.1 64-bit OS. I was not able to find many answers online, but did after some investigation I began to suspect Blu…
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now