Page 1 of 1

BSOD on Win7 64 bit

PostPosted: Wed May 27, 2009 1:44 am
by kamalh
I am getting a blue screen with a 0x0000007e code when Win 7 64 bit RC starts up.
It only seems to happen when USB-UIRT is plugged in and only when Windows starts.
If I unplug USB-UIRT and restart, Windows starts just fine and once Windows has started, I can plug in the USB-UIRT without any problems.

Every time though, if the USB-UIRT is plugged in during startup I get the BSOD with the same code 0x0000007e.
This happens on both an external USB hub as well when connected directly to a port on the system.

Any ideas what I can do here ?

My system details:
Asus M4N78 Pro motherboard with latest BIOS
nVidia 9500GT video card
AMD Phenom II x4 810
8 GB RAM
Antect case with 500 W power supply
Hauppauge 1600 TV card

Windows 7 64 bit RC build 7100
USB-UIRT Vista drivers 20204
Thanks

BSOD workaround

PostPosted: Sun Aug 09, 2009 2:54 am
by nappysolo
This is a fairly old post, so you may have found a solution. It sounds like the same problem I am having. I have 8GB of RAM in my system. If you use "msconfig" to set a maximum limit on the OS RAM usage to 4095, the BSOD goes away. I was also having a problem on my new configuration - Win7 X64 with 8GB RAM - with my old Hauppauge PVR-150 card. Hauppauge reports that their x64 driver for this card won't work with more than 3GB of RAM in the system. It appears that limiting the RAM fixes both problems.

Not really a fix, but at least I can operate until updated drivers are available.

PostPosted: Sat Aug 15, 2009 2:02 am
by antrillion
I have the same BSOD problem on Windows 7 x64 RTM with 8GB memory on startup. Plugging the device in after startup and everything works fine, but starting windows with my USB-UIRT plugged in and the BSOD is the result.

0x0000007E on new 8GB Windows 7 x64 system

PostPosted: Wed Aug 19, 2009 2:48 pm
by ftsi
I've posted my take on this issue here: (avoid duplicate postings)
http://www.usbuirt.com/phpBB2/viewtopic.php?t=5938

It is my hope that Jon Rhees will address this issue and take appropriate measures.

For the being, nappysolo's suggestion is the only workaround I've found.
Thanks nappysolo!
Frank