Windows Vista Freezing & Blue Screen

All,

I'm getting tired of fixing Vista... I don't know whether this is a hardware compatability issue or if it's a Vista software issue but hopefully someone can help...

I seem to be getting a blue screen error or the computer freezes on a random basis. It has to be finding something that happens within the system that I don't know about. I've tried everything. My motherboard is ASUS A8N32-SLI DELUX with an Athalon AMD 64 X2 processor chip. The only piece of hardware that I have found a Vista driver for is my Video card. Everything else is still behind in the times.

The blue screen error only stays up for a second before it resets the computer without any input on my part so I have no time to read it and see what it is saying..........

Has anyone else had this problem and got it fixed??? Or am I gonna have to wait for drivers and a service pack from microsoft to try fixing the problem?

 

hi

I'm afraid the only thing you can do is waiting for the new drivers for your hardware...

As i know, many hardware industry has leased their drivers for vista, maybe you can take a shoot on their website.

 

Thank you so far for being willing to help me!!

You wouldn't believe how many times I had to restart the computer due to it freezing on me just to get the programs loaded and ran to get this dump... The only way I can get more than 2 minutes out of the computer is by running safe mode..... NOT something I bought a $200 O.S. for.

I seem to get 2 different blue screens when it crashes on me.. The codes that they give are the 2 following:

1)
IRQL_NOT_LESS_OR_EQUAL
***STOP: 0x0000000A (0x00000002, 0x00000001, 0x81FA4E79)

2)
***STOP: 0x0000008E (0xC0000005, 0x81E197E9, 0x8A6994BC, 0x0000000)

What I got out of it (but am probably wrong so just skip this part) is that my lack of drivers is what is screwing it up???

Hopefully they help but just in case... here is one of the dumps that was logged....

THE FOLLOWING TEXT IS FROM MY DEBUGGING DUMP THAT WAS CREATED.
HAVE FUN!!!!
_______________________________________________________________


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


Loading Dump File [C:\Windows\Minidump\Mini050807-07.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11db0
Debug session time: Tue May 8 21:55:16.812 2007 (GMT-5)
System Uptime: 0 days 0:00:15.406
Loading Kernel Symbols
............................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81e197e9, 8a6994bc, 0}

Probably caused by : hardware ( nt!PsReferencePrimaryToken+92 )

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

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 81e197e9, The address that the exception occurred at
Arg3: 8a6994bc, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


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

FAULTING_IP:
nt!PsReferencePrimaryToken+92
81e197e9 085f5e or byte ptr [edi+5Eh],bl

TRAP_FRAME: 8a6994bc -- (.trap ffffffff8a6994bc)
.trap ffffffff8a6994bc
ErrCode = 00000002
eax=5359532a ebx=8a463e70 ecx=00000005 edx=8d639db4 esi=8a55c3dc edi=8a463d90
eip=81e197e9 esp=8a699530 ebp=8a69953c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!PsReferencePrimaryToken+0x92:
81e197e9 085f5e or byte ptr [edi+5Eh],bl ds:0023:8a463dee=00
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 7

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: smss.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!PsReferencePrimaryToken+92
81e197e9 085f5e or byte ptr [edi+5Eh],bl

LAST_CONTROL_TRANSFER: from 81e4927e to 81e197e9

