ShadesOfGrey

Model: Lenovo Legion T5 tower -Windows 10 21H1 (19043.1081) -Intel Core i7 10700F -Nvidia GeForce RTX 2060 -Crucial 32GB (2x16) 2933MHz RAM -Samsung 860 and 970 Evo SSDs -650W PSU For about a week, my PC will completely lock up several minutes after waking up from sleep or hibernate. That’s the only time this happens. If I am using the PC from a fresh shutdown or restart, it will not happen. It always happens several minutes after sleep/hibernate. It completely locks up. Cursor won’t move, keyboard won’t respond. Any video and/or audio that’s playing will either cut out, slow down, stutter, etc. Unfortunately, Event Viewer doesn’t tell me anything. I look through the events for the time that my PC locked up, and it doesn’t provide me with any kind of error that I can see that helps me at all. There are no minidump files, indicating that it’s not BSODing, and thus I cannot take a look at any dmp via Blue Screen View. It’s not related to any app. It happens when the PC is idle, w/no non-system apps running. The only consistent thing is the sleep/hibernate. System Restore will not work. ☹ No matter which backup I try, I get this error: https://imgur.com/BoFLmTc I have already tried: -Memtest-No errors -CHKDSK and SFC /scannow (found and repaired errors, but didn't fix problem) -Running the most recent Windows updates -Checking Lenovo for any driver/firmware updates (none available) -Disabling hybrid sleep in Advanced Power Settings -Disabling USB Selective Suspend -Setting Processor Power Management at minimum 5% (max is still at 100%) -Swapping out USB ports. I even swapped out my mouse, because it stopped working. But the problem persisted, even with two other mice Maybe try my keyboard? Unplug my camera? There’s not a whole lot that I keep actively plugged in. I have a USB pass through cable from one of my monitors, but swapping USB ports didn’t work. I think it’s related to my stupid self temporarily enabling Windows Insider updates, because I was trying to (foolishly) see if I could pull a Windows 11 update that I could create an ISO from, to boot in to a virtual machine. People kept saying to enable Insider builds, but doing so on a Windows 10 VM simply would not offer a Windows 11 build. I think it updated to a flakey Windows 10 Insider update, which might be causing this. I wasn't trying to install Windows 11 on my main PC, just trying to get an ISO directly from Microsoft. But the problem is that with System Restore not working, I can’t roll back in any way that I know how. It does not appear to happen in Safe Mode. But seeing as I am not provided any information on what’s causing it, I have no clue what to try disabling. Must I really restart my PC dozens of times, testing out various third-party drivers and such? I really don’t want to refresh if I can avoid it. Does anyone have any idea of what I could try? Edit: After running Driver Verifier, I got some BSODs, and have uploaded the dmp files. 070521-22140-01.dmp 070521-24218-01.dmp 070521-24359-01.dmp

