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

computer crashing quite often


  • Please log in to reply
4 replies to this topic

#1 wayne_uk

wayne_uk

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Local time:07:21 AM

Posted 15 March 2009 - 12:42 PM

Hi guys
having a problem with my computer crashing,occasionally back to windows screen but mostly to a total restart
I have followed the de-bugging information and i hope i have this report correct.
my machine is,
intel core2 quad Q8200
Gigabyte GA-73PVM-S2H motherboard with NVIDIA GeForce 7100 / NVIDIA nForce 630i onboard graphics
4Gig memory (corsaire)
running windows xp pro service pack3
500w power supply
Hope someone can help
thanks
wayne

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


Loading Dump File [C:\WINDOWS\Minidump\Mini031509-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Mar 15 15:32:27.968 2009 (GMT+0)
System Uptime: 0 days 1:04:35.536
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 804f0262, b4499c2c, 0}

Probably caused by : ntkrpamp.exe ( nt!IopStartNextPacketByKeyEx+1c )

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

2: 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: 804f0262, The address that the exception occurred at
Arg3: b4499c2c, 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!IopStartNextPacketByKeyEx+1c
804f0262 f00fc13a lock xadd dword ptr [edx],edi

TRAP_FRAME: b4499c2c -- (.trap 0xffffffffb4499c2c)
ErrCode = 00000002
eax=00000020 ebx=880d7b80 ecx=00000000 edx=0000001c esi=883eb2e0 edi=00000001
eip=804f0262 esp=b4499ca0 ebp=b4499ca8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IopStartNextPacketByKeyEx+0x1c:
804f0262 f00fc13a lock xadd dword ptr [edx],edi ds:0023:0000001c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from 804f031d to 804f0262

STACK_TEXT:
b4499ca8 804f031d 883eb2e0 00000000 00000020 nt!IopStartNextPacketByKeyEx+0x1c
b4499d38 8054162c 000008c0 00000000 00000000 nt!IoStartNextPacket+0x2d
b4499d38 7c90e4f4 000008c0 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
06f2af9c 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IopStartNextPacketByKeyEx+1c
804f0262 f00fc13a lock xadd dword ptr [edx],edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!IopStartNextPacketByKeyEx+1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

FAILURE_BUCKET_ID: 0x8E_nt!IopStartNextPacketByKeyEx+1c

BUCKET_ID: 0x8E_nt!IopStartNextPacketByKeyEx+1c

Followup: MachineOwner



Additional information on BSOD.
win32k.sys page-fault-in-non-paged-area
syop: 0x00000050 (0x80000003. 0x00000000. 0xBF815EF5. 0x00000000)
win32k.sys-address BF815EF5 base at BF800000
datestamp 4900FC9

hope this helps
wayne

Edited by wayne_uk, 15 March 2009 - 03:03 PM.


BC AdBot (Login to Remove)

 


#2 wayne_uk

wayne_uk
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Local time:07:21 AM

Posted 17 March 2009 - 10:46 AM

Hi,
I think i may have found the problem, a sound driver
I have posted in the internal hardware section,
so if a mod would like to close this post down then ok
thanks
wayne

#3 wayne_uk

wayne_uk
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Local time:07:21 AM

Posted 19 March 2009 - 09:10 AM

Hi Guys
Update to the problem,
I have done a complete new install of windows, i am still having a problem with crashes, here is a new minidump file
thanks
Microsoft Windows Debugger Version 6.11.0001.404 X86
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Mar 19 13:12:50.953 2009 (GMT+0)
System Uptime: 0 days 1:13:37.890
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image RtkHDAud.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {60, 2, 0, b71298c1}

Probably caused by : RtkHDAud.sys ( RtkHDAud+6f8c1 )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b71298c1, address which referenced memory

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


READ_ADDRESS: 00000060

CURRENT_IRQL: 2