STACK_TEXT:
8a69953c 81e4927e 8d639db0 8a55c3c0 8a55c478 nt!PsReferencePrimaryToken+0x92
8a699554 81e445db 8a569328 8a463d90 8a55c3dc nt!SeCaptureSubjectContextEx+0x3e
8a699578 81e44573 8a569328 8a463d90 8a55c3c0 nt!SeCreateAccessStateEx+0x5a
8a699598 81dec652 8a55c3c0 8a55c478 00000009 nt!SeCreateAccessState+0x27
8a6995e0 81d394a9 8a69976c 84183a90 00000000 nt!ObOpenObjectByName+0xd5
8a6996ac 81d39268 8a69998c 00000009 8a69976c nt!CmOpenKey+0x1b1
8a6996d0 81c8c96a 8a69998c 00000009 8a69976c nt!NtOpenKey+0x39
8a6996d0 81c7ea09 8a69998c 00000009 8a69976c nt!KiFastCallEntry+0x12a
8a699754 81e293f2 8a69998c 00000009 8a69976c nt!ZwOpenKey+0x11
8a699794 81e22fdf 8a69998c 8a692390 8a463d90 nt!RtlOpenImageFileOptionsKey+0x92
8a6998d0 81e22a5c 8a463d90 00000001 00000000 nt!PspAllocateProcess+0x265
8a699d30 81c8c96a 0023f63c 0023f640 02000000 nt!NtCreateUserProcess+0x4e3
8a699d30 76f40f34 0023f63c 0023f640 02000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0023f548 00000000 00000000 00000000 00000000 0x76f40f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PsReferencePrimaryToken+92
81e197e9 085f5e or byte ptr [edi+5Eh],bl

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!PsReferencePrimaryToken+92

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

