Tech Support Forum banner

Sound Loop Crash (Please, please help!!!)

1154 Views 3 Replies 2 Participants Last post by  DT Roberts
Okay for like 1 year ++ i have been getting this crash im not sure i got it before i used windows 7, which was vista, i dont think i did but everyday when i turn my computer on after 2-6hours? my sound will randomly loop, playin the last bit of the music played every like 0.5sec, this music/sound can be from games, windows media player, youtube etc and SOMTIMES, only sometimes(minority of time)when this occurs i can't watch youtube videos or start video games either it would instantly crash my firefox on play. Other than that when my sound crashes everything else works fine. I have bought a new sound card still didnt fix it i run 64bit, 4gb ram(old), q660 quad core (old), asus p5e motherboard and a pretty hot PSU, corsair 620w

all my temps are fine etc, i have no idea whats wrong PLEASE HELP IM GOING DO LOSE MY MIND, ITS BEEN LIKE 2 YEARS restarting like 2-3 times a day... thank you very very much in advance
Status
Not open for further replies.
1 - 4 of 4 Posts
This sounds like it might actually be video-related. Although you are not experiencing BSODs, please follow the instructions here: http://www.techsupportforum.com/f217/blue-screen-of-death-bsod-posting-instructions-452654.html

It will provide us with many useful logs to troubleshoot.
doneeeeeeee

Attachments

All sorts of good stuff in there!

Apparently you have suffered from a few BSODs, but only a few. One is bugcheck 0x124 (usually hardware-related), another is 0xC2 pointing to dxgkrnl.sys (graphics card driver), and a new one for me - 0xBE:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Devin\AppData\Local\Temp\Rar$DI00.201\031110-42572-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50
Debug session time: Thu Mar 11 05:18:35.731 2010 (GMT-4)
System Uptime: 0 days 1:43:46.713
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff880041087d6, 127b78121, fffff8800691dc80, b}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4244e )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880041087d6, Virtual address for the attempted write.
Arg2: 0000000127b78121, PTE contents.
Arg3: fffff8800691dc80, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800691dc80 -- (.trap 0xfffff8800691dc80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88004108776
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ac60c4 rsp=fffff8800691de10 rbp=0000000000000000
 r8=0000000000000702  r9=0000000000000002 r10=fffffa8006444e40
r11=fffff8a00a2300d2 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!ExAcquireResourceExclusiveLite+0x54:
fffff800`02ac60c4 f0480fba696000  lock bts qword ptr [rcx+60h],0 ds:e238:fffff880`041087d6=83490000019e820f
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b3cdb2 to fffff80002abdf00

STACK_TEXT:  
fffff880`0691db18 fffff800`02b3cdb2 : 00000000`000000be fffff880`041087d6 00000001`27b78121 fffff880`0691dc80 : nt!KeBugCheckEx
fffff880`0691db20 fffff800`02abbfee : 00000000`00000001 fffff880`04108776 fffffa80`06444e00 fffff8a0`0010e670 : nt! ?? ::FNODOBFM::`string'+0x4244e
fffff880`0691dc80 fffff800`02ac60c4 : fffffa80`04a81180 00000000`02b0c848 00000000`00000000 00000000`00000080 : nt!KiPageFault+0x16e
fffff880`0691de10 fffff880`0121310b : 00000000`c00000d8 00000000`00000003 00000000`00000002 fffff8a0`02e2f010 : nt!ExAcquireResourceExclusiveLite+0x54
fffff880`0691de80 fffff880`012aee77 : 00000000`00000000 fffff8a0`02cfced8 fffff8a0`0a230106 00000000`00000000 : Ntfs!NtfsAcquireFcbWithPaging+0x13b
fffff880`0691dee0 fffff880`012afce2 : fffffa80`06444e40 fffffa80`04a82350 fffff8a0`001e4bc0 00000000`00000701 : Ntfs!NtfsFindPrefixHashEntry+0x44e
fffff880`0691e010 fffff880`012aa28d : fffffa80`06444e40 fffffa80`0408ec10 fffff880`0691e1f0 fffff880`0691e238 : Ntfs!NtfsFindStartingNode+0x452
fffff880`0691e0e0 fffff880`01213c0d : fffffa80`06444e40 fffffa80`0408ec10 fffff880`0691e490 fffff880`01026900 : Ntfs!NtfsCommonCreate+0x3dd
fffff880`0691e2c0 fffff800`02acd64a : fffff880`0691e400 fffff800`02b2fb00 fffff8a0`0010e6a0 fffff8a0`0010e6a0 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0691e2f0 fffff880`01213b2f : fffff880`01213bf0 fffff880`0691e400 fffff880`0691e400 fffff880`012b532d : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`0691e3d0 fffff880`012b09c0 : 00000000`00000000 00000000`00000000 fffff880`0691e620 fffffa80`0408ec10 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
fffff880`0691e430 fffff880`0102523f : fffffa80`04a81030 fffffa80`0408ec10 00000000`00000000 fffffa80`04925950 : Ntfs!NtfsFsdCreate+0x1b0
fffff880`0691e5e0 fffff880`010442b9 : fffffa80`0408ec10 fffffa80`04a86010 fffffa80`0408ec00 fffffa80`04925950 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0691e670 fffff800`02dbe477 : 00000000`00000005 fffff800`02dbded0 fffffa80`040e8b10 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`0691e720 fffff800`02db4764 : fffffa80`048cbcd0 00000000`00000000 fffffa80`0622e010 00000000`00000701 : nt!IopParseDevice+0x5a7
fffff880`0691e8b0 fffff800`02db9876 : fffffa80`0622e010 fffff880`0691ea30 fffff880`00000040 fffffa80`039ebc90 : nt!ObpLookupObjectName+0x585
fffff880`0691e9b0 fffff800`02dc0587 : fffff880`01044630 00000000`00000001 fffffa80`06c49b01 00000000`00000000 : nt!ObOpenObjectByName+0x306
fffff880`0691ea80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCreateFile+0x2b7


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4244e
fffff800`02b3cdb2 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4244e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4244e

BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4244e

Followup: MachineOwner
I definitely think this is video-related, especially because of those last two. Please install the latest graphics driver from here and see if BSODs persist: http://driverscollection.com/?H=Radeon HD 4800&By=ATI

Also, just to put out there:
Code:
Event[14225]:
  Log Name: System
  Source: Disk
  Date: 2010-06-29T15:26:19.035
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: moe-PC
  Description: 
The device, \Device\Harddisk1\DR1, has a bad block.
We'll worry about that later. Good luck!
See less See more
1 - 4 of 4 Posts
Status
Not open for further replies.
Top