Your suggestion seems like a last resort not a first response, so I won't be f-disking and starting over as a first step to fix the problem. I've barely used this thing to do anything other than install software and updates and it really is the last set of driver updates from Dell that broke it.
The truth is, I'm not convinced that the same problem won't just happen again. I'm going to install the same software and the same updates which should theoretically produce the same results.
I did finally get the Windows update installed and I'll test the TiVo thing tonight and hopefully it'll just work. I have found in the past that sometimes a good Windows update will resolve instability issues.
With a brand new HP laptop, I had continuing malfunctions after applying Windows and HP updates at the very beginning. After many hours of frustration, I traced it back to a defective HP update--I did so by installing each HP update individually, and setting a Windows restore point (that I easily could roll back to)before applying each update, so that I could pinpoint which update was causing the issue. You might consider something likewise.
Hi, Monica - I must be leading a charmed life, as my V8P 64 has never crashed and blue-screened on me. It's had it share of little mysteries, but nothing that prevented it from working.
You shouldn't have to put up with this. Advice to reset is shorthand for avoiding all sorts of things. For example, we don't know in the long run how well our flash-based EMMC hard drive will handle things like "bit rot," that wonderful problem that comes from one tiny little mis-write or mis-read of a system file. We also can only guess what a virus may be sneaking around and doing. Sometimes starting over is the quickest fix. (I don't even know if fdisk is a wise idea on one of these "drives.")
I've found that the "bit rot" you speak of is sometimes resolved with a solid windows update. The one I just installed was 366 MB so it's not just a couple small fixes. We'll see... and I don't think you can f-disk one of these... that's just short hand for starting over. I'd rather go forward than backward, but if I have to reset I will.
I'm with you... If I have to, then this is what I'm going to do first... because I know when the problems started and the installations are cataloged by date so I can uninstall everything going backwards.
I did go into the Windows Update Troubleshooter which said it repaired something... But, I'm pretty sure the update that is the culprit came from Dell though. It didn't come through Windows Update. Unfortunately I downloaded and installed that Dell upgrade before I upgraded the firmware in my router and it turns out the router was definitely suspect prior to its upgrade.
Your suggestion seems like a last resort not a first response..."
I wasn't giving a "first response", I was replying to what you said in your title, "going to throw this thing out soon". Now that is what I call a "last resort"! :emotion-2:
I'm with you... If I have to, then this is what I'm going to do first... because I know when the problems started and the installations are cataloged by date so I can uninstall everything going backwards.
I did go into the Windows Update Troubleshooter which said it repaired something... But, I'm pretty sure the update that is the culprit came from Dell though. It didn't come through Windows Update. Unfortunately I downloaded and installed that Dell upgrade before I upgraded the firmware in my router and it turns out the router was definitely suspect prior to its upgrade.
My best wishes are with you! With my HP, it literally took me 20 hours of installs/uninstalls and customer service calls before I figured out what was going on (and I stress that I figured it out, not the HP techs.) and, like you, I literally was at the point of getting ready just to throw the thing away (well, to return it, as I still was within the return policy). GOOD LUCK!
So the problem has improved but is not completely settled...
I uninstalled and reinstalled the Network Driver (I uninstalled it, then realized I hadn't downloaded the driver and had to download it from another machine which was stupid.)
Now it's a bit more stable, but I still have a couple of issues...
1. The sleep function simply does not work. Period. If I boot the machine and it's connected to a WiFi then I hit the button to turn it off, then I turn it back on later connected to the same network, I expect it will not have to be rebooted in order to connect to network devices, but on this thing I have to reboot it everytime. The TiVo IP address hasn't changed in months... and it can't find it after being woken up??
2. Even after a reboot, when I run the TiVo Desktop app and successfully start downloading the programs it BSOD's once. The message is not consistent... but it does seem to be settled on two messages right now... "ATTEMPTING SWITCH FROM DPC" and "IRQ_NOT_LESS_OR_EQUAL (sdbus.sys)" Generally it only does this once, then after it kicks itself over and I start the Application again, with the downloads already in the queue to be downloaded, it seems to be able to download the programs without too much pain. Pretty quick too. But this BSOD thing cannot be good for long term stability.
Does anyone happen to know which driver is responsible for the MicroSD Slot? I apparently need to un-install and re-install it.
Hi, Monica - About the wireless, is it detecting and connecting to the wireless network (the router, not the Tivo) upon awakening? Mine does this flawlessly and routinely, at least to outside appearances. However, if I keep the router admin screen open and watch for the Dell, I see "blips" where the thing is reaching out to the network even during sleep. I've never seen a real list of what apps or events trigger this.
Jeff Leites
2 Intern
•
480 Posts
2170
0
Posted April 25th, 2014 10:00
Seems to me that something got seriously messed up at some point. You should probably restore it to the original factory condition, and start over.