eax=5359532a ebx=8a463e70 ecx=00000005 edx=8d639db4 esi=8a55c3dc edi=8a463d90
eip=81e197e9 esp=8a699530 ebp=8a69953c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!PsReferencePrimaryToken+0x92:
81e197e9 085f5e or byte ptr [edi+5Eh],bl ds:0023:8a463dee=00
ChildEBP RetAddr Args to Child
8a69953c 81e4927e 8d639db0 8a55c3c0 8a55c478 nt!PsReferencePrimaryToken+0x92
8a699554 81e445db 8a569328 8a463d90 8a55c3dc nt!SeCaptureSubjectContextEx+0x3e
8a699578 81e44573 8a569328 8a463d90 8a55c3c0 nt!SeCreateAccessStateEx+0x5a
8a699598 81dec652 8a55c3c0 8a55c478 00000009 nt!SeCreateAccessState+0x27
8a6995e0 81d394a9 8a69976c 84183a90 00000000 nt!ObOpenObjectByName+0xd5
8a6996ac 81d39268 8a69998c 00000009 8a69976c nt!CmOpenKey+0x1b1
8a6996d0 81c8c96a 8a69998c 00000009 8a69976c nt!NtOpenKey+0x39
8a6996d0 81c7ea09 8a69998c 00000009 8a69976c nt!KiFastCallEntry+0x12a (FPO: [0,3] TrapFrame @ 8a6996e4)
8a699754 81e293f2 8a69998c 00000009 8a69976c nt!ZwOpenKey+0x11 (FPO: [3,0,0])
8a699794 81e22fdf 8a69998c 8a692390 8a463d90 nt!RtlOpenImageFileOptionsKey+0x92
8a6998d0 81e22a5c 8a463d90 00000001 00000000 nt!PspAllocateProcess+0x265
8a699d30 81c8c96a 0023f63c 0023f640 02000000 nt!NtCreateUserProcess+0x4e3
8a699d30 76f40f34 0023f63c 0023f640 02000000 nt!KiFastCallEntry+0x12a (FPO: [0,3] TrapFrame @ 8a699d64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
0023f548 00000000 00000000 00000000 00000000 0x76f40f34
start end module name
80200000 80202880 SiWinAcc SiWinAcc.sys Mon Nov 01 14:21:31 2004 (41868CBB)
80203000 8020a000 pciide pciide.sys Thu Nov 02 03:51:35 2006 (4549B197)
8020a000 80219000 volmgr volmgr.sys Thu Nov 02 03:51:44 2006 (4549B1A0)
80219000 80221000 msisadrv msisadrv.sys Thu Nov 02 03:35:08 2006 (4549ADBC)
80221000 8022a000 WMILIB WMILIB.SYS Thu Nov 02 03:54:53 2006 (4549B25D)
8022a000 8026d000 acpi acpi.sys Thu Nov 02 03:35:03 2006 (4549ADB7)
8026d000 8027a000 WDFLDR WDFLDR.SYS Thu Nov 02 03:54:05 2006 (4549B22D)
8027a000 802b5000 CLFS CLFS.SYS Thu Nov 02 03:30:52 2006 (4549ACBC)
802b5000 802bd000 BOOTVID BOOTVID.dll Thu Nov 02 04:39:29 2006 (4549BCD1)
802bd000 802c6000 PSHED PSHED.dll Thu Nov 02 04:42:51 2006 (4549BD9B)
802c6000 802ce000 kdcom kdcom.dll Thu Nov 02 04:42:20 2006 (4549BD7C)
80405000 80406580 SiRemFil SiRemFil.sys Wed Oct 18 17:20:04 2006 (4536A894)
80407000 8040f000 spldr spldr.sys Wed Oct 25 17:40:44 2006 (453FE7EC)
8040f000 80417000 atapi atapi.sys Thu Nov 02 03:51:34 2006 (4549B196)
80417000 80461000 volmgrx volmgrx.sys Thu Nov 02 03:51:54 2006 (4549B1AA)
80461000 8046f000 PCIIDEX PCIIDEX.SYS Thu Nov 02 03:51:34 2006 (4549B196)
8046f000 8047f000 mountmgr mountmgr.sys Thu Nov 02 03:51:06 2006 (4549B17A)
8047f000 804a4000 pci pci.sys Thu Nov 02 03:35:13 2006 (4549ADC1)
804a4000 8051f000 Wdf01000 Wdf01000.sys Thu Nov 02 03:54:18 2006 (4549B23A)
8051f000 80600000 CI CI.dll Thu Nov 02 04:42:45 2006 (4549BD95)
80606000 80615000 partmgr partmgr.sys Thu Nov 02 03:51:47 2006 (4549B1A3)
80615000 80640000 msrpc msrpc.sys Thu Nov 02 03:50:16 2006 (4549B148)
80640000 80744000 ndis ndis.sys Thu Nov 02 03:57:33 2006 (4549B2FD)
80744000 80754000 fileinfo fileinfo.sys Thu Nov 02 03:36:47 2006 (4549AE1F)
80754000 80785000 fltmgr fltmgr.sys Thu Nov 02 03:30:58 2006 (4549ACC2)
80785000 807ab000 SCSIPORT SCSIPORT.SYS Thu Nov 02 03:51:38 2006 (4549B19A)
807ab000 807e2000 Si3132r5 Si3132r5.sys Mon Nov 27 17:11:59 2006 (456B70BF)
807e2000 80800000 ataport ataport.SYS Thu Nov 02 03:51:34 2006 (4549B196)
81a07000 81a10000 crcdisk crcdisk.sys Thu Nov 02 03:52:27 2006 (4549B1CB)
81a10000 81a1f000 mup mup.sys Thu Nov 02 03:31:04 2006 (4549ACC8)
81a1f000 81a55000 volsnap volsnap.sys Thu Nov 02 03:52:11 2006 (4549B1BB)
81a55000 81abf000 ksecdd ksecdd.sys Thu Nov 02 03:43:45 2006 (4549AFC1)
81abf000 81bc7000 Ntfs Ntfs.sys Thu Nov 02 03:31:39 2006 (4549ACEB)
81bc7000 81c00000 NETIO NETIO.SYS Thu Nov 02 03:58:01 2006 (4549B319)
81c00000 81fa1000 nt ntkrpamp.exe Thu Nov 02 03:36:16 2006 (4549AE00)
81fa1000 81fd5000 hal halmacpi.dll Thu Nov 02 03:30:18 2006 (4549AC9A)
82405000 82414000 amdk8 amdk8.sys Thu Nov 02 03:30:18 2006 (4549AC9A)
825a9000 825ca000 CLASSPNP CLASSPNP.SYS Thu Nov 02 03:51:34 2006 (4549B196)
825ca000 825db000 disk disk.sys Thu Nov 02 03:51:40 2006 (4549B19C)
825db000 82600000 ecache ecache.sys Thu Nov 02 03:52:42 2006 (4549B1DA)
82617000 82625000 usbehci usbehci.sys Thu Nov 02 03:55:04 2006 (4549B268)
82637000 82638420 ASACPI ASACPI.sys Thu Aug 12 21:52:52 2004 (411C2D04)
8263f000 82640700 USBD USBD.SYS Thu Nov 02 03:55:00 2006 (4549B264)
82641000 82642380 swenum swenum.sys Thu Nov 02 03:51:15 2006 (4549B183)
82730000 82738000 dump_atapi dump_atapi.sys Thu Nov 02 03:51:34 2006 (4549B196)
82760000 82768000 RDPCDD RDPCDD.sys Thu Nov 02 04:02:01 2006 (4549B409)
82790000 82798000 rdpencdd rdpencdd.sys Thu Nov 02 04:02:01 2006 (4549B409)
8363f000 83646000 Null Null.SYS Thu Nov 02 03:51:05 2006 (4549B179)
83646000 8364d000 Beep Beep.SYS Thu Nov 02 03:51:03 2006 (4549B177)
83700000 83710000 NDProxy NDProxy.SYS Thu Nov 02 03:58:08 2006 (4549B320)
837c0000 837cf280 ohci1394 ohci1394.sys Thu Nov 02 03:55:16 2006 (4549B274)
87804000 87817000 i8042prt i8042prt.sys Thu Nov 02 03:51:12 2006 (4549B180)
87817000 87822000 fdc fdc.sys Thu Nov 02 03:51:33 2006 (4549B195)
87822000 87855000 yk60x86 yk60x86.sys Mon Oct 02 02:05:41 2006 (4520BA45)
87855000 87860000 tunnel tunnel.sys Thu Nov 02 03:57:29 2006 (4549B2F9)
87860000 8786d000 watchdog watchdog.sys Thu Nov 02 03:37:44 2006 (4549AE58)
87877000 87882000 dump_dumpata dump_dumpata.sys Thu Nov 02 03:51:34 2006 (4549B196)
878af000 878ba000 kbdclass kbdclass.sys Thu Nov 02 03:51:09 2006 (4549B17D)
878ba000 878d2000 parport parport.sys Thu Nov 02 03:51:29 2006 (4549B191)
8790c000 87915000 Fs_Rec Fs_Rec.SYS Thu Nov 02 03:30:47 2006 (4549ACB7)
87915000 8791e000 rasacd rasacd.sys Thu Nov 02 03:58:13 2006 (4549B325)
87939000 87942000 tunmp tunmp.sys Thu Nov 02 03:57:23 2006 (4549B2F3)
879f5000 87a00000 mouclass mouclass.sys Thu Nov 02 03:51:09 2006 (4549B17D)
88205000 88210000 TDI TDI.SYS Thu Nov 02 03:58:46 2006 (4549B346)
88210000 8823b000 msiscsi msiscsi.sys Thu Nov 02 03:52:40 2006 (4549B1D8)
8823b000 88248080 1394BUS 1394BUS.SYS Thu Nov 02 03:55:12 2006 (4549B270)
88249000 88254200 fetnd5 fetnd5.sys Mon Feb 13 23:55:24 2006 (43F170CC)
88255000 8826d000 cdrom cdrom.sys Thu Nov 02 03:51:44 2006 (4549B1A0)
8826d000 882aa000 USBPORT USBPORT.SYS Thu Nov 02 03:55:09 2006 (4549B26D)
882aa000 882c4000 serial serial.sys Thu Nov 02 03:51:29 2006 (4549B191)
882c4000 88360000 dxgkrnl dxgkrnl.sys Thu Nov 02 03:38:46 2006 (4549AE96)
8836a000 88374000 serenum serenum.sys Thu Nov 02 03:51:25 2006 (4549B18D)
88374000 8837e000 usbohci usbohci.sys Thu Nov 02 03:55:05 2006 (4549B269)
8837e000 88388000 mssmbios mssmbios.sys Thu Nov 02 03:35:13 2006 (4549ADC1)
88388000 88392000 flpydisk flpydisk.sys Thu Nov 02 03:51:32 2006 (4549B194)
88392000 8839c000 nsiproxy nsiproxy.sys Thu Nov 02 03:57:30 2006 (4549B2FA)
883a6000 883b0000 Dxapi Dxapi.sys Thu Nov 02 03:38:17 2006 (4549AE79)
88808000 8881f000 rasl2tp rasl2tp.sys Thu Nov 02 03:58:13 2006 (4549B325)
8882c000 88839000 umbus umbus.sys Thu Nov 02 03:55:24 2006 (4549B27C)
88839000 88846000 crashdmp crashdmp.sys Thu Nov 02 03:51:36 2006 (4549B198)
888ef000 88fffd80 nvlddmkm nvlddmkm.sys Sat Feb 10 13:18:53 2007 (45CE1A9D)
89031000 8905b000 ks ks.sys Thu Nov 02 03:51:18 2006 (4549B186)
8905b000 8906a000 termdd termdd.sys Thu Nov 02 04:02:00 2006 (4549B408)
8906a000 89075000 Msfs Msfs.SYS Thu Nov 02 03:30:56 2006 (4549ACC0)
89075000 89088000 raspptp raspptp.sys Thu Nov 02 03:58:14 2006 (4549B326)
89088000 89097000 raspppoe raspppoe.sys Thu Nov 02 03:58:12 2006 (4549B324)
89097000 890ba000 ndiswan ndiswan.sys Thu Nov 02 03:58:13 2006 (4549B325)
890ba000 890c5000 ndistapi ndistapi.sys Thu Nov 02 03:58:07 2006 (4549B31F)
890c5000 89105000 storport storport.sys Thu Nov 02 03:51:45 2006 (4549B1A1)
89105000 891ff480 nvmfdx32 nvmfdx32.sys Mon Jan 15 18:50:38 2007 (45AC215E)
89200000 8920c000 vga vga.sys Thu Nov 02 03:53:56 2006 (4549B224)
89364000 89398000 usbhub usbhub.sys Thu Nov 02 03:55:20 2006 (4549B278)
89e05000 89e1e000 fwpkclnt fwpkclnt.sys Thu Nov 02 03:57:26 2006 (4549B2F6)
89e1e000 89e2c000 Npfs Npfs.SYS Thu Nov 02 03:30:57 2006 (4549ACC1)
89e4c000 89e6d000 VIDEOPRT VIDEOPRT.SYS Thu Nov 02 03:54:07 2006 (4549B22F)
8a016000 8a029000 wanarp wanarp.sys Thu Nov 02 03:58:13 2006 (4549B325)
8a029000 8a037000 netbios netbios.sys Thu Nov 02 03:57:26 2006 (4549B2F6)
8a037000 8a04d000 pacer pacer.sys Thu Nov 02 03:57:33 2006 (4549B2FD)
8a04d000 8a07f000 netbt netbt.sys Thu Nov 02 03:57:18 2006 (4549B2EE)
8a07f000 8a0c6000 afd afd.sys Thu Nov 02 03:58:41 2006 (4549B341)
8a106000 8a11a000 smb smb.sys Thu Nov 02 03:57:10 2006 (4549B2E6)
8a11a000 8a12f000 tdx tdx.sys Thu Nov 02 03:57:34 2006 (4549B2FE)
8a12f000 8a200000 tcpip tcpip.sys Thu Nov 02 03:58:31 2006 (4549B337)
8a610000 8a638000 fastfat fastfat.SYS Thu Nov 02 03:30:49 2006 (4549ACB9)
8a786000 8a798000 USBSTOR USBSTOR.SYS Thu Nov 02 03:55:05 2006 (4549B269)
8a798000 8a7ae000 cdfs cdfs.sys Thu Nov 02 03:30:50 2006 (4549ACBA)
8a7ae000 8a7c5000 dfsc dfsc.sys Thu Nov 02 03:31:04 2006 (4549ACC8)
8a7c5000 8a800000 rdbss rdbss.sys Thu Nov 02 03:31:24 2006 (4549ACDC)
8d800000 8d9ff000 win32k win32k.sys Wed Feb 14 20:57:33 2007 (45D3CC1D)

Unloaded modules:
878d2000 878df000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
87877000 87882000 dump_ataport
Timestamp: unavailable (00000000)
Checksum: 00000000
82770000 82778000 dump_atapi.s
Timestamp: unavailable (00000000)
Checksum: 00000000

 

Your chipset drivers should be here:
http://www.nvidia.com/content/drivers/drivers.asp
Platform/nForce drivers -> nForce4 series AMD

Check the listing for Network Adapters in Device Manager, I would expect that they should be listed as "NVIDIA nForce Controllers ".

Did you get the Realtek audio drivers from your other thread? You reminded me that I did not have mine installed, I downloaded them and now my sound is working. (BTW, I have an Abit system).

Once you have the chipset drivers installed, if the system does not settle down, try uninstalling and reinstalling the graphics drivers (there should be an uninstaller in Control Panel -> Programs).

Look through Device Manager if there are listings that may require specific drivers. If you have any odd hardware attached, remove it or disable it until you find the source of the errors (for example, I could see that my LAN drivers needed to be installed and now I have the correct audio drivers).

Matt

 

Matt,

I downloaded the nForce drivers.

I got on Realtek's website and searced for a driver for my ALC850 sound card but none available... It only has "Datasheets" and "Reference Designs" available for download... Is there another place I could go or do you know where my driver would be?

The drivers that came with the motherboard on the support disk cannot run. When I load the disk and try running it it says that the disk is not compatable with Vista... So, I go to ASUS website and see if they have the drivers for Vista posted and come up with nothing.

In device manager there are 2 items in the "Other Devices" that both have triangles with exclamations in them they are:
1)Multimedia Audio Controller (assuming thats my realtek that I can't figure out)
2)Unknown Device.. could this be my ethernet card?

 

