Welcome Guest ( Log In | Register )

123 Pages « < 14 15 16 17 18 > » Bottom

Outline · [ Standard ] · Linear+

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

views
     
ChEnG3664
post Jul 5 2007, 11:20 PM

New Member
*
Junior Member
16 posts

Joined: May 2007


hi all, please help me. icon_question.gif icon_question.gif icon_question.gif i just finished set up a new PC. Here is my new PC spec:

-AMD AM2 4200+.
-Biostar 570 SLi.
-Palit 7300GT Sonic.
-2 X 1G Kingston value RAM 667Mhz.
-Enermax 460W FMAII.

I always have Bsoc blue screen problem while i wanna disconnect my broadband connection. Is it my network driver problem? But i search into Biostar web there is no driver for network. I also facing the USB problem while i try to using my card reader. The error is:

USB device not recognized
one of the USB devices attached to this computer has malfunctioned, and windows does not recognize it.

CAN ANYONE HELP ME TO SOLVE THIS BOTH MAIN PROBLEM OF MY NEWLY PC??? I FEEL WANNA CRY LIAO.......
f4st
post Jul 6 2007, 01:41 AM

New Member
*
Newbie
2 posts

Joined: Apr 2005


Hi guys,

I'm having some bsod problems here as well,mostly while plying wow n once awhile out in the windows,btw i already created my mini dump file by using WInDBG to analyse it. This is my results.Can anybdy help me out here?

QUOTE

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


Loading Dump File [C:\Documents and Settings\7\Desktop\Mini070507-03.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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Thu Jul  5 16:17:21.625 2007 (GMT+8)
System Uptime: 0 days 2:35:52.411
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8051b80c, f7c82a84, f7c82780}

Probably caused by : hardware ( kmixer!PerfUnregisterProvider+1f )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 8051b80c, The address that the exception occurred at
Arg3: f7c82a84, Exception Record Address
Arg4: f7c82780, Context Record Address

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!WmipDoFindRegEntryByDevice+11
8051b80c 8b5008          mov    edx,dword ptr [eax+8]

EXCEPTION_RECORD:  f7c82a84 -- (.exr 0xfffffffff7c82a84)
ExceptionAddress: 8051b80c (nt!WmipDoFindRegEntryByDevice+0x00000011)
  ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
  Parameter[0]: 00000000
  Parameter[1]: 0000000a
Attempt to read from address 0000000a

CONTEXT:  f7c82780 -- (.cxr 0xfffffffff7c82780)
eax=00000002 ebx=00000000 ecx=8055913c edx=86607a70 esi=8602df10 edi=00000000
eip=8051b80c esp=f7c82b4c ebp=f7c82b4c iopl=0        nv up ei pl nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            efl=00010217
nt!WmipDoFindRegEntryByDevice+0x11:
8051b80c 8b5008          mov    edx,dword ptr [eax+8] ds:0023:0000000a=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  3

PROCESS_NAME:  System

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

READ_ADDRESS:  0000000a

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

MISALIGNED_IP:
nt!WmipDoFindRegEntryByDevice+11
8051b80c 8b5008          mov    edx,dword ptr [eax+8]

LOCK_ADDRESS:  805624e0 -- (!locks 805624e0)

