[SOLVED] windows 7 blue screen crash when i shut down

Aug 27, 2019
15
1
15
0
So ever since i downloaded a program that was supposed to update my old drivers automatically, I've had this issue. When I would shut down, it would go into a blue screen and then restart. I then unchecked the box in control panel that makes my computer automatically restart. So now, when I shut down, I see he blue screen but nothing else so I need to manually shut down my computer. Help please
 

Colif

Win 10 Master
Moderator
Reactions: PC Tailor

PC Tailor

Distinguished
Herald
Welcome to the forums my friend!

So ever since i downloaded a program that was supposed to update my old drivers automatically,
There is your issue unfortunately.

Avoid driver updaters like the plague. They have a notorious habit of installing inappropriate and incorrect drivers. Always update the drivers yourself manually via the manufacturers website.

Unfortunately your options can be a little difficult, as usually it's hard to undo the changes of these driver updaters as they bulk update a ton, and there's no way of knowing which ones are causing the issue.

Best thing you can do is to revert to a system restore prior to you using the program. Equally you could try trawling through all of your drivers one by one and update them directly from the manufacturers website (but there will also be plenty of drivers it's probably updated that you don't even see).
 
Aug 27, 2019
15
1
15
0
Thanks for the help but I have another problem: to restore my computer, it says I need to have a restore point I think which I never made, can I still revert the changes before I updated my drivers?
 

PC Tailor

Distinguished
Herald
Thanks for the help but I have another problem: to restore my computer, it says I need to have a restore point I think which I never made, can I still revert the changes before I updated my drivers?
Without a restore point or a backup - no.

I'll be honest, in plenty of cases people end up clean installing W10 again after a driver updater causes this, because it can be so hard to nail the cause.

