This is DRIVING ME INSANE!

UKFX

UKFX

UKFX

Associate
Joined
25 Aug 2009
Posts
618
Location
London
Windows has a habbit of getting stuck on the Shutting Down screen, it is most likely however when Windows has been on for long periods of time. The symbol just swirls around and around and around for a very long time until eventually it BSODS. I don't understand why. My only thought it that it could possibly be the TP-Link WN822 Dual Antenna 300Mbps USB Wireless adapter, which is not signed by Windows, which is causing the problem but there are no guarantees. I have not yet the money to buy another adapter to check, so I have to wait.

This has pretty much been an issue since I built this computer about 6-7 months ago (I bought all the parts from OCUK :) ). Because it can't be replicated easily and doesn't always guarantee to hang and because I have so many different USB devices, like IP addresses, the combination of numbers of times I'd have to be reboot the computer would be colossal.

I've tried different software. I'd updated bios several revisions over the months. I've installed drivers for headsets and adapters, controllers, mice, etc, or I've used just Windows based ones (as I'm doing now). I can't do this with the TP-Link adapter because Windows has no PnP drivers for it, so I have to use the unsigned driver on the disc.

When the PC screwed up, in the Event Viewer all it says is: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

No help. I reinstalled a fresh copy of Windows 7 yesterday, over the months this is probably the 7th or 8th time I've reinstalled Windows, and I doubt it is a hardware issue. I don't think it is software either. Perhaps it is this driver?

I've seen threads and threads on the Internet regarding Shut Down hangs, and some fingers point towards SP1 as the culprit. However since my OEM license includes SP1 there is no way of uninstalling it.

I would move from Windows to Linux, because I love that OS, but sadly I'd like to play all my games with ease, an that's not yet a reality on Linux, so I'm stuck.

:(

Any ideas?
 
Last edited:
I had a similar issue a while back. Clearing the CMOS (removing the battery) sorted it.
Can't guarantee the same for you obviously :) Worth a try I guess.
 
Uncle Petey said:
I had a similar issue a while back. Clearing the CMOS (removing the battery) sorted it.
Can't guarantee the same for you obviously :) Worth a try I guess.
Click to expand...

I cleared the CMOS yesterday for the first time before Installing Windows 7 fresh. Made no difference sadly. :(

Fire_fly said:
Have you tried removing the wireless adapter then shutting down?

What is your system spec?
Click to expand...

Can't remember but I'll try again. I've tried so many things. Sometimes when I shut down on previous installs of Windows 7, the lights on my keyboard and mouse would go out, and I'd be unable to do anything other than press the power off button. A couple of times in the past, it'd get stuck on the Shutting Down bit and I'd press Ctrl+Alt+Del and it'd say something about memory not being written and dwm.exe wasn't terminated properly (I think) blah blah something or other. I blamed that on Fraps when Fraps was still monitoring the desktop when I pressed Shutdown in the Start Menu, but that is no concern to me now and I do not believe is the cause. To make sure all was well I tested the memory and it passed with flying colours. I don't even have Fraps installed on this fresh install of Windows 7, and it's already done it, so evidently it wasn't Fraps anyway. Again, the longer Windows is on, the more likely it is, so I doubt I'll be replying for a while, or at least until this evening.

Check my sig. :P
 
Last edited:
Have you got anything plugged into the non Intel USB 3 sockets on the back panel of the motherboard. I had a similar problem with my motherboard where it would hang for 5 mins on shutdown which I traced to Windows having issues with the VIA USB 3 controller.

Also try that TP-Link adapter in a USB 2 port, I also had issues with one not liking my Motherboard's USB 3 ports.
 
If its BSOD'ing then it will generate a dump file in c:\windows\minidump ... you can load that into a program such as 'whocrashed' which might point to the problem in the analysis screen.
 
The Wireless adapter is already plugged into a USB 2.0 Port. My headset is plugged into a USB 3.0 Port. Etron. So lame. Not sure it's that though.

If the computer later tonight has the shut down issue, or whenever the next time it does have it, I will unplug the Wireless Adapter first, if it still doesn't shut down I will leave it on that screen until the system BSODs. I tried once to understand the dumps but I never used a program for it. Thanks for the heads up. I'll get that for later.
 
Not managed to replicate the problem... well I did, but annoyingly it happened when I restarted the machine to finish a Windows update. Once it exited the Windows desktop, it started going its thing before the actual reboot and solid froze at 29% (Do not turn off your computer). Came back about 30 minutes later, sure enough, still stuck there, so no BSOD and dump. Had to restart via the reset button my Zalman Z9 Plus.

Once it booted up after the restart, it finished the update before the login screen appeared and it seems okay, so no lasting issues created from that disaster.

Just to note, when it got stuck on 29%, I unplugged the Wireless adapter from the rear USB 2.0 port. Nothing happened, so I pulled out the headset from the USB 3.0 port and the Logitech F510 controller which is in the other USB 3.0 next to it. Made no difference.

Earlier, knowing that the issues were not related to drivers, I installed the drivers for my webcam, my headset, my keyboard, my mouse and my controller.

I just need to await Windows to **** up again when shutting down to see if pulling anything out of the USBs help and to await a BSOD so I can investigate the dump.

I was sitting there, half expecting Windows not to boot properly after that dodgy stuck update thinking to myself, I really can't be assed with this again - eyeing up Ubuntu 12.04 LTS on a CD next to me. Valve best hurry up and port my game library. The moment that happens, bye bye Windows.

:@
 
Pull the stuff out then boot into windows and then shutdown to see if it still hangs that way it it will help to rule out a driver issue.
 
Hi folks. Sorry I took so long getting back but annoyingly, the computer felt like behaving itself for ages, all because I wanted it to hang on start up so I could use WhoCrashed. Thanks again tribz for the heads up on that software.

Basically, the software confirmed what I figured - a driver issue. It's preventing the computer from shutting down because the driver/device will not power off properly, so it most likely is the wireless adapter.

Here is the info WhoCrashed gave me last night:


On Mon 04/02/2013 23:36:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-16068-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800A833050, 0xFFFFF800034073D8, 0xFFFFFA800C581540)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 04/02/2013 23:36:21 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800A833050, 0xFFFFF800034073D8, 0xFFFFFA800C581540)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Not really sure what to do. I can't chance spending money on yet another wireless adapter, because I'm freakin' broke, but also because there is no guarantee that it is the adapter.

:S
 
Nope, it might not be that device. ntoskrnl is just saying "windows crashed" and is frustratingly vague. Most of my BSODs give the same info. I wish I knew more about deciphering bugchecks, but hopefully someone else can help.

Some people have said that it's the shutdown sound .wav file that causes some hangs. I don't know if you've tried disabling that?
 
Which driver are you using for the adapter?

Look here: http://www.tp-link.com/en/products/details/?model=TL-WN822N#down

If you haven't already, hit the 'Download' tab and find the driver for your version of the adapter. I'd have thought they should be signed drivers too surely?

If that doesn't work it's back to the drawing board; as it's been said it may not be the adapter but it's a good place to start.
 
Hi folks.

The other day I figured, instead of troubleshooting this problem which happens, meh, whenever it feels. Sometimes many times, sometimes not for a while, I decided to get Windows 8 Pro. It was a spur of the moment kind of thing a few days back and it only cost me £43.19. I upgraded using the Upgrade Edition DVD-ROM but did a completely clean install. Runs beautifully.

I figured, if I have to spend money on a new wireless adapter, or a powered hub, why not just chance it and get a new OS? Since power management is further improved on Windows, I figured it may handle it differently, and that perhaps the TP-Link drivers for the wireless adapter (beta ones) would be a bit different.

My wireless adapter never works off the bat, so it requires the supplied CD (on Win 7), or in this case, fortunately I had put the TP-Link Windows 8 beta drivers on my flash drive before I installed the new OS. So far so good (touch wood? lol). Everything flies beautifully and shuts down, sleeps, boots quicker and it is pretty much Windows 7 underneath the gimmicky metro UI, and yes, it can be counter productive at times. (i.e. a moment ago I want to check which screenshots I wanted to keep on team but it kept leaving the desktop to open each picture in the picture app, without the ability to scroll through the other Steam Screenshot Manager pictures, thus having to check and delete each one individually)

Overall, very pleased.

Should anything go massively wrong and I start encountering shut down issues again, I'll be sure to check back.

Thanks to everyone who contributed to helping. Much appreciated.

Peace :)
 
