Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screens of Death everywhere.


  • Please log in to reply
17 replies to this topic

#1 Please Help Us

Please Help Us

  • Members
  • 156 posts
  • OFFLINE
  •  
  • Local time:02:49 AM

Posted 31 December 2009 - 02:45 AM

Well recently I reformatted my computer, replaced the memory, and wanted to start fresh with it. However, recently I've been getting blue screens of death from just about everything. Games, surfing the web, hell just leaving it on the desktop screen with nothing else on can cause it to crash. However, I've been taking notes of the blue screens and I think I have a rough idea of what might be causing it and all the errors so far. Anyway here's a list of the errors and what I think is causing them.

0x000000D1 (0x0654F680 0X00000002 0X00000000 0XF653ADED)
ALCXWDM.SYS Address F653ADEB base at F65F7000 datestamp 42adc0cd
Its a part of the Realtek AC97 audio program, which doesn't even work properly on my computer in the first place. :thumbsup:

0x000000D1 ( 0x00170014 0x00000002 0x00000000 0xf73c76d4)
Ndis.sys F73C76D4 base at 73A4000 datestamp at 48023d03
I seem to have two copies of this file on my computer, however all I know it has to do something with my modem or my internet service something like that. Ignorance man go :trumpet:

0x000000C5 C0X70704452 0X00000002 0X00000001 0X8054B16A
Microsoft said this error was caused by my Nvidia 5800 (At least I think that's what it is off the top of my head, sorry a bit slow today like every day :flowers: ) which I updated recently so that could be one of the culprits.

So anyway those are the only types of errors I've seen so far, I haven't noticed a different or a new one aside from those three. Yes they're all stop errors as well, so I'm really kind of stuck. Anyway, if anyone here could provide some help that would be great! Anyway, thank you all for your wonderful time and help here already, and hopefully we'll get this out of the way quickly and easily.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 AM

Posted 01 January 2010 - 11:26 AM

http://www.aumha.org/a/stop.htm

You can look up general descriptions and suggestions for each error, using the last two characters from the first string of the error message.

Appears that you have a bunch of damaged/wrong drivers...or you might start thinking "CMOS battery" or "RAM" or "PSU".

Louis

#3 Please Help Us

Please Help Us
  • Topic Starter

  • Members
  • 156 posts
  • OFFLINE
  •  
  • Local time:02:49 AM

Posted 01 January 2010 - 11:32 AM

Well I've actually replaced both the cmos battery and the RAM in the last week or so, so hopefully they aren't the case, but I'll make sure to check. Also the PSU has never given me trouble before as well, however, I'll make sure to check that as well. I'll take a look at the site right now and see what if suggests, if I have any more questions I can post them here correct or would it be better to make a new topic?

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 AM

Posted 01 January 2010 - 12:02 PM

This is your topic :thumbsup:...no need to create a new one.

This topic may be moved to the XP forum, but probably not. Drivers are hardware issues and XP issues, so posts should be able to be in either.

Louis

#5 Please Help Us

Please Help Us
  • Topic Starter

  • Members
  • 156 posts
  • OFFLINE
  •  
  • Local time:02:49 AM

Posted 01 January 2010 - 12:05 PM

Alright then thank you sir, if it has to be moved to XP I have no problem with that, whatever goes is whatever goes. :thumbsup:

Alright, so I found out that Nivida cards are a real common issue for causing C5 issues, I'm still looking for a solid "English" solution but I was wondering if you might know anything of the issue. Thank you once again for even answer though, so please take your time no need to rush.

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 AM

Posted 01 January 2010 - 01:29 PM

The way that I deal with STOP errors is a process of elimination.

First, I take note of the Aumha general description and guidance.

Correct that...first thing is to determine if I can boot into XP or not. If not, right away I mentally prepare for a clean install.

If I can boot into XP and then read up...I look for .dmp files which are generated after a STOP error. These files tend to be most helpful in attempting to figure out what is going wrong.

Then...Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

FWIW: There are all sorts of drivers in any XP install. Some of those are system drivers, some are hardware drivers, some are software drivers. Any of these can become damaged and create problems, at any time. This is one reason the .dmp files are so important, IMO...since Windows may report File 1 as being the cause of a problem, when, in fact, File 1 is merely where the effect shows up in Windows.

Louis

#7 Please Help Us

Please Help Us
  • Topic Starter

  • Members
  • 156 posts
  • OFFLINE
  •  
  • Local time:02:49 AM

Posted 01 January 2010 - 01:32 PM

Alright sir I'll take a look at the .dmp files in a few minutes. Should I post them here or just report or ask for help with anything I don't understand. To be honest I'm more then a bit puzzled and I rather not make any stupid mistakes then I've already done. Thank you for what you've done so far, really its been a lot of help! :thumbsup:

#8 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 AM

Posted 01 January 2010 - 01:35 PM

If you follow the procedures suggested in the Help link I provided, you will post data back to your thread and someone will try to properly interpret it :thumbsup:.

Louis

#9 Please Help Us

Please Help Us
  • Topic Starter

  • Members
  • 156 posts
  • OFFLINE
  •  
  • Local time:02:49 AM

Posted 02 January 2010 - 05:21 AM

Alright sir, sorry for the late response, but hopefully you can answer a few more questions. I have SEVERAL minidumps, should I post them all of only the ones that are different and the latest.

Also should this topic be moved to the window's xp board at this point or is it still fine here?

Thank you once again for your help, hopefully I'll get some answers soon.

#10 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 AM

Posted 02 January 2010 - 07:50 AM

Hmmm...well, I'll suggest that it be moved internally to XP forum. There won't be any disruption so just look in this forum when you want to post.

It could be a hardware issue per se...but it's not looking like such, at this time.

Re the .dmp files....let's just look at the last three, at this time.

Louis

#11 Please Help Us

Please Help Us
  • Topic Starter

  • Members
  • 156 posts
  • OFFLINE
  •  
  • Local time:02:49 AM

Posted 02 January 2010 - 06:17 PM

Alright then, lucky us we have one from today then.

Anyway this is the latest three all happening January 2, 10, December 31, 09, and December 29, 09, in that order.

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini010210-01.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:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Jan 2 17:01:15.562 2010 (GMT-6)
System Uptime: 1 days 11:38:39.272
Loading Kernel Symbols
...............................................................
....................................................
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 805bc207, f7ac1b98, 0}

