Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Amby19

  • Rank

Profile Information

  • Gender
  • Location
  • Interests
    Machine Info:

    Computer type: PC/Desktop
    Computer Manufacturer/Model Number: Home-built
    OS: Windows 7 Professional 64-bit
    CPU: Intel Core i7-4790K Devil’s Canyon Quad-Core 4.0 GHz
    Motherboard: ASUS Z97-A
    Memory: 16GB G.SKILL TridentX 2666 (PC3 21300) RAM
    Graphics Card: EVGA nVidia GTX-750
    Hard/SSD Drives: System is on 2x RAID 0 Samsung 850 PRO 256GB
    Case: CoolerMaster Storm Scout 2
    Cooling: CoolerMaster Hyper 212 EVO with 2 fans
    Keyboard: Apple Slim Full
    Mouse: Logitech Trackball Marble

Computer Information

  • OS
    Windows 7
  • CPU
  • RAM
  • Storage Size
    Greater Than 8.0TB
  • Graphics Card

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Please see my reply to -pops-, Gandalph. Perhaps you are unfamiliar with the enormous number of people for whom using a dual-boot system is essential, or at least highly desired. There are software developers that do brisk, profitable business selling boot managers. Even Microsoft has made certain their operating systems provided dual or multiple boot capabilities. You use MS's multi-boot manager every time you boot up, even if you only have a single Windows OS.
  2. Thanks for your reply and question. Please see my answer in my reply to -pops-, above. It really does make sense, depending on the situation.
  3. Thanks for the info, Boris! I've been using BootIt Bare Metal as my boot manager for years, and it's predecessors even longer. When I set it up on any of my computers, after installing it, the first thing I see is a bold warning stating that if the user is running Windows 10, one MUST disable fast startup, both in the BIOS and in Win 10's settings. So I've done that long ago, but it's important and valuable that you point this out to all Win 10 users. Thanks!
  4. Thanks for your reply, -pops- ! Here's why I pretty much have to have Win 7 on the same, primarily Win 10, computer: Because Windows 10 sometimes (not often) gets messed up so bad it won't boot. Since Microsoft decided to make getting into Windows 10 Safe Mode so annoyingly difficult, it's vastly easier to boot into Win 7 so that I can fix the problems on the Win 10 system partition instead. Also, generally speaking, having two Windows OSes installed on the same system allows you to boot into the other one when such a problem occurs on one. So why Win 7 and Win 10 as those two OS
  5. Every time I try to visit this site I get a strenuous warning message that the site is insecure because it's security certificate is invalid! I have to override these error messages / warnings in order to get here. Does no one managing this site care about this? Are they even aware of this dreadful situation? Why haven't they fixed this?
  6. This is extremely aggravating and puzzling: I have both Windows 10 Pro (build 1703) and Windows 7 Pro (service pack 2 with the latest updates) installed on different NTFS disks/partitions on the same computer (actually, I have two computers with both installed). Here's the aggravating problem: If I first boot Windows 10 and then boot into Windows 7, I get "Disk needs to be checked for inconsistency" and runs CHKDSK on most, if not all, of my dozen disks & partitions. While doing so, it always finds numerous errors and repairs them. When all those CHKDSKs are finally done (after at least 15
  7. Problem solved. I reset ALL the power profiles to their default values, rebooted, changed my selected power profile back to my custom values, and viola! -- my machine is waking up correctly again!
  8. Additional Info-- output of "powercfg –devicequery wake_armed" command: HID-compliant system controller (002) Realtek PCIe GBE Family Controller HID-compliant consumer control device (008) HID-compliant vendor-defined device (022) Logitech USB TrackMan Wheel (009) HID Keyboard Device (027)
  9. All of a sudden, my 64-bit Win 10 Pro (v 1511) desktop will no longer wake up from sleep via my USB keyboard or mouse. It worked perfectly for the last year until yesterday, no matter how many power cycles it went through. I shut it down last night, but after I booted up this morning and later put it to sleep, it would no longer wake up no matter what I do. There were no changes whatsoever since yesterday; no installs and no updates. I've tried a few power cycles since then, but the problem remains. I made no changes to my power profile. I do NOT have "fast start" or hibernation enabled, an
  10. I'm seeing the exact same problem with 32-bit Firefox 53.0 under 64-bit Windows 10 Pro (v 1511). None of the possible solutions / workarounds had any effect. I had no choice but to force a dubious "bybass". This is one of only 3 sites I've ever seen this error with, and so the presumption exists that the warning may well be legitimate. FYI.
  11. Thank you for your reply, but I regret that I'm apparently too under-informed to understand it. In any case, I'm now virtually certain that a path string that contains both UNC and relative components is syntactically invalid, so unless you or someone else informs me otherwise, that's what I'll go with. Thanks again.
  12. I've searched extensively on MSDN and elsewhere, but I can't find an answer to this question: Is a UNC path string that is also relative syntactically valid? For example, are any of the following path strings syntactically valid? (regardless of whether they make logical sense or redundant or meaningful or not): \\srv\shr1\.. \\srv\shr1\dir1\dir2\.. \\srv\shr1\dir1\dir2\. \\srv\shr1\. \\srv\shr1\.. \\srv\. \\srv\shr1\dir1\.. \\ Thanks!
  13. Of course I do, but the backup is quite recent and has the exact same problem.
  14. Here are the other two mini-dumps... BSOD Mini-Dumps 2.zip
  15. For a couple of weeks now I've been getting several different BSODs on one of my 64-bit Win 7 Pro SP1 systems. I don't think I've seen more than one at a time (i.e., the sequence I keep seeing is BSOD, reboot with CHKDSK, then the system runs fine with no issues for hours or days before another BSOD occurs). Due to upload size constraints on this forum, I could only upload 3 of the 5 mini-dumps I've experienced in the last 24 hours. In that time, I've seen 4 different BSOD types: 0x03B, 0x00A, 0x01A, and two 0x04E -- but I've seen a couple of other ones whose error codes I can't recall.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy