Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on shutdown/restart


02 Nov 2010   #1

Windows 7 Ultimate (32bit)
 
 
BSOD on shutdown/restart

Hi all, i'm new to this forum, i just signed up because i have a problem with my windows 7. Every time i click shutdown from the start menu he says "shutting down windows" and then a bsod appears. Now...

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x86
- the original installed OS on the system? Yes
- an OEM or full retail version? full retail
- What is the age of system (hardware)? About 2 years
- What is the age of OS installation (have you re-installed the OS?) 13/01/2010, and yes, i reinstalled the OS

I attach the files created by the program in the "BSOD - Posting Instructions" thread
Thanks in advance.
EDIT: the file is now attached, sorry


My System SpecsSystem Spec
.

02 Nov 2010   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

The file is not attached.
My System SpecsSystem Spec
04 Nov 2010   #3

Windows 7 Ultimate (32bit)
 
 

as i said in the edit i uploaded the file... could someone help me now? Thx
My System SpecsSystem Spec
.


04 Nov 2010   #4

Windows 7 professional x86/
 
 

How long has this been happening?

Were there any changes to your system prior? i.e added HW or software application

Go to start --> search and type msconfig - under the General tab choose selective start up amd remove the tick from start up items. Then go to the startup tab and remove all ticks. Restart.

Test from there. If this works then you can start adding them back one by one until the problem application is located.

If it's still the same then we'll move on...
My System SpecsSystem Spec
04 Nov 2010   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\110110-19172-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82c19000 PsLoadedModuleList = 0x82d61810
Debug session time: Mon Nov 1 16:07:28.771 2010 (GMT-4)
System Uptime: 0 days 0:26:54.379
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 9286419c, 807c0b40, 807c0720}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c )
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: 9286419c, The address that the exception occurred at
Arg3: 807c0b40, Exception Record Address
Arg4: 807c0720, 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:
usbhub!UsbhFdoSetPowerDx_Action+36
9286419c 8b4728 mov eax,dword ptr [edi+28h]
EXCEPTION_RECORD: 807c0b40 -- (.exr 0xffffffff807c0b40)
ExceptionAddress: 9286419c (usbhub!UsbhFdoSetPowerDx_Action+0x00000036)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000028
Attempt to read from address 00000028
CONTEXT: 807c0720 -- (.cxr 0xffffffff807c0720)
eax=c4138a98 ebx=87148028 ecx=c4138998 edx=78447350 esi=c4138998 edi=00000000
eip=9286419c esp=807c0c08 ebp=807c0c20 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
usbhub!UsbhFdoSetPowerDx_Action+0x36:
9286419c 8b4728 mov eax,dword ptr [edi+28h] ds:0023:00000028=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000028
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d81718
Unable to read MiSystemVaType memory at 82d61160
00000028
FOLLOWUP_IP:
libusb0+428c
929e828c ?? ???
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 92864f66 to 9286419c
STACK_TEXT:
807c0c20 92864f66 c4138a98 00000000 c4138998 usbhub!UsbhFdoSetPowerDx_Action+0x36
807c0c48 92864dc8 871485d8 00000004 c4138998 usbhub!UsbhFdoDevicePowerState+0x189
807c0c64 9284ebac 87148028 871480e0 c4138998 usbhub!UsbhFdoPower_SetPower+0x6d
807c0c78 82c24d36 87148028 c4138998 00000016 usbhub!UsbhGenDispatch+0x63
807c0c90 82c5549e 00000004 87148028 807c0ca8 nt!IopPoHandleIrp+0x28
807c0ca0 82c27069 807c0cd8 929e828c 87148028 nt!IofCallDriver+0x55
807c0ca8 929e828c 87148028 c4138998 00000000 nt!PoCallDriver+0x10
WARNING: Stack unwind information not available. Following frames may be wrong.
807c0cd8 929e53dc 871270e0 c4138998 82d5a400 libusb0+0x428c
807c0cf8 82c24843 87127028 c4138998 00000000 libusb0+0x13dc
807c0d50 82e2766d 00000000 ae8b7616 00000000 nt!PopIrpWorker+0x351
807c0d90 82cd91d9 82c244f2 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: libusb0+428c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: libusb0
IMAGE_NAME: libusb0.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45ffb877
STACK_COMMAND: .cxr 0xffffffff807c0720 ; kb
FAILURE_BUCKET_ID: 0x7E_libusb0+428c
BUCKET_ID: 0x7E_libusb0+428c
Followup: MachineOwner
---------
This driver was listed as the direct cause and must be updated. All other suggestions have lead to an enviornment for the BSOD and must be correct to avoid future BSODs

Libusb0.sys file description
Productname: LibUSB-Win32 - Kernel Driver
Description: LibUSB-Win32 - Kernel Driver
Company:Company: http://libusb-win32.sourceforge.net

Outdated drivers
Code:
libusb0.sys  Tue Mar 20 06:33:27 2007 (45FF
lmimirr.sys  Tue Apr 10 18:32:11 2007 (461C
RaInfo.sys   Fri Jan 04 13:57:12 2008 (477E
The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. If the list is extensive I have included the driver verifier test so that you may determine which drivers are in need of immediate attention.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
http://www.duplexsecure.com/en/faq

Scan with your Anti Virus



How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
It is very important to remember that the dump reports only give clues as to the problem and although it is very easy to analyze only one or two, usually more are needed. If you experience additional BSOD after installing a current version of the driver in question, be sure to post so that we can use the additional information to assist you in preventing the BSOD's
My System SpecsSystem Spec
06 Nov 2010   #6

Windows 7 Ultimate (32bit)
 
 

so, the first thing, relly thanks for your anwsers, i tryied the first one, removing startup items, but i always get the bsod... now i'll try to update libusb
My System SpecsSystem Spec
06 Nov 2010   #7

Windows 7 Ultimate (32bit)
 
 

i just removed libusb (i dont need it anymore) and it just worked! no more BSOD =D yay! relly thanks richc46 and thanks you too solarwind for your anwser
My System SpecsSystem Spec
Reply

 BSOD on shutdown/restart




Thread Tools



Similar help and support threads for2: BSOD on shutdown/restart
Thread Forum
BSOD shutdown then restart BSOD Help and Support
Solved BSOD only at restart/shutdown BSOD Help and Support
Solved BSOD every shutdown & restart BSOD Help and Support
BSOD on shutdown/restart BSOD Help and Support
BSOD when shutdown or restart Graphic Cards
BSOD when shutdown/restart BSOD Help and Support
Shutdown / Restart = BSOD BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:10 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33