Event Viewer: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff81044a04e060, 0xffffef85b868f7b0, 0xffff81044f12c3b0). A dump was saved in: C:\WINDOWS\Minidump\021020-7000-01.dmp. Report Id: c94f0eb4-453f-4540-a344-91932048b186. Results of Minidump: Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\021020-7000-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 18362 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff802`5e000000 PsLoadedModuleList = 0xfffff802`5e448150 Debug session time: Mon Feb 10 02:28:35.627 2020 (UTC - 5:00) System Uptime: 0 days 1:08:43.411 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ...................................... Loading User Symbols Loading unloaded module list ................ For analysis of this file, run !analyze -v 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffff81044a04e060, Physical Device Object of the stack Arg3: ffffef85b868f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffff81044f12c3b0, The blocked IRP Debugging Details: ------------------ KEY_VALUES_STRING: 1 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10.0.18362.628 (WinBuild.160101.0800) SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd. SYSTEM_PRODUCT_NAME: GT73VR 7RE SYSTEM_SKU: 17A1.3 SYSTEM_VERSION: REV:1.0 BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: E17A1IMS.325 BIOS_DATE: 03/12/2018 BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd. BASEBOARD_PRODUCT: MS-17A1 BASEBOARD_VERSION: REV:1.0 DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump DUMP_TYPE: 2 BUGCHECK_P1: 3 BUGCHECK_P2: ffff81044a04e060 BUGCHECK_P3: ffffef85b868f7b0 BUGCHECK_P4: ffff81044f12c3b0 DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: pci FAULTING_MODULE: fffff80263130000 pci CPU_COUNT: 8 CPU_MHZ: b58 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 9e CPU_STEPPING: 9 CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_SESSION_HOST: ANALYSIS_SESSION_TIME: 02-10-2020 02:31:07.0878 ANALYSIS_VERSION: 10.0.18362.1 amd64fre STACK_TEXT: ffffef85`b868f778 fffff802`5e2ee3d7 : 00000000`0000009f 00000000`00000003 ffff8104`4a04e060 ffffef85`b868f7b0 : nt!KeBugCheckEx ffffef85`b868f780 fffff802`5e2ee2e1 : ffff8105`388a0210 ffff8104`4fd891b0 ffffc680`4f2c0100 ffffc680`4f2c0180 : nt!PopIrpWatchdogBugcheck+0xef ffffef85`b868f7f0 fffff802`5e06ba89 : ffff8105`388a0248 00000000`00000080 00000000`00000002 ffff8104`00000002 : nt!PopIrpWatchdog+0x31 ffffef85`b868f840 fffff802`5e06a7e9 : 00000000`0000000c 00000000`00989680 00000000`0002666f 00000000`00000087 : nt!KiProcessExpiredTimerList+0x169 ffffef85`b868f930 fffff802`5e1c5024 : 00000000`00000000 ffffc680`4f2c0180 ffffc680`4f2d1240 ffff8104`54d03080 : nt!KiRetireDpcList+0x4e9 ffffef85`b868fb60 00000000`00000000 : ffffef85`b8690000 ffffef85`b8689000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84 THREAD_SHA1_HASH_MOD_FUNC: 418dcf5cc7a95525fe8ac8ffec7980c508fac304 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 380ee536789d4b77d82e9ab3a599c8d978e0118f THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693 FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: 10.0.18362.628 STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys BUCKET_ID: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys PRIMARY_PROBLEM_CLASS: 0x9F_3_POWER_DOWN_e2xw10x64_IMAGE_pci.sys TARGET_TIME: 2020-02-10T07:28:35.000Z OSBUILD: 18362 OSSERVICEPACK: 628 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 1991-11-30 00:21:39 BUILDDATESTAMP_STR: 160101.0800 BUILDLAB_STR: WinBuild BUILDOSVER_STR: 10.0.18362.628 ANALYSIS_SESSION_ELAPSED_TIME: 1080 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_e2xw10x64_image_pci.sys FAILURE_ID_HASH: {4e9d0212-3878-3d83-28f5-ae5c37341dff} Followup: MachineOwner ---------

Laptop: MSI GT73RE Titan (Windows 10 Pro x64 1909) GeForce GTX 1070 As of recently (last week) will not go in to hibernate. After a restart, it usually will the first time or two. But after that, the screen will shut off, the power and GPU buttons will still be lit, and the PC will effectively hang. After 5 minutes or so, the PC will shut off. When you turn it back on, it is indeed booting up from a cold boot. nothing that I had open was saved. I have disabled virtually everything that was running at startup. I've disabled any third party modifications . I have run SFC scannow and repaired/restarted, I've checked and troubleshot power settings. I ran CHKDSK/f, restarted. I never use Fast Startup (and double checked it), so that's irrelevant. Nothing works. I checked Event Viewer, and get a "Windows failed to resume from hibernate with error status 0XC00000001" error. I Googled that, but didn't come across anything especially helpful, besides the "Probably a driver causing it" response. The timestamp is 5 minutes after I attempted hibernate. This would indicate that it fails to enter hibernate after five minutes, and BSODs. But this is all with the screen having shut off, so I don't see it. I ran whoCrashed, and the most recent crashes indicate the same error: DRIVER_POWER_STATE_FAILURE in the NTOSKRNL.EXE file. It is coming from the kernel, of course. I will post the output here, but it does not indicate any specific hardware driver that is causing it. just a generic kernel panic. This week, I've had both an NVidia GeForce driver update, and a Windows update on this PC. I could try rolling back the NVidia driver. But the WhoCrashed analysis said that no offending third party drivers were found. I was wondering if anyone had any other advice, or knew of this problem. WhoCrashed output: On Sat 2/8/2020 16:57:22 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\020820-7046-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0) Bugcheck code: 0x9F (0x3, 0xFFFFC00F6AA55060, 0xFFFFE3069123F7B0, 0xFFFFC0005A46BDE0) 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. A device object has been blocking an IRP for too long a time. This is 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 Sat 2/8/2020 16:39:07 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\020820-7031-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0) Bugcheck code: 0x9F (0x3, 0xFFFFAB0EEC5CA570, 0xFFFFE68A84E4F7B0, 0xFFFFAB0EF37CB8A0) 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. A device object has been blocking an IRP for too long a time. This is 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