FAULTING_IP:
RtkHDAud+6f8c1
b71298c1 8b09 mov ecx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b7121eb8 to b71298c1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805510c0 b7121eb8 00000058 80551114 89461b80 RtkHDAud+0x6f8c1
80551130 b70f90b1 89481af0 8055118c 89461000 RtkHDAud+0x67eb8
80551400 b70fba35 89461008 89026c78 ffdff980 RtkHDAud+0x3f0b1
80551428 80545e7f 89485114 89461000 89026c78 RtkHDAud+0x41a35
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
RtkHDAud+6f8c1
b71298c1 8b09 mov ecx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: RtkHDAud+6f8c1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME: RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46f0e8e2

FAILURE_BUCKET_ID: 0xD1_RtkHDAud+6f8c1

BUCKET_ID: 0xD1_RtkHDAud+6f8c1

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b71298c1, address which referenced memory

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


READ_ADDRESS: 00000060

CURRENT_IRQL: 2

FAULTING_IP:
RtkHDAud+6f8c1
b71298c1 8b09 mov ecx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b7121eb8 to b71298c1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805510c0 b7121eb8 00000058 80551114 89461b80 RtkHDAud+0x6f8c1
80551130 b70f90b1 89481af0 8055118c 89461000 RtkHDAud+0x67eb8
80551400 b70fba35 89461008 89026c78 ffdff980 RtkHDAud+0x3f0b1
80551428 80545e7f 89485114 89461000 89026c78 RtkHDAud+0x41a35
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
RtkHDAud+6f8c1
b71298c1 8b09 mov ecx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: RtkHDAud+6f8c1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME: RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46f0e8e2

FAILURE_BUCKET_ID: 0xD1_RtkHDAud+6f8c1

BUCKET_ID: 0xD1_RtkHDAud+6f8c1

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b71298c1, address which referenced memory

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


READ_ADDRESS: 00000060

CURRENT_IRQL: 2

FAULTING_IP:
RtkHDAud+6f8c1
b71298c1 8b09 mov ecx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b7121eb8 to b71298c1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805510c0 b7121eb8 00000058 80551114 89461b80 RtkHDAud+0x6f8c1
80551130 b70f90b1 89481af0 8055118c 89461000 RtkHDAud+0x67eb8
80551400 b70fba35 89461008 89026c78 ffdff980 RtkHDAud+0x3f0b1
80551428 80545e7f 89485114 89461000 89026c78 RtkHDAud+0x41a35
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
RtkHDAud+6f8c1
b71298c1 8b09 mov ecx,dword ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: RtkHDAud+6f8c1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME: RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46f0e8e2

FAILURE_BUCKET_ID: 0xD1_RtkHDAud+6f8c1

BUCKET_ID: 0xD1_RtkHDAud+6f8c1

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

just had 2 new internet explorer reports, as followed

AppName: dmcr.exe AppVer: 1.0.0.1 ModName: dmcr.exe
ModVer: 1.0.0.1 Offset: 000708a1

AppName: iexplore.exe AppVer: 7.0.6000.16791 ModName: flash10b.ocx
ModVer: 10.0.22.87 Offset: 000ba57d

Edited by wayne_uk, 19 March 2009 - 09:42 AM.


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,884 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:21 AM

Posted 19 March 2009 - 01:04 PM

Looks to me like you need a new sound driver or sound chip/card.

RtkHDAud+6f8c1 points to a Realtek sound driver.

I suggest uninstalling all audio drivers before attempting to install the most current version for your system. At times, updating is merely ineffective when a driver is corrupt/damaged.

Louis

#5 wayne_uk

wayne_uk
  • Topic Starter

  • Members
  • 39 posts
  • OFFLINE
  •  
  • Local time:07:21 AM

Posted 19 March 2009 - 03:53 PM

Thanks for replying Louis,
I had the same thoughts, on my motherboard i also have HDMI audio, I wondered if there was a conflict, so I have disabled the HDMI audio on the board and been soak testing my system for 6 hours now without the crashing, so hopefully i may have found the problem, i will find out tomorrow if my computer does not crash tonight I will enable the HDMI audio and see what happens,
wayne




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users