Wintel W8 Pro Mini Pc

[Shameka Cretsinger]

Ihad only mini-dumps enabled (I've changed it since, but have not seen a BSOD yet) and looking at my "C:\windows\Minidump" directory I see 11 mini-dumps from the last 6 months, about two bug-checks a month

Running windbg and friends from the "Debugging tools for Windows" results in error "0n1392" which I read in short as "corrupted".Looking into the file with a hex editor, I tend to agree with the diagnosis as the top part of the file is sprayed with the ASCII string "PAGEPAGE".

Looks like you're having some sort of hardware failure. This would account for the BSODs and for the mini-dumps not being saved properly. It might be a good idea to find a Linux live CD and boot it. Preferably one with diagnostics/testing programs on it. It might help you pin down what's going wrong.

I am running Ubuntu server 19 on a Z83 (similar CPU) with 4 GB RAM / 64 GB eMMC / 64 GB SSD and it works well. The only thing you have to add is an HDMI dongle, as the mini PC does not boot without a display connected. The OS is installed on eMMC, maria db is writing to SSD.

I try to remember, but I think you have to have a 64 bit EFI to run a 64 bit Linux, not sure though.

There are several variations of these boxes, the one I have with 4 GB memory had a 64bit Windows on it.

I have an SD slot, and I planned to use it for my files and applications, but it seems that the OS directory is not enough for the OS alone, so the question is what can I do? I have already run the disk cleanup, deleted temporary files, etc. How can I minimize the storage space consumed by Windows?

The Windows feature updates will consume approximately 3-5GB once ready to install, but the download of the feature update itself is done via Windows update and can consume a lot more in preparation for the update.

Once it has opened look towards the bottom right of the tool for the "Clean up system files" button and click it. This will then scan again but this time the "files to delete" list will be populated with feature updates and windows update cleanup amongst others.

Do you have any specific needs that require the PC to be running Windows 10? Perhaps you could instead install a lightweight Linux distro such as Lubuntu? I ask because I was in the same boat as you. Bought a super cheap Lenovo netbook with 32GB eMMC and 2GB Ram. I thought it'd be fine since my only intent was to use it for browser based items.

However, the Windows update process was always consuming ALL of the 32gb of space but still never enough space to actually do the update. That combined with the limited ram meant the thing moved like a slug.

I tried many of the techniques mentioned in other answers here. But eventually got tired of constantly fighting the battle and decided I didn't need Windows 10 on this machine. I wiped Windows and installed Lubuntu. It's been great, meets my needs for this machine, and it runs much better now.

As noted by @spikey_richie, the likely culprit is your winsxs or (Windows Side-by-Side directory). Every patch or update that happens on the system gets duplicated and stored in this directory. It is Windows way to provide rapid roll-back of a patch or update in case of error/component failure. It can get very large (dozens of GBs) and grows over time.

Here are some very complete referenes talking about why it happens and how to resolve the size. This removal of older files is fine, unless you have system issues because removing the system backup will limit your ability to recover or roll back to a known-good state.

I have a Mini-ITX Intel DH61AG mobo w/ an Intel i3 processor and 8GB of 1600MHz DDR3 RAM. Anyways, this computer has been crashing kind of frequently. It is not an OS problem, as I have used Ubuntu (and had kernel panics), Windows 7, and Windows 8. Each of these OSes have had problems, so I ran a HDD check, and I know it is not a heat issue because I tested the processor for a few days when I first put the computer together. When I ran memtest86+, however, I got an error - so I did individual testing, and both chips came back good, did a really intense test with both of them again (took half a day), and no errors. So, I still think the problem could be RAM, but I am not sure - I tested it pretty extensively (might let it run all night again tonight)... which brings me to my point.

Could someone explain to me (in simple terms if possible) how to READ the minidump files of Windows computers? I've tried before with a guide I found online, but failed miserably. I'm fine with installing the software, I will probably need it sometime in the future as well. I have seen a few other posts on SU that just ask people to post minidump logs, but I feel as if that is too localized. Would someone be able to explain this?

The minidumps contain information about the process that crashed. If you don't have the source code for that module then the minidump might not help you much. It contains information about the stack in each thread of a process at the time of crash, and a bunch of other stuff.

That said, you can open these in Visual Studio. I also did a very quick Google, just in case I'm missing something (being a programmer, I tend to think like a programmer a lot and I start imagining that minidumps are just for programmers). Found this:

Talks about installing Microsoft Debugging Tools to analyse the minidump. Check that out, and see if you can get any useful information out of it. At the very least, the name of the module that crashed might help you.

If you suspect it's an intermittent RAM problem (and especially if it's been sitting in the computer for many years), you should try reseating (remove and reinsert) the RAM and run your tests again. With a bit of luck, that might cure it.

