compsavvy

@magicandre Thanks. Will try and reply with results

@magicandre Need your help on this. This is a brand new sandy bridge laptop with a greater than 2 minute boot time. The trace: https://www.dropbox.com/s/n2uak80f78orbuo/boot_base%2Bcswitch%2Bdrivers%2Bpower_1.7z And the log: [2012/05/21-19:28:47.284] Detected Win7RTM physical (ReadyBoot) prefetcher; the SysMain service is auto-started. [2012/05/21-19:28:47.300] Registering for auto-run with a 120000 msec delay... [2012/05/21-19:28:47.300] Completed auto-run change. [2012/05/21-19:28:47.331] Starting trace... [2012/05/21-19:28:48.173] Enabled boot logging to 'C:\Windows\system32\boot_base+cswitch+drivers+power_1_km_premerge.etl' [2012/05/21-19:31:38.349] Detected Win7RTM physical (ReadyBoot) prefetcher; the SysMain service is auto-started. [2012/05/21-19:31:38.365] Stopping trace... [2012/05/21-19:31:41.500] Stopped kernel logger. [2012/05/21-19:31:41.719] Stopped user-mode logger. [2012/05/21-19:31:41.719] The trace you are capturing "C:\Windows\system32\boot_base+cswitch+drivers+power_1.etl" may contain personally identifiable information, including but not necessarily limited to paths to files accessed, paths to registry accessed and process names. Exact information depends on the events that were logged. Please be aware of this when sharing out this trace with other people. [2012/05/21-19:32:28.176] Merged ETL file to 'C:\Windows\system32\boot_base+cswitch+drivers+power_1.etl' [2012/05/21-19:32:28.238] Waiting for prefetcher... [2012/05/21-19:37:18.695] Gave up waiting for Win7RTM physical prefetcher after 300 seconds. [2012/05/21-19:37:18.695] Could not wait for prefetcher. [2012/05/21-19:37:18.695] Stopping trace... [2012/05/21-19:37:18.789] Couldn't find kernel logger in active logger list. [2012/05/21-19:37:18.789] Couldn't find user-mode logger in active logger list. [2012/05/21-19:37:18.789] Unregistering auto-run... [2012/05/21-19:37:18.789] Completed auto-run change. Regards

@MagicAndre1981 I did not figure it out that the problem had been resolved. I was just trying to help.

@Marian I feel your system files may be corrupt. So, try this: SFC.EXE /SCANNOW Again in an elevated command prompt

@marian If what MagicAndre1981 suggested does not help, open notepad as admin and save a blank file as layout.ini(and not layout.ini.txt) in the prefetch folder.

@marian It happens if "idle tasks" have been taken care of recently. Have you tried boot defrag?? if not try this in an elevated command prompt defrag.exe [drive letter]: -b

@Marian Open cmd.exe as admin Type this: rundll32.exe advapi32.dll,ProcessIdleTasks And wait for it to complete

I can assure you that usage pattern remains same. Anyway I can debug it cause I am losing a great deal of battery life. I am using catalyst 11.3 gpu driver. I suspect something with the usb root hub as my notebook has a webcam (it is using generic windows driver as oem did not provide any driver for it) and a bluetooth adapter attached to usb. I have disabled bt from the bios. So, it should not create problems. It would be great if you could help me troubleshoot the driver issue.

I wanted your help on the power issue of my notebook. Using batterybar, i have monitored the battery discharge rate and found that on an average, the discharge rate is 4w higher after resuming from sleep that from a reboot. Do you know of any tool that can diagnose it?? By the way, my manufacturer(dell) has posted 12 BIOS updates and none of them seems to have resolved the issue, So, I think it must be windows. I have win 7 x64 sp1 installed on a dell studio 1558 notebook

@magic andrei Remember the usbvideo.sys BSOD?? Well, I installed the sp1 and the problem did not go away. Then I tried the hotfix but to no avail. Any inputs??

@andrei I can confirm that the issue is with webcam driver. Disabling the integrated webcam solves the problem for me.