It's a little obscure. Get the "High Definition Audio Codecs ". It will put a Realtek HD Audio Manager in the System Tray, use that to test the speakers. If you are testing with one set of speakers, connect them to the lime green socket.
http://www.realtek.com.tw/downloads...=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

Once you have installed the nForce and audio drivers, check in Device Manager again.

Matt

 

I downloaded the High Def audio driver and then went to device manager... Still had the exclamation next to it saying it was not located... So, I went in manually through device manager and loaded the driver that I supposedly loaded when I downloaded the driver from the website and It then moved the item from the "other devices" dropdown to the Audio dropdown but still doesn't seem to have done anything to help out... Vista still says that no device output is attached. I checked my speakers and they are plug and play... they work when I plug them into a MP3 player so I know they are good. I went to the store and got a new Ethernet card that had a driver for vista thinking that that would help out some, but I still get blue screen or it freezes completely... I'm kinda stumped

Would the fact that the ASUS motherboard I am using doesn't have any drivers for its on board devices for Vista yet make Vista do this? Everything else works with it. My video card works fine and I downloaded a driver for my optical wireless mouse through logitech and it works fine.

Should I get a Vista ready soundcard and plug it into a PCI slot and see if that fixes the problem?

The "Unknown Device" is still on my device manager under "Other Devices" with an exclamation next to it. Says it is plugged into a PCI slot but the only thing I have plugged into a PCI slot is my Ethernet card and that has a Vista driver installed... When I disabled the "Unkown Device" nothing happened... Internet still worked and nothing was noticeable on the surface.

 