A kernel network mini-redirector driver implements a number of callback routines that are used by the Redirected Drive Buffering Subsystem (RDBSS) to communicate with the driver. In the remainder of this document, a kernel network mini-redirector driver will be referred to as a network mini-redirector driver.

When a network mini-redirector driver first starts (in its DriverEntry routine), the driver calls the RDBSS RxRegisterMinirdr routine to register the network mini-redirector driver with RDBSS. The network mini-redirector driver passes in a MINIRDR_DISPATCH structure, which includes configuration data along with pointers to the routines that the network mini-redirector driver implements (a dispatch table).

A network mini-redirector can choose to implement only some of these routines. Any routine that is not implemented by the network mini-redirector should be set to a NULL pointer in the MINIRDR_DISPATCH structure passed to RxRegisterMinirdr. RDBSS will only call routines implemented by the network mini-redirector.

One special category of routines implemented by a network mini-redirector are the low I/O operations that represent the traditional file I/O calls for read, write, and other file operations. All of the low I/O routines can be called asynchronously by RDBSS. A kernel driver for a network mini-redirector must make certain that any low I/O routines that are implemented can be safely called asynchronously. The low I/O routines are passed in as an array of routine pointers as part of the MINIRDR_DISPATCH structure from the DriverEntry routine. The value of the array entry is the low I/O operation to perform. All of the low I/O routines expect a pointer to an RX_CONTEXT structure to be passed in as a parameter. The RX_CONTEXT data structure has a LowIoContext.Operation member that also specifies the low I/O operation to perform. It is possible for several of the low I/O routines to point to the same routine in a network mini-redirector driver since this LowIoContext.Operation member can be used to specify the low I/O operation requested. For example, all of the low I/O calls related to file locks could call the same low I/O routine in the network mini-redirector and this routine could use the LowIoContext.Operation member to specify the lock or unlock operation requested.

RDBSS also assumes asynchronous operation for a few other routines implemented by a network mini-redirector. These routines are used for establishing a connection with a remote resource. Since connection operations can take a considerable amount of time to complete, RDBSS assumes these routines are implemented as asynchronous operations.

RDBSS assumes that all routines implemented by a network mini-redirector other than the low I/O and connection-related routines are based on synchronous calls. However, this is subject to change in future releases of the Windows operating system.

All of the routines implemented by a network mini-redirector return an NTSTATUS value on completion. Most routines return STATUS_SUCCESS on success or an appropriate NTSTATUS value. In addition to return values specific to a particular routine, there are two generic categories of errors that can be returned for most routines :

STATUS_USER_SESSION_DELETED

The user session on the server has been deleted. The session may have timed out, the server may have been restarted causing all existing user sessions to be deleted, or an administrator on the server may have forced a delete of the user session .

I just finished this mini quilt for the Fab Little Quilt Swap on flickr. I know I said I wasn't doing any for a while, but the swap mamas used flattery to their advantage, and here is the finished product, "Stained Glass Windows"!!! I had a great time making this and it is my first time sewing curves--a swap item may or may not be the perfect time to try something like this. The jury is still out.I signed up for Rachel's Curves Class after seeing a few of her excellent preview projects, and figured it would be easier to take the plunge with a little hand holding. I think curves are just like anything else--zippers, sewing with non-cotton fabrics, etc. They seem scary, you try it out, realize it isn't too difficult, and go on from there.Stained Glass Windows was inspired by a scrappy color wheel from Rachel's class, and a suggestion from Elizabeth to invert the color wheel similar to a doll quilt in progress by Norma of Petit Design Co. The quilting is perhaps my favorite part--I outlined the "cathedral window" three times, both inside and outside the window. Note: the map fabric is from Etchings by 3 Sisters from Moda.I used one of my favorite Loulouthi prints for the back,and the polka dot binding is from Cosmo Cricket's Circa 1934.Linked to Finish it up Friday @ crazymomquilts Finally--can you believe this was made almost entirely of scraps? Excited to link up to Rachel's Festival of Scrapiness! QuiltsKatie BlakesleyMarch 13, 2012mini quilt, modern quilt28 Comments Facebook0 Twitter Pinterest0 0 Likes Previous Flea Market Fancy // Works in Progress Favorite Things, Works In ProgressKatie BlakesleyMarch 14, 2012flea market fancy quilt, modern quilt, works in progress12 Comments Next My Quilt is on the Moda Bake Shop Today! Patterns, QuiltsKatie BlakesleyMarch 12, 2012 ka...@swimbikequilt.com Hours Disclosures Swim Bike QUilt NewsletterGet a Free Star Bright Quilt Pattern, and subscribe for tutorials, announcements,

quilt along news + tips for starting [and finishing] your quilts.

3a8082e126