I'd be tempted to run in safe mode first and see if the issue persists there.
If not, a clean boot state (https://support.microsoft.com/en-gb/help/929135/how-to-perform-a-clean-boot-in-windows )
 

PC Tailor

Distinguished
Herald
Aug 27, 2019
15
1
15
0
After going through all of the steps, I found multiple files made from different dates from the 26 to the 29th. They all end with dmp but I'm not sure how I'm supposed to copy them to documents. I can't seem to be able to copy paste them onto docs.
 

PC Tailor

Distinguished
Herald
After going through all of the steps, I found multiple files made from different dates from the 26 to the 29th. They all end with dmp but I'm not sure how I'm supposed to copy them to documents. I can't seem to be able to copy paste them onto docs.
We really probably only need the last 3 or so for now.
Just upload them onto a file sharing site of somekind then paste the link here.
 

PC Tailor

Distinguished
Herald
I have ran the dump files and you can see the full reports here:
https://pste.eu/p/ebFz.html SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
https://pste.eu/p/DhQY.html SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Summary of findings:
BugCheck 1000007E
Probably caused by : iusb3xhc.sys ( iusb3xhc+4f850 )

Bugcheck Description:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
"This bug check indicates that a system thread generated an exception that the error handler did not catch. To interpret it, you must identify which exception was generated.

About your bugcheck:
"This is typically driver based and therefore you should reference the third party modules loaded to check which ones may be misbehaving.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.

Check with your hardware vendor for any ACPI or other firmware updates. Hardware issues, such as system incompatibilities, memory conflicts, and IRQ conflicts can also generate this error. Confirm that any new hardware that is installed is compatible with the installed version of Windows.

You can also disable memory caching/shadowing of the BIOS to try to resolve the error. You should also run hardware diagnostics, that the system manufacturer supplies."

Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.

Both dump files blame iusb3xhc.sys which is:
iusb3xhc.sys11/05/2017IntelIntel USB 3 Host extensible Driver

I'd be tempted to disable these using Autoruns (you can find link to this on the reports) and see if the issue repeats. Are you using USB 3 ports frequently?
 
Aug 27, 2019
15
1
15
0
So I disabled iusb3xhc.sys and nothing really changed because when I shut down my computer, it went into bsod again. However, I don't know if it's related but my mouse doesn't work anymore after starting up my computer again.
 

PC Tailor

Distinguished
Herald
So I disabled iusb3xhc.sys and nothing really changed because when I shut down my computer, it went into bsod again. However, I don't know if it's related but my mouse doesn't work anymore after starting up my computer again.
Do you have a dump file for the BSOD?
And just odd that all your dumps blaming USB - and going to shutdown definitely sounds like a driver misbehaving during the shutdown procedure.
 

PC Tailor

Distinguished
Herald
Can you post it?
I'd half suspect the driver updater you've used has installed incorrect or inappropriate drivers which is leading to your issue.

I'd almost be suggesting a clean install will guarantee a fix, but we may be able to narrow down what the cause is.
 

Colif

Win 10 Master
Moderator
Also helps to know what he has attached, like there are Samsung printer drivers from 2005

shame 3rd party updater wasn't driver booster as it at least creates a restore point before it installs the wrong drivers.

you would need to compare installed drivers against https://support.dynabook.com/support/modelHome?freeText=PT44GU-00T003&osId=3333616 to see what might be the problem

or you can run driver verifer, it will check all your drivers and hopefully not cause a boot loop - https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier - it will cause a BSOD but that is its job. Make bad drivers crash.

it should find the buggy ones.
 
Last edited:
Reactions: PC Tailor

Colif

Win 10 Master
Moderator
I don't get exactly what you want me to post but here's something. By the way, I found out that when I click the "add bluetooth device", it instantly goes into bsofhttp://prntscr.com/p077vm
He wants the dump files you have.
copy all those dumps in your screenshot to another folder
zip the files and upload the zip to a file sharing website and show a link here, and PC will be able to convert them and we see whats going on.

your bluetooth drivers are from 2019, I wonder if they actually match your hardware or were mistakenly installed by the software updater.. or have you updated them since we started this thread?
 
Last edited:

Ketchup79

Notable
Aug 7, 2019
1,449
133
1,140
75
Which driver update program did you use? Not to waste your time here, but did you look and see if the program keeps a record of what it installed and when? Might be easier than tracing dump files.

Also, WhoCeashed can give you a general idea of what your error is about. The free version can be pretty general on some issues, more specific on others. It all depends on what the issue is:

https://www.resplendence.com/whocrashed
 
Reactions: PC Tailor

PC Tailor

Distinguished
Herald
Your google drive folder is blocked - you have to enable file sharing on the files.

I would tend to avoid using whocrashed in most cases, it doesn't really give as much info, and often blames the wrong things. That and obviously it only translates, whereas depending on the bug check, we can run some more commands to get more info - If you can give sharing access, I can run a program to run the report.
 
Last edited:
Aug 27, 2019
15
1
15
0
I don't remember the name of the driver updater... I also deleted once I used it... And for the dump files, I think I made it possible for others to get access to it
 

PC Tailor

Distinguished
Herald
Being as there were many dumps, I have simply run 4 of the most recent ones as this should give us enough inof for now (i've selected a couple different time periods just to show the difference over time) and you can see the full reports here:

Dump 1: https://pste.eu/p/OMf3.html (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
Dump 2: https://pste.eu/p/NSsy.html (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
Dump 3: https://pste.eu/p/R7yW.html (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
Dump 4: https://pste.eu/p/V5Sg.html (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)

Summary of findings:
BugCheck 1000007E
Probably caused by : iusb3xhc.sys ( iusb3xhc+4f850 )

Bugcheck Description:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
"This bug check indicates that a system thread generated an exception that the error handler did not catch. To interpret it, you must identify which exception was generated.

Common exception codes include the following:
0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.
0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
Ntstatus.h file that is located in the inc directory of the MWDK contains all references"
About your bugcheck:
"This is typically driver based and therefore you should reference the third party modules loaded to check which ones may be misbehaving.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.

Check with your hardware vendor for any ACPI or other firmware updates. Hardware issues, such as system incompatibilities, memory conflicts, and IRQ conflicts can also generate this error. Confirm that any new hardware that is installed is compatible with the installed version of Windows.

You can also disable memory caching/shadowing of the BIOS to try to resolve the error. You should also run hardware diagnostics, that the system manufacturer supplies."

Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.

All of your dumps are all blaming:

iusb3xhc.sys
11/05/2017IntelIntel USB 3 Host extensible Driver

That and this module is in your process stack leading up to the crash.
I thought this had been disabled from the last round?
Also what peripheral USB devices do you have plugged in?
There are a wealth of other drives, but would stick to the obvious one for now.
BIOS is also from 2015
 
Last edited:

ASK THE COMMUNITY