Resource @ nt!PiEngineLock (0x805624e0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address  : 0x805624e0
Thread Count  : 0
Thread address: 0x00000000
Thread wait  : 0x0

LAST_CONTROL_TRANSFER:  from 805e7d2b to 8051b80c

STACK_TEXT: 
f7c82b4c 805e7d2b 8602df10 00000080 8602df10 nt!WmipDoFindRegEntryByDevice+0x11
f7c82b60 805aae1a 8602df10 00000000 8602df10 nt!WmipFindRegEntryByDevice+0x1a
f7c82b74 805aadc7 8602df10 85e9b4b0 8602df10 nt!WmipDeregisterDevice+0x17
f7c82b90 b95d418f 8602df10 00000002 f7c82bb4 nt!IoWMIRegistrationControl+0xa9
f7c82ba0 b95bd4c8 8602df10 85e9b568 85942370 kmixer!PerfUnregisterProvider+0x1f
f7c82bb4 804e19ee 8602df10 85e9b4b0 f7c82c40 kmixer!DispatchPnp+0x58
f7c82bc4 8059df4d 8598ed68 8598ed68 00000017 nt!IopfCallDriver+0x31
f7c82bf0 805ab09d 8602df10 f7c82c1c 00000000 nt!IopSynchronousCall+0xb7
f7c82c44 805ab115 8598ed68 00000017 e2abb848 nt!IopRemoveDevice+0x93
f7c82c60 805ab347 00000308 e2abb848 00000000 nt!IopSurpriseRemoveLockedDeviceNode+0x90
f7c82c74 805ab372 8598d368 00000003 e2abb848 nt!IopDeleteLockedDeviceNode+0x50
f7c82ca8 805ab5fc 8598ed68 02abb848 00000003 nt!IopDeleteLockedDeviceNodes+0x3f
f7c82d3c 805ab6d0 f7c82d78 80703974 e53d3af0 nt!PiProcessQueryRemoveAndEject+0x4d2
f7c82d58 8059f480 f7c82d78 85f6e7e0 8056b4fc nt!PiProcessTargetDeviceEvent+0x2a
f7c82d7c 804e29d6 85f6e7e0 00000000 867c2640 nt!PiWalkDeviceList+0x122
f7c82dac 80576b24 85f6e7e0 00000000 00000000 nt!ExpWorkerThread+0xef
f7c82ddc 804eed86 804e2912 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
kmixer!PerfUnregisterProvider+1f
b95d418f 5d              pop    ebp

SYMBOL_STACK_INDEX:  4

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

SYMBOL_NAME:  kmixer!PerfUnregisterProvider+1f

STACK_COMMAND:  .cxr 0xfffffffff7c82780 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

Followup: MachineOwner
---------
shyjohn
post Jul 6 2007, 10:43 PM

Getting Started
**
Junior Member
108 posts

Joined: May 2007


QUOTE(f4st @ Jul 6 2007, 01:41 AM)
Hi guys,

I'm having some bsod problems here as well,mostly while plying wow n once awhile out in the windows,btw i already created my mini dump file by using WInDBG to analyse it. This is my results.Can anybdy help me out here?
*
Probably is a ram. Try reseat to another slot. If you have 2 sticks of ram, take out one and test one by one.


Added on July 6, 2007, 11:10 pm
QUOTE(choyster @ Jul 5 2007, 03:50 PM)
Today my comp crash 3 times here is the new dump,really sien thanks and pls help me guys
*
looks like faulty ram.

This post has been edited by shyjohn: Jul 6 2007, 11:10 PM
shahz
post Jul 6 2007, 11:22 PM

I have more stars than cleave
******
Senior Member
1,566 posts

Joined: Jun 2007
From: Subang Jaya


lol..BSOD does not necessarily be referred to RAM..Any hardware can cause a BSOD - including hard disk or even motherboard..sometimes, a software conflict can cause it too..If BSOD occured after you installed something, recover your Windows to an earlier state and test if it still occurs..Also, try to note down what is written in the BSOD so some guidance can be given..Sometimes, BSOD can be totalled and you might just end up performing a reformat.. smile.gif cheers

ShahZ
choyster
post Jul 6 2007, 11:26 PM

Regular
******
Senior Member
1,802 posts

Joined: May 2006


QUOTE(shyjohn @ Jul 6 2007, 10:43 PM)
Probably is a ram. Try reseat to another slot. If you have 2 sticks of ram, take out one and test one by one.


Added on July 6, 2007, 11:10 pm

looks like faulty ram.
*
how do i check if its a faulty ram mem86 i dunno use le
shyjohn
post Jul 6 2007, 11:30 PM

Getting Started
**
Junior Member
108 posts

Joined: May 2007


QUOTE(shahz @ Jul 6 2007, 11:22 PM)
lol..BSOD does not necessarily be referred to RAM..Any hardware can cause a BSOD - including hard disk or even motherboard..sometimes, a software conflict can cause it too..If BSOD occured after you installed something, recover your Windows to an earlier state and test if it still occurs..Also, try to note down what is written in the BSOD so some guidance can be given..Sometimes, BSOD can be totalled and you might just end up performing a reformat.. smile.gif cheers

ShahZ
*
Yes, BSOD does not necessarily be referred to RAM. I'm guessing (choyster's case) because most of stack pointing to win32k.sys which an integral part of windows. Usually this is symptoms of ram. The first thing to do when BSOD occurs is to check the ram because 80% BSOD caused by ram. In f4st's case, IP_MISALIGNED also related to ram problem.