GetUlongFromAddress: unable to read from 80565d50
GetUlongFromAddress: unable to read from 80565d50
Probably pool corruption caused by Tag: NVMD

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

1: kd> !analyze -v
*******************************************************************************
* *
* 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: 805bc207, The address that the exception occurred at
Arg3: f7ac1b98, Trap Frame
Arg4: 00000000

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

GetUlongFromAddress: unable to read from 80565d50
GetUlongFromAddress: unable to read from 80565d50

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

FAULTING_IP:
nt!ObpCloseHandleTableEntry+13
805bc207 83b9a800000000 cmp dword ptr [ecx+0A8h],0

TRAP_FRAME: f7ac1b98 -- (.trap 0xfffffffff7ac1b98)
ErrCode = 00000000
eax=e1af1920 ebx=86dc4830 ecx=000a7ad0 edx=864c2329 esi=864c2328 edi=e1af1920
eip=805bc207 esp=f7ac1c0c ebp=f7ac1c18 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!ObpCloseHandleTableEntry+0x13:
805bc207 83b9a800000000 cmp dword ptr [ecx+0A8h],0 ds:0023:000a7b78=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: System

CORRUPTING_POOL_ADDRESS: 864c2308

CORRUPTING_POOL_TAG: NVMD

LAST_CONTROL_TRANSFER: from 805bc3df to 805bc207