I am having connection problems at the moment.

I looked at the Asus drivers for your machine. The ethernet/LAN/network drivers are described as Marvell Yukon. So try those listed as:
"Product Category = PC Connectivity
Product Family = Yukon
Platform = Vista x86 "
(if you are running 64bit Vista, use Platform = Vista x64)
at Marvell
http://www.marvell.com/drivers/search.do
[Edit: look at reinstalling the audio drivers below first]

Your Realtek audio is not described as "High Definition" like mine.
Ahhh!...I see yours is described as "Realtek ALC850 AC'97 Driver ", uninstall those HD codecs and use the AC'97 version.
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=8&PFid=14&Level=3&Conn=2
(software)

Matt

 

Thank You so much for your help thus far!

I am sitting at work, so I can't perform the operations that you suggested yet matt. I did however search for the drivers you have listed and am confused as to which Marvel one to install...

There are 3 different choices that come up with the search without using keywords to narrow it down... Do I install:
Yukon Windows Vista
Miniport Windows Installer
VCT Installer

I could give it a shot and say that the Yukon is the one I want, but I am not sure and don't want to ***** things up any more than they already are...

I found the installer for the sound card you mentioned and that will be easy enough to install.

Thank you again for looking into all that for me. Guess I'm just not "Vista ready "

 