Please correct me if wrong smile.gif


Added on July 6, 2007, 11:33 pm
QUOTE(choyster @ Jul 6 2007, 11:26 PM)
how do i check if its a faulty ram mem86 i dunno use le
*
please refer to this link www.memtest.org/ there also have instructions.

This post has been edited by shyjohn: Jul 6 2007, 11:39 PM
choyster
post Jul 7 2007, 12:00 AM

Regular
******
Senior Member
1,802 posts

Joined: May 2006




Added on July 6, 2007, 11:33 pm

please refer to this link www.memtest.org/ there also have instructions.
*

[/quote]

craps i dont have floppy
ff7yta
post Jul 7 2007, 12:29 PM

Rookie
******
Senior Member
1,091 posts

Joined: Oct 2005


QUOTE(choyster @ Jul 7 2007, 12:00 AM)
QUOTE


Added on July 6, 2007, 11:33 pm

please refer to this link www.memtest.org/ there also have instructions.
*
craps i dont have floppy
*
U can run memtest using another pc. All it needs is just swapping.

This post has been edited by ff7yta: Jul 7 2007, 12:30 PM
spikeee
post Jul 8 2007, 01:30 AM

Look at all my stars!!
*******
Senior Member
2,923 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: 12
LittleCordines
post Jul 9 2007, 06:13 PM

.: eXTRemELy nOOb :.
****
Senior Member
639 posts

Joined: May 2007
From: In The Middle Of Nowhere



BSOD problemo...

I need some help from you guys...

it happen again. is this cause by the HDD got bad sector..??

This post has been edited by LittleCordines: Jul 11 2007, 02:19 AM
9ty5
post Jul 14 2007, 07:11 PM

Getting Started
**
Junior Member
88 posts

Joined: Jan 2003
I got a BSOD which kinda relates to usb stuff, or so it seems. Here's the dump file.
Appreciate all form of assistance. smile.gif



Attached File(s)
Attached File  Mini071407_01.zip ( 5.96k ) Number of downloads: 15
BS87
post Jul 15 2007, 10:20 PM

New Member
*
Junior Member
11 posts

Joined: Jul 2007
HI , i am using compaq presario v3203au, recently my pc always appears bluescreen and i don't know why....

so may you guys help me to settle this problem?

this is my minidump file and the bluescreen snapshot
mini dump file
bluescreen snapshoot
spikeee
post Jul 15 2007, 10:47 PM

Look at all my stars!!
*******
Senior Member
2,923 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!


jaeger
post Jul 15 2007, 11:45 PM

New Member
*
Newbie
1 posts

Joined: Jul 2007
QUOTE(9ty5 @ Jul 14 2007, 07:11 PM)
I got a BSOD which kinda relates to usb stuff, or so it seems. Here's the dump file.
Appreciate all form of assistance.  smile.gif
*
Probably caused by : snpstd3.sys ( snpstd3+3a619 )

Error 0xFE occurs when you start the "Safely Remove Hardware" utility on a docked portable computer

http://support.microsoft.com/kb/329581

A "STOP 0xFE" error message occurs after your Windows XP-based computer returns from standby or from hibernation

http://support.microsoft.com/kb/837386

are you using usb web cam? try to uninstall/reinstall CliqueCam and make sure the driver is up to date.

QUOTE(BS87 @ Jul 15 2007, 10:20 PM)
HI , i am using compaq presario v3203au, recently my pc always appears bluescreen and i don't know why....

so may you guys help me to settle this problem?

this is my minidump file and the bluescreen snapshot
mini dump file
bluescreen snapshoot
*
Probably caused by : NVENETFD.sys ( NVENETFD+34ae )

try to update your motherboard driver esp Network.

9ty5
post Jul 16 2007, 12:08 AM

Getting Started
**
Junior Member
88 posts

