[Leelad00]

that would be a waste of your money, i couldnt accept that

anyway here is the screenshot you requested :

[Advertisements]

Another option.
Take the soundcard out and try it in another system
If it loads and works then we will continue.
If not then the card is bad.
If I have read eveyrhting right this is a addon card and not onboard.
If that is so there should be a model number on the card along with the make of the card.
Can you get that info please for us?

[rshaffer61]

Another option.
Take the soundcard out and try it in another system
If it loads and works then we will continue.
If not then the card is bad.
If I have read eveyrhting right this is a addon card and not onboard.
If that is so there should be a model number on the card along with the make of the card.
Can you get that info please for us?

[Leelad00]

ok after taking the back off my computer i have found that:

the sound card is built in, i cant take it out.. i think if it is the sound card.
the number etc for the card is :

ITE
IT8705AF
0527-GXS
N122PE

I did a search for just the IT8705af part, and it came up in google for sound card drivers, so i can presume that that is the sound card. if so it is fixed in. non removable.

i also saw a card that had SiS written on it.. i suppose that is the chipset? i got the number from that anyway..:
SiS 964

[rshaffer61]

OK then we need to look at another option.

Please boot system and go into the BIOS
Normally this is done at the first post screen and tapping the DEL key.
Once in the bios look for either Advanced or Onboard Peripherals
Once there look for ONboard Audio and make sure it is enabled.
When you have finished make sure to Save and Exit
System will reboot and then see if the issue resolves itself.

[Leelad00]

already done this, however i tried it again, and yes it was already enabled.

however on my bios it is described as BIOS > Integrated Peripherals > realtek AC '97 Audio - Enabled.

[rshaffer61]

Aha the mystery of where the AC97 is coming from.
Now the problem is why you cannot install the driver no matter where it comes form.
Other then this is the system running correctly?
Also what is the other entry that is showing in Device Manager?
Microsoft Life Cam
Is there a camera hooked to the system through a USB post?

[Leelad00]

i was hoping you could tell me and yes that is a webcam i havent installed properly yet. ill unplug it.

EDIT - yes the system is running fine elsewhere.

Edited by Leelad00, 08 September 2009 - 08:39 AM.

[rshaffer61]

Then try this:
Boot into safe mode and then go to Device Manager
See if the Audio controller is showing there.

If so and it is still not working(Yellow exclamation mark) then right click on it and uninstall it.
Then reboot back into Normal mode and then see if windows can install it on it's own.
Post back with your results.

[Leelad00]

still the same result. uininstalled in safe mode, then rebooted normally and it restarted my computer half way through installation again.. :/

[rshaffer61]

however on my bios it is described as BIOS > Integrated Peripherals > realtek AC '97 Audio - Enabled.

Was there any other audio other then the above?
If you clicked on this did it open to give you any other options?

[Leelad00]

no that was the only audio device thing, and when i clicked on it it was either enable or disable.

[rshaffer61]

At this point it looks like the the only option is the driver itself.
Lets try one more option and see if we can get rid of any residual driver and try this completely fresh.
Download Drive Sweeper and install it.
Now boot back to Safe Mode and start Drive Sweeper
Any entries for Realtek or SIS Audio have it clean them.
Then reboot back into normal mode and try the official AC97 driver I had you download earlier.
Let us know if this works.

[Leelad00]

nope, same result : the installation of the driver causes the computer to restart itself and then say it has recovered from a serious error

[rshaffer61]

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

[Leelad00]

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Thu 10/09/2009 16:00:40 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF273646D, 0xF40AAA74, 0xF40AA770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/09/2009 15:44:33 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF29A846D, 0xF8AB5A74, 0xF8AB5770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/09/2009 15:38:52 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF28DB46D, 0xF8AB9A74, 0xF8AB9770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/09/2009 15:22:17 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF420446D, 0xF8AADA54, 0xF8AAD750)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/09/2009 15:20:15 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF494D46D, 0xF8AB9A54, 0xF8AB9750)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/09/2009 15:18:40 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF49ED46D, 0xF8AB1A54, 0xF8AB1750)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/09/2009 12:14:45 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF60A53C6, 0xF89A1A5C, 0xF89A175C)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 08/09/2009 21:04:01 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF226846D, 0xF8AC1A74, 0xF8AC1770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 08/09/2009 13:32:10 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF0C1146D, 0xF8AB9A74, 0xF8AB9770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 08/09/2009 00:08:52 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF26B446D, 0xF8AC1A74, 0xF8AC1770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 07/09/2009 23:58:59 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF248B46D, 0xF8ABDA74, 0xF8ABD770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 07/09/2009 22:33:54 your computer crashed
This was likely caused by the following module: portcls.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF284446D, 0xF8AB5A74, 0xF8AB5770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


there you go mate