UKFX said:
Hi folks.

The other day I figured, instead of troubleshooting this problem which happens, meh, whenever it feels. Sometimes many times, sometimes not for a while, I decided to get Windows 8 Pro. It was a spur of the moment kind of thing a few days back and it only cost me £43.19. I upgraded using the Upgrade Edition DVD-ROM but did a completely clean install. Runs beautifully.

I figured, if I have to spend money on a new wireless adapter, or a powered hub, why not just chance it and get a new OS? Since power management is further improved on Windows, I figured it may handle it differently, and that perhaps the TP-Link drivers for the wireless adapter (beta ones) would be a bit different.

My wireless adapter never works off the bat, so it requires the supplied CD (on Win 7), or in this case, fortunately I had put the TP-Link Windows 8 beta drivers on my flash drive before I installed the new OS. So far so good (touch wood? lol). Everything flies beautifully and shuts down, sleeps, boots quicker and it is pretty much Windows 7 underneath the gimmicky metro UI, and yes, it can be counter productive at times. (i.e. a moment ago I want to check which screenshots I wanted to keep on team but it kept leaving the desktop to open each picture in the picture app, without the ability to scroll through the other Steam Screenshot Manager pictures, thus having to check and delete each one individually)

Overall, very pleased.

Should anything go massively wrong and I start encountering shut down issues again, I'll be sure to check back.

Thanks to everyone who contributed to helping. Much appreciated.

Peace :)
Click to expand...

As for your picture viewing problem, right click and set the default program for opening pictures as the "Windows Photo Viewer" rather than the Metro App.

Almost everything is there from 7, just there are Metro alternatives for somethings, but they are not replacements, so you can chose to do it the Windows 7 way :)
 
You must log in or register to reply here.
Back
Top Bottom