System UIDs Inconsistent – Android

Recently in my tinkering of system APKs, I encountered an error upon reboot: System UIDs Inconsistent.

I thought this could be from me re-adding the Gallery apk since that was the last action before the error, but it turns out it was much more.At some point, I got corruption in my data partition.  I still don’t know how this happened, but a couple identifiers let me know the culprit.

First, I reboot into recovery (TWRP) and ran a permissions fix.  Part of the output told me that it could not access /data/data/com.RiteshSahu.SMSBackupRestore.  I used this app to backup my SMS messages when changing ROMs, so I figured I would simply remove it and the data folder to get rid of the offending problem.  This was not that easy.  In Root File Explorer, there was no folder “data/data/com.RiteshSahu.SMSBackupRestore”.  Hmmm.

Rebooting back into Recovery, I ran permissions fix again to see if the directory was now cleaned out, but received the same error.  I successfully ran a data backup in order to preserve any settings I may lose, so I figured next would be deleting data and then restoring it.  The problem followed.  I even tried to reinstall the app (which I noticed the APK was gone and no longer showed as an installed app).  When trying to reinstall, I received “Unknown Error code during application install: -24” and the install failed.  Next step: Drop to terminal and see if I can remove the folder.

In TWRP, you can easily open a terminal in any folder, so I dropped into /data/data and ran “ls”.  Sure enough – there’s the folder.  Let’s delete it with “rm com.RiteshSahu.SMSBackupRestore”.  A quick “ls” showed me the folder was now gone. Reboot and voila! – No more UID error.

I know this would have been a major pain without the permissions error pointing me in the right direction.  Lesson learned to use multiple approaches to identify the problem.  Good luck to any others who stumble across this error.

Bugcheck 9f Dell e6410

Recently had ANOTHER BSOD during sleep on my Dell e6410.  Let’s see what caused it:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800748b060, fffff80000b9c518, fffffa80071d6b80}
Probably caused by : pci.sys
Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800748b060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80071d6b80, The blocked IRP

Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000f59000 pci
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02eef8d2 : 00000000`0000009f 00000000`00000003 fffffa80`0748b060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02e8a85c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`02e8a6f6 : fffff800`0302ff80 00000000`00d54724 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`02e8a5de : 000001fb`af0e19ca fffff800`00b9cc58 00000000`00d54724 fffff800`02ffd708 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02e8a3c7 : 0000007d`4901dfc1 0000007d`00d54724 0000007d`4901dfdc 00000000`00000024 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e778ca : fffff800`02ffae80 fffff800`03008cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_3_NETwsw00_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_NETwsw00_IMAGE_pci.sys
Followup: MachineOwner
---------

0: kd> !irp fffffa80071d6b80
Irp is active with 5 stacks 3 is current (= 0xfffffa80071d6ce0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    
            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    
            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa800a4a0050 00000000 00000000-00000000    
          Unable to load image \SystemRoot\system32\DRIVERS\NETwsw00.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwsw00.sys
 \Driver\NETwNs64
            Args: 00014400 00000001 00000004 00000002
 [ 16, 2]   0 e1 fffffa8009d43ac0 00000000 fffff80002e6b710-fffffa800b3c1520 Success Error Cancel pending
           \Driver\vwifibus    nt!IopUnloadSafeCompletion
            Args: 00014400 00000001 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800940daa0    
            Args: 00000000 00000000 00000000 00000000

0: kd> lm vm NETwsw00
start             end                 module name
fffff880`068a7000 fffff880`073f9000   NETwsw00 T (no symbols)           
    Loaded symbol image file: NETwsw00.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwsw00.sys
    Image name: NETwsw00.sys
    Timestamp:        Wed May 29 09:10:47 2013 (51A5FE57)
    CheckSum:         00B0B5C3
    ImageSize:        00B52000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Looking at what this module is on my filesystem, I can see that this is an Intel Wifi Link Driver. Hmmm. I just updated my drivers recently to fix the same problem. I guess Intel did not fix the BSOD issue.  Checked for an updated driver, and voila!  Let’s hope this one fixes the problem.

Lowrance flush mount kit

If anyone else is appalled at what Lowrance wants to charge for 4 screws and a template (which they call a flush mount kit and charge up to $30), then this information will definitely help.  The screws are M3 x .5 x <length needed>.  I used a 10mm length for mounting it onto 1/4″ birch.  Lowes in my area have panhead slotted screws in this size, but I couldn’t find them at Home Depot.  Total cost – $1.12.  Shove that up your fishfinder, Lowrance!

Project Millie

Earlier this year we were blessed to get a boat from our parents.  This boat has been in Lacey’s family for quite some time and is very dear to her.  She has lots of memories with this boat and camping in Arkansas.  Lacey named her Mrs. Millie after her childhood babysitter.

Now that the lake season is over, I thought it only fitting to give this old gem a makeover for next year’s season.  The vinyl was ripping in places and the carpet has gotten dull, so carpet replacement and upholstery job is in the works.  Also, we’ll upgrade the depth finder and get that fuel gauge working again.  Here are pictures of my progress.

This is a 1997 Manta Ray Sun Sport 215 w/Johnson 130 v4