BSOD on Win-7 after xbootmgr restart

0

I've opened a previous question marked as duplicate of this.

I looked at the Event 100 in Event viewer as suggested by the third answer and I've installed xbootmgr from Windows Performance Analysis Tools download link of the first referenced answer.

I also followed this guide that is mentioned in other similar answers here. This was my last command before the restart.

xbootmgr –trace boot -traceFlags BASE+LATENCY+DISK_IO_INIT+DISPATCHER+DRIVERS+FILE_IO+FILE_IO_INIT+NETWORKTRACE+PERF_COUNTER+POWER+PRIORITY+REGISTRY -postBootDelay 300 -resultPath C:\Boot_Trace

I got a persistent BSOD after the restart and I managed to solved it only after a few hours (and after trying many remedies..).

I've noticed that the output file was produced as preview and was locked (initially I could not delete it - even from the safe mode) and it had a big (maybe growing) size of 7GB.

I'd like to try again the xbootmgr and the performance analysis tool anyway, if it is possible, because I need to find out what is slowing down my boot process. Is this issue with the BSOD documented somewhere and is there a way to detour it?

EDIT

This post from msdn looks relevant: is actually the DRIVERS traceflag which triggers the BSOD?

Giulio

Posted 2016-09-13T11:14:32.117

Reputation: 165

Answers

0

Yes, the DRIVERS flag is the cause on the BSOD on Windows 7 systems. I submitted such a crash dump to Microsoft. Based on my submitted crash dump they fixed it before Windows 8 was released. If you get the crash, run the command without the DRIVERS flag:

xbootmgr –trace boot -traceFlags BASE+LATENCY+DISK_IO_INIT+DISPATCHER+FILE_IO+FILE_IO_INIT+NETWORKTRACE+PERF_COUNTER+POWER+PRIORITY+REGISTRY -postBootDelay 300 -resultPath C:\Boot_Trace

The fix from Win8 was never backported to Windows 7.

magicandre1981

Posted 2016-09-13T11:14:32.117

Reputation: 86 560

only a quick question: from the analysis tool I see that (for example) in the first 110 seconds there is only the system (id 4) process and a full (almost 100%) disk usage. I don't understand what is exactly happening (since it's even before than other processes start ...) – Giulio – 2016-09-14T14:05:03.893

During that initial phase (100 seconds) the system is reading a catroot system folder... 80MB related to many updates... any thoughts if that can be optimized? – Giulio – 2016-09-15T03:14:02.700

run disk cleanup and uninstall all old updates (WIndowsUpdate cleanup): https://support.microsoft.com/en-us/kb/2852386

– magicandre1981 – 2016-09-15T16:24:19.713

Thank you again very much. Btw (crossing fingers) a defrag seems to have solved my issue :-) ... I'm taking note of your suggestion anyway – Giulio – 2016-09-15T19:05:30.637

to fix slow boot issues completely, replace a HDD with a SSD and you'll have no slow boot issues – magicandre1981 – 2016-09-16T04:20:34.977

All started after seeing a windows 7 enterprise with a spectacularly fast boot. No SSD. Do you have an idea how did they achieve this? – Giulio – 2016-10-13T07:48:49.903

you can optimize boot with xbootmgr, this works for a short time to speedup boot a lot: http://www.msfn.org/board/index.php?showtopic=140262

– magicandre1981 – 2016-10-13T15:03:47.700

Actually I continue to see what I described in my previous, above comment. So I guess there is something else, which is lasting not just for a short time... And I still wonder how to (if I can) reproduce it on a Win7 home premium, for example? (or maybe the difference it's all due to a terrible performance degradation from 0.5 to 1 TB? and windows version is unrelated?) – Giulio – 2017-05-27T10:52:25.563

to really fix slow boot, use a SSD. I use a SSD since 2012 and never see slow boots again. – magicandre1981 – 2017-05-27T15:13:17.203

Asked: 2016-09-13T11:14:32.117

Viewed: 287 times

Active: 2016-09-13T15:40:47.867