Joined: Jan 2003
spikee,
Yeah, it's in .dmp format. I ain't too sure how to convert that to text format. Anything that comes standard with win xp that i can use to view the .dmp format?
spikeee
post Jul 16 2007, 12:41 AM

Look at all my stars!!
*******
Senior Member
2,923 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

BS87
post Jul 16 2007, 01:11 AM

New Member
*
Junior Member
11 posts

Joined: Jul 2007
hi spikeee i try upload my file b4, but it wrote..."Upload failed. You are not permitted to upload a file with that file extension."

so tat i choose badongo to uplaod my file, hope u guy don mind.

thx you jaeger, i will try to update my network driver...hope my problem will be fixed^^
ff7yta
post Jul 19 2007, 02:42 PM

Rookie
******
Senior Member
1,091 posts

Joined: Oct 2005


QUOTE(9ty5 @ Jul 14 2007, 07:11 PM)
I got a BSOD which kinda relates to usb stuff, or so it seems. Here's the dump file.
Appreciate all form of assistance.  smile.gif
*
Your minidump file states an error in ntkrnlpa.exe. This cannot pin to the problem causing the BSOD.

Can u explain what usb stuff causes your BSOD?

A possibility is that the USB is drawing too much power.
You might need to change your PSU.
Added on July 19, 2007, 2:42 pm
QUOTE(BS87 @ Jul 15 2007, 10:20 PM)
HI , i am using compaq presario v3203au, recently my pc always appears bluescreen and i don't know why....

so may you guys help me to settle this problem?

this is my minidump file and the bluescreen snapshot
mini dump file
bluescreen snapshoot
*
BSOD points to motherboard drivers. U need to update them.
QUOTE(BS87 @ Jul 16 2007, 01:11 AM)
hi spikeee i try upload my file b4, but it wrote..."Upload failed. You are not permitted to upload a file with that file extension."

so tat i choose badongo to uplaod my file, hope u guy don mind.

thx you jaeger, i will try to update my network driver...hope my problem will be fixed^^
*

If u want to upload a file, u must rename the extension to .txt, or u can zip the files before uploading. Lowyat.net does not support .rar extensions too. smile.gif

The badongo site doh.gif shakehead.gif
Added on July 19, 2007, 2:43 pm
QUOTE(spikeee @ Jul 8 2007, 01:30 AM)
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 :
Hope you guys can help me out!
*
The problem happens as there were too many inputs given or too many programs was opened at the same time.

Solution? Try to be more patient next time. smile.gif

Maybe I'm wrong, as there are many other possibilities.

This post has been edited by ff7yta: Jul 19 2007, 02:51 PM
spikeee
post Jul 19 2007, 03:15 PM

Look at all my stars!!
*******
Senior Member
2,923 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
shyjohn
post Jul 21 2007, 02:01 AM

Getting Started
**
Junior Member
108 posts

Joined: May 2007


QUOTE(spikeee @ Jul 19 2007, 03:15 PM)
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
*
interesting... is it working if you install with proper driver?


Added on July 21, 2007, 3:52 am
QUOTE(9ty5 @ Jul 14 2007, 07:11 PM)
I got a BSOD which kinda relates to usb stuff, or so it seems. Here's the dump file.
Appreciate all form of assistance.  smile.gif
*
Your dump file crashes with bugcheck FE with

para1: 00000002, BAD_URB. The USB client driver has submitted a USB Request Block (URB) that is still attached to another Input/Output (I/O) request packet (IRP) that is still pending in the USB driver.
Para2: 84e85e28 is the irp that is currently pending in usbport.sys
para3: 84e5ac48, the newest irp currently being submitted by the client.
Para4: 863ba470, URB that caused the error. I'm not sure with this one. But we need to do some troubleshooting: remove usb hub and CliqueCam from system and see if any differences and please visit Microsoft with this error 0xfe (2,...) maybe it's related to Microsoft hot fix.


This post has been edited by shyjohn: Jul 21 2007, 03:52 AM

123 Pages « < 14 15 16 17 18 > » Top
 

Change to:
| Lo-Fi Version
0.0269sec    0.38    6 queries    GZIP Disabled
Time is now: 29th March 2024 - 10:12 AM