I'll tell you that my Zune sounded better than my Ipod does. But damned if Microsoft couldn't unfuk their clunky Zune software.

I have a laptop, so there's not a whole lot of practical upgrading to be done. But the answer is: Whenever I have the money, and desire new hardware. In the 2.5 years I've owned this laptop, I've upgraded the primary and secondary storage drives, and RAM. I don't anticipate affording a new PC of similar caliber for some time now. So I hope to get as much use out of my current primary laptop for as long as I can.

I know I'm late to the party, here. And this has probably been said several times over in this thread by now. But Vista was awesome. it's bad reputation and critical failure had far more to do with lagging OEMs and hardware developers not keeping up with the needed hardware/driver support for Vista. Linus was dead on in that video that he made. Vista was a damn good OS, and a sexy beast at that.

Both of my laptops are Windows 10 with Classic Shell. I virtualize a whole bunch of OSs: Every major version of Windows, the newest versions of Linux Mint, Ubuntu, Arch Linux, Fedora, Slackware, FreeBSD, Solaris 9 - 11, OS X 10.6 - 10.11 (minus 10.7). I also emulate earlier versions of Mac OS: System 6 (which is the same environment as Systems 1-5, so the same basic concept), OS 7, 8, 9, 10.2, 10.4.

Thank you! I will pay mind to that in the future!

I don't know who told you that, but it doesn't even make sense. A bootable Windows 10 USB is nothing more than a media tool. It has nothing to do with product keys. In fact, if you already have an activated copy of Windows (as long as it's one of the versions of Windows that's eligible for the free upgrade) on the device in which you install Win10 via the USB, then the Win10 install will already be activated once you're done. If installing Windows clean, you need to worry about things like making sure that you install the proper hardware drivers for your device. And Win10 has even gotten better with this than previous versions. You still need to have a valid product key. If you're doing a build on a brand new PC, then you still need to buy Windows 10 for whatever price that it's going for nowadays. If you are upgrading a PC that previously came with Windows 7 on up (and it's still activated), then you can just clean install on top of that, and you should be fine.

As someone who is in to Hackintosh as a hobby, the resolution issue can in fact be fixed. Although, perhaps not in VirtualBox. I had the same problem in VBox, until I switched to VMware. There is indeed a fan made version of VMware tools for OS X guests (known as "Darwin.iso") that fixes the resolution issue. It comes bundled with the fan made Unlocker tool for VMware. You still may have to fight with things like getting sound working and/or optimizing your display depending on what kind of hardware you're using, though. Although, if you're in to it, there are plenty of pre-made OS X .vmdk files out there in internet land which work quite well. So yeah, because OS X lacks most of the major hardware drivers that Windows has, and must legally be officially unsupported for hypervisors on Non-Apple hardware, then the hardware support is far behind.

