Blue screen if startup with HDMI connected

[hlodver]

I have a brand new MSI Media Live box. The Installation process went fine except when it came to startup after installation. I always receive a blue screen and sometime I have the "irql_not_less_or_equal" message. The system works perfectly when I startup using the VGA connector. I have verified that HDMI does work if I startup using the VGA connector and then extend the desktop.

I have downloaded and install the Windows 7 driver from Nvidia. My card is Geforce 6150. The error descriped above happened using my Philips Tv and also my computer LCD screen.

Any Ideas?

 

[hlodver]

If I remove the HDMI cable from the computer while it is starting up and plug it in again when the login screen has appeared then this works without problems. Also works when starting up from hibernation.

 

[hdwalla]

does windows 7 recognize your phillips tv? since it works after you boot up the driver is just crashing when it tries to set up the tv initially. I mean what does it say your display is when your hdmi is plugged in?

 

[hlodver]

The monitor type in win 7 is Generic PnP Monitor but in the Nvidia Control Panel it is detected as Philips 1080p Tv. Where I change the resolution it is just listed as 1080p Tv. I get the same error when I connect a computer screen via HDMI.

The Tv model is 37PFL7662D/12.

 

[hdwalla]

here is the latest nvidia drivers, you might already have them. It doesn't sound like a hardware issue but its interesting that your hdmi does work but just not plugged in on boot.

NVIDIA Graphics Supercharge Microsoft Windows 7

 

[Dragonfly]

Many times, it's a cable problem with HDMI. Try using a different HDMI 1.3 cable and see if that clears up your handshake problem.

 

[hlodver]

I tried a different cable without any success. What is happening at startup that does not happen like after resuming from hibernation?

 

[angryman]

Strange... I'm using HDMI for my monitor.

How old is the cable itself? As previously suggested try a new cable, to ensure it is 1.3.

The cable seems to be getting windows to load something:

Error Message:


IRQL_NOT_LESS_OR_EQUAL
Explanation:
This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
User Action:
This error usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If you encounter this error while upgrading from Windows NT 4.0 or earlier, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturers to obtain updates of these tools. For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. You should also run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows 2000 drivers. Disable sync negotiation in the SCSI BIOS, check the cables and the SCSI IDs of each device, and confirm proper termination. For enhanced integrated device electronics (EIDE) devices, define the onboard EIDE port as Primary only. Also, check each EIDE device for the proper master/slave/stand-alone setting. Remove all EIDE devices except for hard disks. If the message appears during an installation of Windows 2000, make sure that the computer and all installed peripherals are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://www.microsoft.com. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at [URL="http://support.microsoft.com/support."]http://support.microsoft.com/support.[/URL]

 

[hlodver]

I bought a specific certified HDMI 1.3 cable but the behavior is the same. I sure hoped that this would do the trick...

It would be good to be able to debug what operation is being run when this happens. I might have to downgrade the OS to get rid of this issue. Although I've gotten used to unplugging the cable while starting up, the worst thing when this happens is that the default startup mode changes to "Startup in recovery mode" and I can't select "Start windows normally" (bluetooth keyboard not recognized at this time of startup). This leads to a long time of searching for errors where there are none. Also the cable unplugging/plugging bothers the wife...

 

[Dragonfly]

I have a similar keyboard recognition problem during start up (Microsoft Media Center Keyboard), so I keep a cheap USB keyboard handy. Using that, you should be able to F8 into Safe Mode and see if you still have the problem.

 

[hdwalla]

visited my parents and plugged my hdmi in. And I blue screened on their phillips tv when I booted up?!? So it rebooted and then i made sure the hdmi was fully plugged in then I booted up fine. I don't know if phillips has an issue but it is interesting.

 

[Crunchy Doodle]

So it isn't just me, and not the 7057 build in particular. I too end up in a start up crash, repair cycle if I start up with the brand new HDMI 1.3b cable plugged into my Dell HDTV set. If I plug in the VGA cable, it's very happy and works smoothly. I'm using a Gigabyte motherboard with an nVidia 7100 / 630 chipset. I have the most recent nVidia driver from the nVidia web site. I get the same response with build 7000 or 7057. I'll try the DVI connector next.

Bye.

 

[Crunchy Doodle]

So I tried the same experiment with the DVI output and BOOM! Same crashing as with HDMI. Just maybe, the older 6000 and 7000 series nVidia GPUs don't like to do DVI or HDMI under Windows 7. Could be. :sarc:

My HTPC is running Windows 7, and is connected to the same Dell LCD HDTV via a DVI to HDMI cable. Works flawlessly, of course. It's an ASUS motherboard with an nVidia 9300 chipset.

Bye.

 

[gogosan]

I also have similar problem. i dual boot w7 and xp on the same pc. every time i boot into a different os the blue screen come up on my hdtv, sometime if i reset my pc a few times it works fine. don't have that problem if i kept using the same os though. i had been told that some tv have older firmware might have problems when connecting HDMI Devices..unfortunately my HDTV don't have any firmware updates from the vendor.. so i can't be sure if this will fix the problem

 

[Crunchy Doodle]

I have a simple work-around for me on this HDMI boot crash. I connect both the VGA and HDMI to my Dell HDTV set. I have the VGA as the primary monitor with the HDMI as the secondary. With this setup it boots cleanly with no BSOD, crash. I have MC on the HDMI secondary monitor and the standard desktop on the VGA primary. So far, everything works fine. The only minor oddity is that with MC full screen on the secondary HDMI monitor, it "captures" the mouse pointer onto this secondary monitor. To use the mouse on the primary desktop, I have to set MC to not full screen with the normal icon in the upper right corner.

Bye.

 

[shanghei]

My windows 7 will BSOD on startup if I set the audio to hdmi output. I had to change the audio to speakers so it wouldnt BSOD.