BugCheck 1000007E, {ffffffffc0000005, fffff800031bde87, fffff880033bd128, fffff880033bc990} Probably caused by : usbvideo.sys ( usbvideo+3783 ) Followup: MachineOwner --------- 3: 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: ffffffffc0000005, The exception code that was not handled Arg2: fffff800031bde87, The address that the exception occurred at Arg3: fffff880033bd128, Exception Record Address Arg4: fffff880033bc990, 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!IopPerfCompleteRequest+47 fffff800`031bde87 488b5008 mov rdx,qword ptr [rax+8] EXCEPTION_RECORD: fffff880033bd128 -- (.exr 0xfffff880033bd128) ExceptionAddress: fffff800031bde87 (nt!IopPerfCompleteRequest+0x0000000000000047) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880033bc990 -- (.cxr 0xfffff880033bc990) rax=09010100e4e1c000 rbx=fffffa80198f0b70 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80198f0740 rip=fffff800031bde87 rsp=fffff880033bd360 rbp=fffffa80198cbc80 r8=fffffa8003bd9058 r9=fffffa8004c31000 r10=0000000000401802 r11=fffff880033bd400 r12=fffffa80198c7a00 r13=fffffa80198c8d60 r14=0000000000000476 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!IopPerfCompleteRequest+0x47: fffff800`031bde87 488b5008 mov rdx,qword ptr [rax+8] ds:002b:09010100`e4e1c008=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT 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: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f30e0 ffffffffffffffff FOLLOWUP_IP: usbvideo+3783 fffff880`00dd3783 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff88000dd3783 to fffff800031bde87 STACK_TEXT: fffff880`033bd360 fffff880`00dd3783 : fffffa80`198f0740 fffffa80`198cbc80 00000000`00000000 fffffa80`198ea3c0 : nt!IopPerfCompleteRequest+0x47 fffff880`033bd410 fffffa80`198f0740 : fffffa80`198cbc80 00000000`00000000 fffffa80`198ea3c0 00000000`00000001 : usbvideo+0x3783 fffff880`033bd418 fffffa80`198cbc80 : 00000000`00000000 fffffa80`198ea3c0 00000000`00000001 00000000`00000001 : 0xfffffa80`198f0740 fffff880`033bd420 00000000`00000000 : fffffa80`198ea3c0 00000000`00000001 00000000`00000001 fffffa80`198cbd01 : 0xfffffa80`198cbc80 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: usbvideo+3783 FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbvideo IMAGE_NAME: usbvideo.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b8f39d9 STACK_COMMAND: .cxr 0xfffff880033bc990 ; kb FAILURE_BUCKET_ID: X64_0x7E_usbvideo+3783 BUCKET_ID: X64_0x7E_usbvideo+3783 I was able to replicate the problem. Most likely the issue is with webcam drivers

Sorry, the minidump folder is empty. I could not reproduce the problem after the initial BSOD. http://social.msdn.microsoft.com/Forums/en/wptk_v4/thread/9fafc08b-e914-4094-960b-722f97a7f59b I think you might have seen this and this shows that you are right about the problem with the usb driver.

http://dl.dropbox.com/u/17753307/bootlog3.7z I uninstalled sptd.sys and updated my sata drivers and the boot process seems much more streamlined. Thanks for pointing it out. Now, I guess I would leave windows to itself. Did you have any success with the drivers flag??

@andrei When I wanted a trace, windows gave me a bsod and when I wanted a BSOD, it gave me a trace. Somehow, I managed to perform a boot trace with drivers flag and without any bsod. I am attaching for your perusal. Two drivers seem to delay the boot- fltmgr.sys and bowser.sys whose details I could not find By the way, the only thing I changed was upgrade the xbootmgr (I installed the windows 7.1 sdk(upgraded from ver 7.0)). So, see if it resolves the problem for you. http://dl.dropbox.com/u/17753307/bootlog2.7z P.S. I have observed that system activity is zero during the first 3-4 secs. No disk utilisation, no processor usage... What areyour comments on that??