Don't worry too much about the Marvell Yukon drivers until you install those AC'97 drivers. Since the "unknown device" switched over to the Audio Controllers section in Device Manager, it is very likely to be the Realtek audio.

If the audio starts working with those AC'97 drivers, test your system for a while and see if it is stable.

Check under the heading of Network Adapters in Device Manager. It all depends on the description of the device/s. So if it states something like "Standard Network Adapter ", the correct drivers aren't installed. If it states a manufacturer like Marvell (Yukon) or maybe NVIDIA nForce, Windows has probably selected the correct drivers. The drivers that I think are the ones you might need are v9.16.2.3 "Yukon Windows Vista... ". I am a little confused myself. Maybe we can investigate further if you seem to need them. If you run the wrong installation, Windows will just ignore those drivers or complain about them apparently being incorrect.

Matt

 

Thank You for all you help...

I downloaded all the drivers and there still is 1 unknown device in the device manager... but I can't figure out what it is. I thought I checked every piece of hardware in the computer and downloaded a driver if possible, but apparently there is somthing I am missing.

I dissabled the device and nothing happens... no errors, no programs malfunctioning... dunno.

I was still getting blue screen errors after the drivers were installed, so I read through my motherboard manual again and discovered that I installed one of my RAM chips in a wrong slot... Apparently (I didn't know this) if your only using 2 chips, you MUST put them in specific slots or it will crash.....

I've had the computer running in normal mode for over an hour now and no errors, no freezing.... I think I am good to go...

I would like to however, find out what that device is that is not recognized. Any suggestions??

 

You don't say if the audio is working now. If not, it may it may still be part of the audio drivers.

You can right-click on the device in Device Manager and click Uninstall. It is not functioning now, so you may as well reinstall it. Since you have updated most of the main drivers, when Windows detects it at restart, it can use the updated driver information to possibly identify it correctly.

The other driver I see listed at Asus is the

If I don't use RAID I don't bother installing the RAID drivers, I just leave them with an error.

If the system seems to be running well, don't put much effort into identifying the unknown hardware, it may well be something you won't need. Once Asus have started supplying Vista drivers for your model, you should be able to get that final item identified. If you think you need to identify it look for drivers or information at Silicon Image.

Matt

 

Hi,

Your Unknown Device relates to your Gameport on the Sound Card. Most people do not use this now as they use USB, but even though you might not have anything plugged in it it is recognised by the system.

You cannot get a driver for this from anywhere and MS do not support it and are not doing anything for it either. To get round this problem you need to select that Unknown Device then select add or update driver, then select Browse my Computer for Driver. If i remember correctly i think you have to also select Show All, then locate Creative Ltd (something like that); once selected you will then see a single entry on the right called Unsupported Device, select this and proceed...once this is installed your remaining problem will disappear.

I had the same problem and it worked for me but my card was an Audigy, if your card is different then you can but only try it. If it doesnt work then maybe there is something similar in the listing for your make, if not then at least you can contact the manufacturer to try and get them to help you.

EDIT: I read another of your posts and have just realised you are using a built-in MB sound....in this case, if you do have a gameport only attached then it is that is still the Unknown Device.

 

Sound works GREAT Matt. I uninstalled the HD driver and then installed the 97driver and it worked like a charm!

I do have a game controller device and another device that I think is for cameras... at least thats what it looks like the plug is for. Everything works fine as is, so I'm not going to mess with it until I try running something and it comes up with errors.

Thank you for all your help guys!!!!! Everything helped out lots!!

I am going to try to uninstall the device like you suggested matt. I tried searching for the driver Zykan and it came up with nothing, so I'm not worrying about it.

Thanks again for everything guys!