Welcome Guest ( Log In | Register )

Bump Topic Add Reply RSS Feed
3 Pages  1 2 3 >Bottom

Outline · [ Standard ] · Linear+

 [FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.

views
     
spikeee
post Jul 8 2007, 01:30 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
Hey guys,

just reformatted fresh windows, with new mobo.

installed mobo drivers, gpu/sound card drivers etc etc
i got one or two BSOD about an emu10k file.

attached is the minidump file and my debug analysis :

QUOTE
Microsoft ® Windows Debugger  Version 6.7.0005.1
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Spikeee\Desktop\Mini070707-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Sat Jul  7 01:52:17.687 2007 (GMT+8)
System Uptime: 0 days 0:00:27.265
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f72d5e75, b8aaedfc, 0}

Probably caused by : emu10k1m.sys ( emu10k1m!cardmixerGetDestDetails+1f )

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

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: f72d5e75, The address that the exception occurred at
Arg3: b8aaedfc, 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:
emu10k1m!cardmixerGetDestDetails+1f
f72d5e75 8b4608          mov    eax,dword ptr [esi+8]

TRAP_FRAME:  b8aaedfc -- (.trap 0xffffffffb8aaedfc)
ErrCode = 00000000
eax=00000000 ebx=86374008 ecx=00000001 edx=00000000 esi=00000001 edi=00000000
eip=f72d5e75 esp=b8aaee70 ebp=b8aaee74 iopl=0        nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            efl=00010246
emu10k1m!cardmixerGetDestDetails+0x1f:
f72d5e75 8b4608          mov    eax,dword ptr [esi+8] ds:0023:00000009=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  winlogon.exe

LAST_CONTROL_TRANSFER:  from f72e5672 to f72d5e75