STACK_TEXT:
f7ac1c18 805bc3df e1000eb0 e1af1920 00001c90 nt!ObpCloseHandleTableEntry+0x13
f7ac1c60 805bc517 00001c90 00000000 00000000 nt!ObpCloseHandle+0x87
f7ac1c74 8054162c 80001c90 f7ac1d4c 804fff41 nt!NtClose+0x1d
f7ac1c74 804fff41 80001c90 f7ac1d4c 804fff41 nt!KiFastCallEntry+0xfc
f7ac1cf0 8062ac9f 80001c90 8067d3b0 e2159d84 nt!ZwClose+0x11
f7ac1d4c 8062ab92 00009b60 00000000 80563010 nt!CmpCmdHiveClose+0xd9
f7ac1d68 80650acd 80564820 86dc37a8 00000000 nt!CmShutdownSystem+0x92
f7ac1d7c 8053877d 00000000 00000000 86dc37a8 nt!PopGracefulShutdown+0xdf
f7ac1dac 805cff72 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7ac1ddc 805460ee 8053868e 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ObpCloseHandleTableEntry+13
805bc207 83b9a800000000 cmp dword ptr [ecx+0A8h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObpCloseHandleTableEntry+13

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a784394

FAILURE_BUCKET_ID: CORRUPTING_POOLTAG_NVMD

BUCKET_ID: CORRUPTING_POOLTAG_NVMD

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






Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini123109-01.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:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Dec 31 01:02:23.468 2009 (GMT-6)
System Uptime: 0 days 7:45:13.172
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
.............................
Unable to load image ALCXWDM.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {654f680, 2, 0, f653adeb}

Probably caused by : ALCXWDM.SYS ( ALCXWDM+143deb )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0654f680, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f653adeb, address which referenced memory

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


READ_ADDRESS: 0654f680

CURRENT_IRQL: 2

FAULTING_IP:
ALCXWDM+143deb
f653adeb ff10 call dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: SamHD.exe

LAST_CONTROL_TRANSFER: from 00000000 to f653adeb

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 ALCXWDM+0x143deb


STACK_COMMAND: kb

FOLLOWUP_IP:
ALCXWDM+143deb
f653adeb ff10 call dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ALCXWDM+143deb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ALCXWDM

IMAGE_NAME: ALCXWDM.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 42ade0cd

FAILURE_BUCKET_ID: 0xD1_ALCXWDM+143deb

BUCKET_ID: 0xD1_ALCXWDM+143deb

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




Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini122909-01.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:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 29 03:14:33.218 2009 (GMT-6)
System Uptime: 0 days 4:32:42.924
Loading Kernel Symbols
...............................................................
.......................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000C5, {e9031c, 2, 1, 8054bfd2}

Probably caused by : ntkrpamp.exe ( nt!ExAllocatePoolWithTag+66a )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00e9031c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8054bfd2, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExAllocatePoolWithTag+66a
8054bfd2 894804 mov dword ptr [eax+4],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: McNASvc.exe

LAST_CONTROL_TRANSFER: from 805370d0 to 8054bfd2

STACK_TEXT:
b86e3c50 805370d0 0000000c 00000001 20206f49 nt!ExAllocatePoolWithTag+0x66a
b86e3c74 80580765 00000004 00000008 20206f49 nt!ExAllocatePoolWithQuotaTag+0x46
b86e3d00 80579274 00000064 00000920 00000000 nt!IopXxxControlFile+0x533
b86e3d34 8054162c 00000064 00000920 00000000 nt!NtDeviceIoControlFile+0x2a
b86e3d34 7c90e514 00000064 00000920 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0469fe5c 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+66a
8054bfd2 894804 mov dword ptr [eax+4],ecx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExAllocatePoolWithTag+66a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a784394

FAILURE_BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+66a

BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+66a

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

Edited by Please Help Us, 02 January 2010 - 06:21 PM.


#12 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 AM

Posted 02 January 2010 - 07:07 PM

Well...something to work with :thumbsup:.

<<CORRUPTING_POOL_TAG: NVMD>>

NVMD...equals Non Volatile Memory Device, e.g., a flash drive.

First time I've seen this one, I'd have to guess that...if you have a flash drive attached to this system, you may be infected. That's based on nothing but pure guesswork.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

<<Probably caused by : ALCXWDM.SYS>>

If you have Realtek audio...and file size and location match up with where it's supposed to be...it's probably a valid driver file that is damaged.

http://www.file.net/process/alcxwdm.sys.html

If not, possible malware.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

<<PROCESS_NAME: McNASvc.exe>>

http://mightychicken.com/mc/process/mcnasvc.exe.html AND http://www.file.net/process/mcnasvc.exe.html

OK...so it appears to me...that you might reflect on the possibility of being infected. I don't normally suspect such, but the NVDM error (rather, my interpretation of it) might point that way. Of course, if you haven't had or don't have a flash drive installed/attached, I would switch to suspecting the RAM.

To me, it seems unlikely that I would have an AV driver, an audio driver, and a memory error...all in the same day. Usually, when that happens, it's a CMOS battery problem for me and we have already ruled that out.

We can also rule out RAM, for the same reason.

I would check the entire system for infection, carefully...and I would check any flash drives for infections.

I would also uninstall and then reinstall...the McAfee program you have installed, since at least part of it is damaged.

Ditto for your audio drivers. Remove/uninstall the audio drivers using Device Manager...then reinstall same or updated drivers.

Louis

Edited by hamluis, 02 January 2010 - 07:46 PM.


#13 OldGrumpyBastard

OldGrumpyBastard

  • Members
  • 781 posts
  • OFFLINE
  •  
  • Location:&quot;Way South of 'da Bridge&quot;
  • Local time:01:49 AM

Posted 02 January 2010 - 07:14 PM

Your mini-dumps show a few things:

ALCXWDM.SYS = Realtek AC97 driver
ntkrpamp.exe = system process (Windows) first instance
ntkrpamp.exe = McAfee system process (Is McAfee installed?) 2nd instance

You should be able to download Realtek AC97 driver from your manufacturers website. If McAffe is installed (or once was) you can probably uninstall and re-install to fix this. ntkpamp.exe system process driver will probably be found on your XP installation CD. If you have the CD you can try sfc /scannow. Instructions can be found here:

http://www.bleepingcomputer.com/forums/t/43051/how-to-use-sfcexe-to-repair-system-files/
Does this look like an OldGrumpyBastard or what?

#14 Please Help Us

Please Help Us
  • Topic Starter

  • Members
  • 156 posts
  • OFFLINE
  •  
  • Local time:02:49 AM

Posted 04 January 2010 - 08:11 AM

Sorry for being a bit late sir, let me answer everything I can.

Alright going to download the realtek audio driver asap. Macafee is install onto my computer and will be uninstalled and reinstalled like you said to sir. Also I do have my Window's XP disc (The OS system or master one correct?) and I'm glad I've kept them all throughout the years. The only problem is that somehow it seems like my disc drives won't read anything I put into them I think I've might of knocked them loose when I was replacing the ram and cmos battery. Since I don't see them disabled in the bios file so I'm going to have to pull it out and check. Unless it could be something else you're thinking of, which I wouldn't be sure, but that's the next thing I'm going to check for it.

Now sir, I have four other BSOD logs, do you want me to post them to see if there is a pattern among them or if there is something else more sinister we've missed. Once again thank you deeply for your help so far, and I hope you don't mind me being ab it late in the response.

Also sorry one last edit question, would my computer being a dell have any effect on the realtek audio, and if I have the discs can I just reinstall from there?

Edited by Please Help Us, 04 January 2010 - 08:39 AM.


#15 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:49 AM

Posted 04 January 2010 - 11:01 AM

Rather than review older .dmp files, let's see what happens if you uninstall/reinstall the drivers suggested.

Yes, you can use your drivers CD to install drivers from...that's what I tend to do (since we know that those drivers work with the system).

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users