مشاهده نسخه کامل
: zahedy2006
16-05-2009, 17:44
من قبلا این مشکل رو عنوان کرده بودم. که دیده نشد:19:
سلام
من هم مشکل صفحه آبی را دارم اما وقتی که usb به کامپیوتر وصل می کنم این حالت پیش میاد!!
فلش و مموری را هم می خواند اما پرینتر ، مودم adsl و غیره را تا وصل می کنم صفحه آبی می آید و کامپیوتر ریستارت می شود.
در ضمن من بایوس رو به آخرین ورژن آپ کرده ام.
مادر برد asus P5QL Pro
سی پی یو 2180
و رم 1 گیگ 1066
با برنامه win debugger فایل های دامپ رو چک گردم و در حین چک 10 مگ دانلود کرد و نتیجه زیر را داد
نقل قول:
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 8657b0e0, Device extension pointer of the host controller
Arg3: 80863a34, PCI Vendor,Product id for the controller
Arg4: 85de7f70, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from f6c4ad23 to 804f9d1b
STACK_TEXT:
805502c8 f6c4ad23 000000fe 00000005 8657b0e0 nt!KeBugCheckEx+0x1b
805502e8 f6c57588 8657b028 00001fd0 85d7e000 USBPORT!USBPORT_BugCheck+0x2d
80550324 f78bf05c 05d7c1c0 8657b9dc 85de7f70 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
80550348 f78bcded 8657b9dc 85d7e000 80550378 usbuhci!UhciPollAsyncEndpoint+0x32
80550358 f6c44338 8657b9dc 85de7f70 80545bac usbuhci!UhciPollEndpoint+0x1f
80550378 f6c455f6 026c6f50 8657b0e0 85de7df8 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 f6c48f2e 8657b028 50457270 80545bac USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 f6c57023 8657b028 80545bac 8657b028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c f6c5719a 8657b028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x38f
80550428 80544f5f 8657b64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544e44 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+32
f78bf05c 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+32
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbuhci
IMAGE_NAME: usbuhci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62
FAILURE_BUCKET_ID: 0xFE_usbuhci!UhciPollAsyncEndpoint+32
BUCKET_ID: 0xFE_usbuhci!UhciPollAsyncEndpoint+32
Followup: MachineOwner
---------
در ضمن تست با برنامه memtest86+-2.11.iso هم انجام دادم رم ایراد نداشت.
نقل قول:
دوست عزیز
حتی بدون نتیجه ی اعلام از طرف نرم افزار میشه مجرم این ماجرا رو تشخیص داد[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
تخطی کنترلر USB سیستم شما در استفاده از فضای مورد نیازش بر روی رم بدون هماهنگی با چیپ شمالی و CPU باعث این اخطار و در نهایت ری استارت شدن سیستم شما میشه.
عوض کردن ویندوز یکی از راهکار های بسیار کارآمده که این مشکل رو حل میکنه (البته در 70 درصد موارد)
من ترجیح میدم که هیچ وقت ویندوزم رو عوض نکنم ، دوست دارم شما هم به این زحمت نیوفتید[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
آپدیت مربوط به بخش درایور USB رو انجام بدید.
کریتیکال آپدیت های ویندوز رو هم انجام بدید.
به احتمال زیاد مشکل برطرف میشه[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
سلام و ممنون
همه ویندوز xp ها رو از سال 2001 - که با کامپیوتر خریدم - تا همین چند روزه رو تست کردم و باز این مشکل پیش میاد!!
برای آپدیت هم من نمی دونم درایور رو از کجا بگیرم - به جز اونی که همراه مادربورد داده -
در ضمن اون کیس دیگرم که این مشکل رو داره مودم adsl بهش وصل نمیشه که آنلاین آپدیت رو انجام بدم - مودم هم usb است
نکته ای که هست اینه که قبلا مشکل نداشت ولی بعدا بروز کرد.
و جالبتر اینکه از اسپیکر آژیر پخش میشه!!!!! دمای سی پی یو و ... 41.5 درجه سانتیگراد است
ویرایش
این critical ها رو از کجا آپ کنم؟؟
این ویندوز آپدیت یه سری مذخرف نشون می ده!!
بعد امکان دانلود آپدیت ها به صورت جدا هست؟؟ حالت نصبی
باز هم مشکل ایجاد شد و پس از چک فایل این پیغام رو میده
نقل قول:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\ybx\Desktop\New Folder\Mini051409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols* کد:
[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu May 14 06:04:27.375 2009 (GMT+5)
System Uptime: 0 days 2[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
...........................................
Loading User Symbols
Loading unloaded module list
..................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, 866960e0, 80863a34, 85fc3b60}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
Probably caused by : usbuhci.sys ( usbuhci!UhciPollAsyncEndpoint+32 )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 866960e0, Device extension pointer of the host controller
Arg3: 80863a34, PCI Vendor,Product id for the controller
Arg4: 85fc3b60, Pointer to Endpoint data structure
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: usbuhci
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 453ca422
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xFE
LAST_CONTROL_TRANSFER: from f6c6fddb to 804f9f13
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805502c8 f6c6fddb 000000fe 00000005 866960e0 nt+0x22f13
805502e8 f6c7c710 86696028 00001fd0 864ff000 USBPORT!USBPORT_BugCheck+0x2d
80550324 f78bf102 064fd180 866969dc 85fc3b60 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
80550348 f78bcded 866969dc 864ff000 80550378 usbuhci!UhciPollAsyncEndpoint+0x32
80550358 f6c6940a 866969dc 85fc3b60 80545e4c usbuhci!UhciPollEndpoint+0x1f
80550378 f6c6a6c8 026c6f50 866960e0 85fc39e8 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 f6c6e000 86696028 50457270 80545e4c USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 f6c7c1ab 86696028 80545e4c 86696028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c f6c7c322 86696028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x38f
80550428 805451ff 8669664c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
8055043c 8055b0a0 8055ae40 ffdffc50 00000000 nt+0x6e1ff
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt+0x840a0
8055b0a0 00000000 8055b0a8 8055b0a8 8055b0b0 nt+0x83e40
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+32
f78bf102 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+32
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: usbuhci.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
مسیر سیمبل ها هم درسته
نکته جدید
قبلا نوشته بودم که فلش مموری و رم ریدر را می خواند. حالا وقتی که رم ریدر به دستگاه نصبه و یک یو اس پی جدید مثل مودم یا پرینتر را وصل میکنم کامپیوتر آنها را می شناسد اما درایور شون بدرستی نصب نمیشود:18:
سلام
من هم مشکل صفحه آبی را دارم اما وقتی که usb به کامپیوتر وصل می کنم این حالت پیش میاد!!
فلش و مموری را هم می خواند اما پرینتر ، مودم adsl و غیره را تا وصل می کنم صفحه آبی می آید و کامپیوتر ریستارت می شود.
در ضمن من بایوس رو به آخرین ورژن آپ کرده ام.
مادر برد asus P5QL Pro
سی پی یو 2180
و رم 1 گیگ 1066
با برنامه win debugger فایل های دامپ رو چک گردم و در حین چک 10 مگ دانلود کرد و نتیجه زیر را داد
نقل قول:
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 8657b0e0, Device extension pointer of the host controller
Arg3: 80863a34, PCI Vendor,Product id for the controller
Arg4: 85de7f70, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from f6c4ad23 to 804f9d1b
STACK_TEXT:
805502c8 f6c4ad23 000000fe 00000005 8657b0e0 nt!KeBugCheckEx+0x1b
805502e8 f6c57588 8657b028 00001fd0 85d7e000 USBPORT!USBPORT_BugCheck+0x2d
80550324 f78bf05c 05d7c1c0 8657b9dc 85de7f70 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
80550348 f78bcded 8657b9dc 85d7e000 80550378 usbuhci!UhciPollAsyncEndpoint+0x32
80550358 f6c44338 8657b9dc 85de7f70 80545bac usbuhci!UhciPollEndpoint+0x1f
80550378 f6c455f6 026c6f50 8657b0e0 85de7df8 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 f6c48f2e 8657b028 50457270 80545bac USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 f6c57023 8657b028 80545bac 8657b028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c f6c5719a 8657b028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x38f
80550428 80544f5f 8657b64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544e44 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+32
f78bf05c 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+32
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbuhci
IMAGE_NAME: usbuhci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62
FAILURE_BUCKET_ID: 0xFE_usbuhci!UhciPollAsyncEndpoint+32
BUCKET_ID: 0xFE_usbuhci!UhciPollAsyncEndpoint+32
Followup: MachineOwner
---------
در ضمن تست با برنامه memtest86+-2.11.iso هم انجام دادم رم ایراد نداشت.
نقل قول:
دوست عزیز
حتی بدون نتیجه ی اعلام از طرف نرم افزار میشه مجرم این ماجرا رو تشخیص داد[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
تخطی کنترلر USB سیستم شما در استفاده از فضای مورد نیازش بر روی رم بدون هماهنگی با چیپ شمالی و CPU باعث این اخطار و در نهایت ری استارت شدن سیستم شما میشه.
عوض کردن ویندوز یکی از راهکار های بسیار کارآمده که این مشکل رو حل میکنه (البته در 70 درصد موارد)
من ترجیح میدم که هیچ وقت ویندوزم رو عوض نکنم ، دوست دارم شما هم به این زحمت نیوفتید[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
آپدیت مربوط به بخش درایور USB رو انجام بدید.
کریتیکال آپدیت های ویندوز رو هم انجام بدید.
به احتمال زیاد مشکل برطرف میشه[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
سلام و ممنون
همه ویندوز xp ها رو از سال 2001 - که با کامپیوتر خریدم - تا همین چند روزه رو تست کردم و باز این مشکل پیش میاد!!
برای آپدیت هم من نمی دونم درایور رو از کجا بگیرم - به جز اونی که همراه مادربورد داده -
در ضمن اون کیس دیگرم که این مشکل رو داره مودم adsl بهش وصل نمیشه که آنلاین آپدیت رو انجام بدم - مودم هم usb است
نکته ای که هست اینه که قبلا مشکل نداشت ولی بعدا بروز کرد.
و جالبتر اینکه از اسپیکر آژیر پخش میشه!!!!! دمای سی پی یو و ... 41.5 درجه سانتیگراد است
ویرایش
این critical ها رو از کجا آپ کنم؟؟
این ویندوز آپدیت یه سری مذخرف نشون می ده!!
بعد امکان دانلود آپدیت ها به صورت جدا هست؟؟ حالت نصبی
باز هم مشکل ایجاد شد و پس از چک فایل این پیغام رو میده
نقل قول:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\ybx\Desktop\New Folder\Mini051409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols* کد:
[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu May 14 06:04:27.375 2009 (GMT+5)
System Uptime: 0 days 2[ برای مشاهده لینک ، لطفا با نام کاربری خود وارد شوید یا ثبت نام کنید ]
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
...........................................
Loading User Symbols
Loading unloaded module list
..................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, 866960e0, 80863a34, 85fc3b60}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
Probably caused by : usbuhci.sys ( usbuhci!UhciPollAsyncEndpoint+32 )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 866960e0, Device extension pointer of the host controller
Arg3: 80863a34, PCI Vendor,Product id for the controller
Arg4: 85fc3b60, Pointer to Endpoint data structure
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: usbuhci
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 453ca422
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xFE
LAST_CONTROL_TRANSFER: from f6c6fddb to 804f9f13
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805502c8 f6c6fddb 000000fe 00000005 866960e0 nt+0x22f13
805502e8 f6c7c710 86696028 00001fd0 864ff000 USBPORT!USBPORT_BugCheck+0x2d
80550324 f78bf102 064fd180 866969dc 85fc3b60 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
80550348 f78bcded 866969dc 864ff000 80550378 usbuhci!UhciPollAsyncEndpoint+0x32
80550358 f6c6940a 866969dc 85fc3b60 80545e4c usbuhci!UhciPollEndpoint+0x1f
80550378 f6c6a6c8 026c6f50 866960e0 85fc39e8 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 f6c6e000 86696028 50457270 80545e4c USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 f6c7c1ab 86696028 80545e4c 86696028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c f6c7c322 86696028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x38f
80550428 805451ff 8669664c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
8055043c 8055b0a0 8055ae40 ffdffc50 00000000 nt+0x6e1ff
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt+0x840a0
8055b0a0 00000000 8055b0a8 8055b0a8 8055b0b0 nt+0x83e40
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+32
f78bf102 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+32
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: usbuhci.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
مسیر سیمبل ها هم درسته
نکته جدید
قبلا نوشته بودم که فلش مموری و رم ریدر را می خواند. حالا وقتی که رم ریدر به دستگاه نصبه و یک یو اس پی جدید مثل مودم یا پرینتر را وصل میکنم کامپیوتر آنها را می شناسد اما درایور شون بدرستی نصب نمیشود:18: