Web Development

Ask something
Question Locked

Windows Vista BSOD issues

0 helpful
11 replies

by coreyx64

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

hello,

i have built a computer to use as a security DVR. it uses a gigabyte EG45M-UD2H mobo with C2D e7600 3.06ghz. 4GB gskill ram. 80gb WD hdd and 2TB hdd for video storage.

everything went flawlessly with it. the new board worked, hdds were fine, so was the PSU, etc.

my dvr card is made my avermedia.
AverMedia, claiming that their DVR card, 6480 express works with both XP and vista, is in fact false. heres why. also im mad cuz i paid for a brand new copy of xp pro and now it doesnt work with the card. owell. more for me--im not paying for this system...its for someone else.

anyway, the CD for the card and the website itself claims this card works with both XP and vista. FAIL. the company only included one (1) driver on the CD and on the website. it is written based on the x86 version of the Vista WDM, which means:

a) doesnt work on xp at all
b) cant take advtg. of 64 bit intel C2D capabilities with a 64 bit version of vista

so i had an oem vista 32 bit disc laying around so i popped it in, setup, yada yada. once booted to the desktop, i made sure all drivers were loaded and installed gigabyte chipset drivers from intel. piece of cake---and no problems.

now here is where there is a hang up. when i tried this in XP, the driver would load, but XP would say "an error occured installing the device. it may not work properly..." so i knew it was a driver issue. turns out it was a vista driver. so scrapped xp and went to vista. *sighs*

every thing works out fine, driver is successfuly installed in vista. YAY! problem solved!?? NOPE.

the software will load. before you get a chance to do anything, it loads the cameras on screeen and the spinning circle cursor freezes and the whole machine locks up, forcing a hard reset. the first time i got a BSOD. couldnt read it really, but essentially it meant hardware problems. ill "re-fail" the system so i can read it again if i need to. upon next boot i get the windows recoverd from unexpected shutdown. and some other details with it. if you need any other info or error message codes let me know.

Thanks,

- Corey -

11 replies

by rob miners

to work with.

Press the WinKey + Pause
Click Advanced and under Startup and Recovery select Settings.
Uncheck Automatically restart.
Click on the dropdown arrow under Write debugging information.
Select Small memory dump (64 KB) and the output is %SystemRoot%\Minidump.
Restart the PC normally as this will allow the System to Blue Screen and create the Minidump.

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

How to read the small memory dump files that Windows creates for debugging

http://support.microsoft.com/kb/315263

To download and install the Windows debugging tools, visit the following Microsoft Web site:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and browse to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
FAULTING_THREAD: 864f6a98

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

STACK_TEXT:
f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

FOLLOWUP_IP:
sgiul50!DrvBitBlt+585
bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: sgiul50!DrvBitBlt+585

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

by coreyx64

and get back to you when i do it. i had to RMA the HDD for it since the sata port's plastic cracked and no longer holds the connector.

Thanks for the help.

by computechdan

good luck tryin to rma on basis of broken plastic, often it's rejected as end user abuse

jacky, nice tid bit on the win + pause
those two jus happen to reside next to each other on my laptop... i'll be usin that one

by coreyx64

on the sata ports the "L" shaped plastic is needed to lock the cables on. SNAP! it was clearly broken, and some of the pins were bent also. i shud get the new one back at the end of this week.

- Corey -

by coreyx64

and i got the "approval" or "cofirmation" email from the vendor. i understand what your saying though.

by coreyx64

if the manufacturer on supplied ONE (1) driver INF file with the capture card, how can they say it runs on XP and vista when those 2 OSs use 2 completely different WDMs? i checked the site for updates (AverMedia) and still only 1 driver. it would have been nice to use this with xp but i guess the driver that is included is only written in vista WDM... :(

by coreyx64

It's a dvr card. It uses averDigi software version 7.5.

by coreyx64

it was RMA'd and i received a replacement. works for me.

This discussion is closed to new replies.