STACK_TEXT: 
b8aaee74 f72e5672 86374008 00000001 b8aaf050 emu10k1m!cardmixerGetDestDetails+0x1f
b8aaf104 f72ea12c 863d019c b8aaf190 865ec780 emu10k1m!cardwaveSetupWaveVolume+0x8a
b8aaf154 f72c994e 863d019c b8aaf1b4 f72c7efe emu10k1m!cardwaveOutOpen+0x532
b8aaf188 f7306778 00002b11 00001000 e21d3928 emu10k1m!CMiniportWaveCyclicStreamSBLive::HwOpen+0x3c
b8aaf1c8 f7305c61 005ec728 e21d38e8 b8aaf230 emu10k1m!CMiniportWaveCyclicStreamSBLive::SetFormat+0x128
b8aaf1f4 f73065e5 865bb600 00000002 85d4bd00 emu10k1m!CMiniportWaveCyclicStreamSBLive::Init+0x189
b8aaf230 f72bef60 865bb600 85d4bce4 00000000 emu10k1m!CMiniportWaveCyclicSBLive::NewStream+0xcf
b8aaf268 f72bdced 00000000 864da628 86476cf8 portcls!CPortPinWaveCyclic::Init+0x250
b8aaf290 f72b1fa0 864da5e8 86560bb4 86560bb8 portcls!CPortFilterWaveCyclic::NewIrpTarget+0xd9
b8aaf2d8 f72b20e9 86476cf8 86576030 864ae008 portcls!xDispatchCreate+0x90
b8aaf2ec f7288077 86576030 864ae008 864ae018 portcls!KsoDispatchCreateWithGenericFactory+0x2b
b8aaf310 f72870b6 86576030 00000000 b8aaf338 ks!DispatchCreate+0xc7
b8aaf320 f72b2057 86576030 864ae008 8669c1b8 ks!KsDispatchIrp+0x98
b8aaf338 804e37f7 86576030 864ae008 864ae008 portcls!DispatchCreate+0x34
b8aaf348 8056f54a 866cf6f8 86631c98 b8aaf528 nt!IopfCallDriver+0x31
b8aaf428 80570c14 86576030 00000000 864db4a0 nt!IopParseDevice+0xa12
b8aaf460 805676b5 866cf6f8 00000000 864db4a0 nt!IopParseFile+0x46
b8aaf4e8 8056749a 80000594 b8aaf528 00000240 nt!ObpLookupObjectName+0x119
b8aaf53c 8056fa23 00000000 00000000 7e38b000 nt!ObOpenObjectByName+0xeb
b8aaf5b8 8056faf2 e226f870 40000000 b8aaf660 nt!IopCreateFile+0x407
b8aaf614 f728858b e226f870 40000000 b8aaf660 nt!IoCreateFile+0x8e
b8aaf690 f7287b19 80000594 f7287b20 e1b15118 ks!KsiCreateObjectType+0xd6
b8aaf6b0 f719cfee 80000594 e1b15118 40000200 ks!KsCreatePin+0x33
b8aaf6d4 f719d70b e21cbeb0 e2138958 e1a995c0 sysaudio!CPinNodeInstance::Create+0x6b
b8aaf710 f719c464 f71a5490 e21cbeac e1ab1b80 sysaudio!CConnectNodeInstance::Connect+0xb3
b8aaf72c f71a2e82 00000000 864da688 f71a5490 sysaudio!CStartNodeInstance::Connect+0x52
b8aaf754 f719b575 e1aa4748 e170ce28 864da688 sysaudio!CStartNodeInstance::Create+0x1a2
b8aaf784 f719c1f7 c0000010 864da688 00000000 sysaudio!CPinInstance::PinDispatchCreateKP+0xa8
b8aaf7a0 f719b71a 8595e358 f719b4e7 864da688 sysaudio!CInstance::DispatchCreate+0x63
b8aaf7d4 f7288077 864acf08 8595e358 8595e368 sysaudio!CPinInstance::PinDispatchCreate+0xc1
b8aaf7f8 804e37f7 864acf08 00000000 8595e358 ks!DispatchCreate+0xc7
b8aaf808 8056f54a 8662f948 865954b8 b8aaf9e8 nt!IopfCallDriver+0x31
b8aaf8e8 80570c14 864acf08 00000000 85d48a88 nt!IopParseDevice+0xa12
b8aaf920 805676b5 8662f948 00000000 85d48a88 nt!IopParseFile+0x46
b8aaf9a8 8056749a 00000798 b8aaf9e8 00000040 nt!ObpLookupObjectName+0x119
b8aaf9fc 8056fa23 00000000 00000000 4eeeb400 nt!ObOpenObjectByName+0xeb
b8aafa78 8056faf2 b8aafba0 40000000 b8aafb20 nt!IopCreateFile+0x407
b8aafad4 f728858b b8aafba0 40000000 b8aafb20 nt!IoCreateFile+0x8e
b8aafb50 f7287b19 00000798 f7287b20 864dac90 ks!KsiCreateObjectType+0xd6
b8aafb70 b89e73d4 00000798 864dac90 40000000 ks!KsCreatePin+0x33
b8aafba4 b89e7805 00000000 00000003 00000001 wdmaud!OpenSysAudioPin+0xa1
b8aafbe0 b89e6a76 00000092 00000003 864a0588 wdmaud!OpenWavePin+0x3e2
b8aafc0c b89e6382 864b4008 864a0588 00000000 wdmaud!Dispatch_OpenPin+0xb7
b8aafc34 804e37f7 00000010 85d32000 806ee2d0 wdmaud!SoundDispatch+0x430
b8aafc44 8056a148 864b409c 8637f778 864b4008 nt!IopfCallDriver+0x31
b8aafc58 8057ad03 865a84a8 864b4008 8637f778 nt!IopSynchronousServiceTail+0x60
b8aafd00 8057d281 000007d4 000007a4 00000000 nt!IopXxxControlFile+0x611
b8aafd34 804de7ec 000007d4 000007a4 00000000 nt!NtDeviceIoControlFile+0x2a
b8aafd34 7c90eb94 000007d4 000007a4 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
018dfab8 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP:
emu10k1m!cardmixerGetDestDetails+1f
f72d5e75 8b4608          mov    eax,dword ptr [esi+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  emu10k1m!cardmixerGetDestDetails+1f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: emu10k1m

IMAGE_NAME:  emu10k1m.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3b6b5fb2

FAILURE_BUCKET_ID:  0x8E_emu10k1m!cardmixerGetDestDetails+1f

BUCKET_ID:  0x8E_emu10k1m!cardmixerGetDestDetails+1f

Followup: MachineOwner
---------
Hope you guys can help me out!


Attached File(s)
Attached File  Mini070707_01.zip ( 16.49k ) Number of downloads: 13
spikeee
post Jul 15 2007, 10:47 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
9ty5 - erm what format is your dump file in? i can't open it. it doesn't seem to be a .dmp file

badongo - it would help a lot if you just attached ur files using the internal uploader for files that small. thanks!
spikeee
post Jul 16 2007, 12:41 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
9ty5 - read the first page of this thread. download and install windebugger . it'll help u open the file for you to read it

all the best
spikeee
post Jul 19 2007, 03:15 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
no i found out what was wrong. i had a creative live value card in the pci slot. for some strange reason, windows actually automatically detects AND INSTALLS software for it (wrong software, though) , even without me installing proper driver for it.

when i don't install proper driver from creative, it detects that the driver for the pci card is wrong, therefore it crashes.

changed sound card (too old, anyway) and no more problem
spikeee
post Jul 25 2007, 02:15 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
Looks like an audio driver problem. Your realtek on board audio driver has been installed properly? try uninstalling and reinstalling it FIRST.

then we see how it goes

Added on July 25, 2007, 2:19 pmThe thing is that onboard audio drivers aren't able to play too many sounds at one time and if your EAX is enabled, that could be causing the problem.

if you really want to make sure that it's the sound card problem, try to disable sounds while playing and see if anything happens. report back here please

all the best!

This post has been edited by spikeee: Jul 25 2007, 02:19 PM
spikeee
post Jul 27 2007, 02:48 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
biggrin.gif Glad to hear that! You're most welcome smile.gif

spikeee
post Jul 29 2007, 12:15 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
brainwasher,

sorry, but maybe u could elaborately tell us exactly what steps u took in diagnosing the problem?
spikeee
post Aug 4 2007, 12:41 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
Looks like a memory problem. Could be a faulty ram. Or first, try to take it out and put it back in
spikeee
post Aug 13 2007, 10:05 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
u've got to show us your minidump for us to be able to even have an idea, bro
spikeee
post Aug 13 2007, 11:47 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
that's why it's called idle process wink.gif IDLE. wink.gif
that's where your system draws processor utilization from.

that's normal.

ok you have ccleaner, so the next time it happens, (BSOD), don't use CCleaner to clear your logs.
spikeee
post Aug 23 2007, 12:06 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
i don't have my windows debugger here with me, but for beast921's error, one of your drivers is causing an issue with the irq address.

usually the driver name is included in the BSOD message. something.sys or something
spikeee
post Aug 23 2007, 01:54 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
Ok , beast921. if you get a BSOD again, please tell me the filename that it includes so that i'll be able to know which driver it is exactly
spikeee
post Apr 16 2008, 03:52 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
Guys, see if you can help me diagnose this minidump :


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


Loading Dump File [C:\Documents and Settings\spikeee\Desktop\minidump\Mini041608-22.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:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
Debug session time: Wed Apr 16 15:00:12.560 2008 (GMT+8)
System Uptime: 0 days 0:03:08.136
Loading Kernel Symbols
.......................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {0, 9f56, ffff60a9, 0}



Probably caused by : NDIS.sys ( NDIS!___PchSym_+c )

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

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

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 00000000, Actual security check cookie from the stack
Arg2: 00009f56, Expected security check cookie
Arg3: ffff60a9, Complement of the expected security check cookie
Arg4: 00000000, zero

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




DEFAULT_BUCKET_ID: GS_FALSE_POSITIVE_MISSING_GSFRAME

SECURITY_COOKIE: Expected 00009f56 found 00000000

CUSTOMER_CRASH_COUNT: 22

BUGCHECK_STR: 0xF7

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from f7970f10 to 80533736

STACK_TEXT:
f0518a2c f7970f10 000000f7 00000000 00009f56 nt!KeBugCheckEx+0x1b
WARNING: Frame IP not in any known module. Following frames may be wrong.
f0518a4c f797064e 04e4eb34 00000000 04e4eb60 0xf7970f10
f0518ddc 804f88fa f73fab85 83f551e0 00000000 0xf797064e
f0518de0 f73fab84 83f551e0 00000000 0000027f nt!KiThreadStartup+0x16
f0518de4 83f551e0 00000000 0000027f 00000000 NDIS!___PchSym_+0xc
f0518de8 00000000 0000027f 00000000 00000000 0x83f551e0


STACK_COMMAND: kb

FOLLOWUP_IP:
NDIS!___PchSym_+c
f73fab84 90 nop

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: NDIS!___PchSym_+c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NDIS

IMAGE_NAME: NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec3

FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_NDIS!___PchSym_+c

BUCKET_ID: 0xF7_MISSING_GSFRAME_NDIS!___PchSym_+c

Followup: MachineOwner
---------
spikeee
post Apr 16 2008, 11:42 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
it would be best if you could post up the minidump file here at least
spikeee
post Apr 18 2008, 10:38 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
Bro, i'm not sure if it's me or what, but both your minidump files are corrupted. Please post your .dmp files again
spikeee
post Apr 20 2008, 01:25 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
Okies, i attempted to analyze your minidump immediately, but it was corrupted, so yeah. all the best!
spikeee
post Apr 23 2008, 10:12 AM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
is it me or is everything that's uploaded to lyn corrupted :s
i can't seem to open the minidump YET AGAIN :s
spikeee
post Apr 23 2008, 01:29 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
bro i'm so sorry, i don't know why i can't seem to open the zip files sad.gif could be my side.. :s

after uploading, can you try downloading the file again and see if you can open the zip file?
spikeee
post Apr 23 2008, 02:27 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
ok all the best with the resolution

*settled via msn*
spikeee
post Apr 23 2008, 03:48 PM

Look at all my stars!!
*******
Senior Member
2,924 posts

Joined: Jan 2005
From: Stamford Bridge
have you tried it? let us know the updates, bro smile.gif
« Next Oldest · Technical Support · Next Newest »
 

3 Pages  1 2 3 >Top
Add ReplyOptions
 

Change to:
| Lo-Fi Version
 0.0652sec    0.25    7 queries    GZIP Disabled
Time is now: 2nd December 2025 - 02:18 AM
All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)
Removal Request
Powered by Invision Power Board © 2025  IPS, Inc.