Major things I dislike about OS X: 1) I simply don't like the Aqua GUI at all. -The top taskbar and dock design can be sexy enough, but I much prefer the taskbar/Start Menu feel of Windows. -I absolutely HATE how in OSX, closing with the red X simply "minimizes" the app, but keeps the app running until you actually quit it. I further hated it when Windows 8/8.1 adopted that feature, and think that one of the best features of Windows 10 was them getting rid of that. -I hate how "minimize/maximize" work in Aqua in conjunction with the dock. A lot. And I don't think that navigating between apps is any more efficient than using the taskbar and/or Windows keyboard shortcuts. -Lots of little things, but overall, I don't like Aqua at all. 2) Far, far, far more software is available for Windows. And generally, much broader internet support is available for Windows versions of cross-platform apps. If nothing else, this is the primary reason I will always be a Windows user. 3) I absolutely hate Apple's push for a proprietary ecosystem. Consider that to use OS X, you must use it on a Mac. It's great if you want everything to be Apple-centric. But I much prefer the approach that platforms like Windows/Linux take: You got hardware? Drop our OS on it. I That was always one of Windows' big selling points: Supporting the most hardware/software it could. They aren't angels, and I'm not saying that at all. But when Windows has tried to push people in to their own ecosystem before, they got raked over the coals for it. When Apple does it, people never really flinch an eye. 4) I don't like Apple's paternalism. I prefer to "take risks" with my computer, and be held accountable for my actions. I don't need Apple to put up a few extra barriers to prevent me from running such and so app that wasn't signed in the App store, et. al. El Capitan in particular pissed me off because I had to boot in to recovery and disable rootless via terminal just to install an app. It was easy enough to do, but come on. Wanting to run a program such as CDock should not have required that. 5) Price. No one will ever convince me that having to spend that amount of money on Apple hardware would be worth it to own OS X. Things I like about OS X: 1) Being familiar with Linux/Unix, I like that the terminal is essentially the same in OS X. That's of course because as mentioned, OS X is based on a Unix-like kernel. -But Microsoft is also remedying this. As in a few months, Windows 10 is getting bash! 2) Legally, it's the only OS that can natively dual-boot and/or virtualize all of the major OS platforms (Windows, Mac, *Nix). Being a huge nerd for this kind of stuff (hell, virtualization is exactly HOW I experienced Linux/Unix and Mac), I think that's pretty cool. Of course Windows and *Nix can do all 3 as well. But doing it on a Mac doesn't require breaking any laws. 3) That aforementioned paternalism has a positive side effect: It helps lead to a more secure OS. And with OS X being frankly much less popular than Windows, there's a lot less malware that can afflict it. Sure, those numbers have drastically increased in the past five years. But consider that it took until 2016 for OS X to get its first known ransomware... Still not worth it for me. But I can see the appeal. Things I'm indifferent about: 1) I would've said that lack of a registry in OS X is nicer. But honestly, dealing with kexts can be just as easy, or just as much of a pain in the ass depending on what you're doing. 2) App installation. While structurally much different in Windows and OS X, as far as the end-user is concerned, it's the same in most areas (required motions, length of time, etc).

I'll make fun of myself here for a bit. I'm currently in school majoring in IT. So I definitely know more than the average person (helped by getting heavily in to virtualization), but still have a lot to learn. Anyway, I'm very satisfied with my home laptop, but wanted to upgrade my school one (baseline i3). Then I figured, I could just go all out and upgrade the home one again, and use the current home one for school, etc. So I was online customizing builds with the option for the new Intel Core sixth generation i7-6500U!!11. Skylake!!!! I mean, I was really pining for one of these builds, and was heavily considering buying one. Then I actually compared it to the CPU on my home laptop (i7-4710HQ). The 4710HQ beats the 6500U in virtually every category on various benchmark/comparison sites. Hell, the 4710 has 4 cores and 8LPs compared to the 6500Us 2/4. If I would have gone through with it, I would have essentially paid to downgrade my CPU. if I really wanted a beneficial upgrade, I would have needed to go for something like an i7-6700T or K (again, based on benchmark testing). Moral of the story? Just because they throw newer generations and higher numbers at you, doesn't mean that it's truly the better product. Not if you don't know the differences between the models that you're buying. The worst part is that my home laptop really is a beast for what I use it for (virtualization, light gaming, etc). I just got bitten by the bug.

Our family's first computer was a "US Computers" tower with Windows 95. We got it for Christmas 1997. I couldn't even tell you any specs, but I can promise that it was lower-end. My first computer was a Toshiba Satellite A-Series with Windows XP that I bought in August 2004. it was $1000, had an AMD Athlon, 512MB RAM, and probably some baseline integrated graphics card. Funny to think that that laptop was likely baseline back in 2004, but it was the price of a higher-end laptop nowadays (I'm guessing). I got five years out of it, finally buying a new laptop in September 2009. Hell, the screen hinges broke, so for the last year or so of its life I had to use something to prop up the screen. It was comical how little I knew about computers back then. I really screwed that thing up. Got plenty of malware, once got it so bad that I had to reformat. And I knew little about maintenance or security, so it was running really slow there towards the end. Would take Firefox like two minutes to boot up. It actually took me losing my install disc when I needed to reformat again (to escape the slowness. Again, didn't know very much) before I just realized it was time for a new one, anyway. Every computer I've bought since then has also been a Toshiba.