Touchscreen Issues when plugged in?

So I'm having (what seems to be) a unique issue. When I have my iPhone plugged in to the wall charger, my touchscreen is about 50/50. Texting becomes a nightmare, because the touchscreen doesnt recognize my inputs. I can push the spacebar, and it thinks I pushed the large EDIT button at the top. Cant even come close to putting sentences together, because its just not calibrated. Unplug it and it works perfectly fine.
ANYONE had this issue yet, or do I just need to make a phone call and exchange?? This issue bugs me almost as much as the proximity sensor making me start FaceTime, mute people, and hanging up on people... but no DEATH GRIP problems here!

Try unplugging the charger from the wall outlet, turn it 180º, then plug it in again. (The prongs will now be in the opposite holes in the wall outlet.) If it now works properly, then the charger is defective, and has some current leakage from the high voltage input to the low voltage output. This could be dangerous, and the charger should be replaced.

Similar Messages

  • Touchscreen inaccuracy when plugged in.

    I've found an issue when my iphone 4s is plugged in, the touchscreen is inaccurate and non-responsive at times. I've been able to reproduce it, and have read several other postings on the issue. The solution in the forums (which works for me) is to touch the metal bezel with your hands. While that works, I have a case on my phone, and I don't want to take the case off every time I want to use my phone when its plugged in. Apple doesn't have a fix for this? I see the issue dating back to the iphone 3.

    Absolutely. I found that if you touch the band around the phone with a finger, the screen reacts normally.
    Haven't quite pinned down the problem yet but must be an earthing issue.
    I've tried a non-Apple cable and two Apple cables and they all behave in the same way:
    All three cables (and the screen) don't work if you don't touch the outer band when plugged into my cheap mains plug.
    All three cables (and the screen) work correctly when used with a computer's USB port.
    Tomorrow I'll try the Apple mains plug that came with the iP4.
    (Having said that though, my car connector works fine and I can operate it one handed - Griffin PowerJolt SE)

  • L22-S1192 sound issue when plugged in

    It only happens when using amplified audio outputs headphones are ok. It makes a humming like it has feedback only happens when plugged in though un plug it and its fine i hate that i cant use my 2.1 speakers to watch movies with friends

    I am thinking its a gound loop but if it was in a car audio id know what to do

  • Wireless issues when plugging into Mac display

    I have noticed that no matter where I am in the house, my Macbook Pro works with my Airport just fine. But when I plug the laptop into a 24" display, my wireless signal does one of two things: it drops a connection, going from full strength to nothing and back again, bouncing back and forth in a slow rhythm, or it will give me a huge drop in strength. Anybody have any idea why this is? Your help is greatly appreciated.

    I also have the same issue, specifically similar to that of DimBimbleby, since I am using my MacBook (2008) connected to one of the Apple 24" LED Displays via an Altona converter in the mini-DVI port. The laptop works excellently when not plugged into the display, as do my DVD player (streaming Netflix) and my AppleTV (will never figure out why I bought that) - as soon as the monitor is plugged in, the internet is either extremely sluggish or does not work at all. It took me a bit to figure out that it was only after the display is connected (moved both things all around the house of course). Does anyone at all have ANY idea how to fix it or improve it?? It's really frustrating and I certainly did not pay all that $$ for the display for it not to work with internet. I recently sold an older style 20" ACD Monitor which never had a single issue working with the internet. I have a Linksys Wireless-N router which is not the greatest ever but works well with everything else. Please help!!!!!

  • RAM issues when plugging in external devices

    When I plug external devices in such as a USB drive, iPhone or a Firewire external HDD the RAM usage on my Mac shoots up beyond normal levels. This has only started happening recently.
    Say for example I plug in my iPhone to sync it. With only iTunes running (no other programs in the dock at all), I get the force quit box come up asking me to close programs down because it doesn't have enough RAM.
    I don't get the force quit box come up when I plug USB devices in but the Mac still becomes nearly unusable.
    Any ideas how to reset or fix this RAM problem (or whatever else it might be)? Everything else is fine, I can numerous programs that require lots of RAM with no problem at all.

    Try resetting the PRAM and resetting the Systems Management Controller.
    PRAM
    1. (Re)start and immediately press & hold the CommandOption+PR keys
    2. Listen for two startup chimes.
    3. Release all keys and let the Mac start normally.
    SMC
    1. Shut down the Mac and disconnect all attached cables; power, USB, FireWire, Ethernet, etc.
    2. WAit 15 seconds.
    3. Reattach the power cable and a USB keyboard & mouse.
    4. Restart the Mac.
    5. Reattach all hot attachable peripherals.
    Dah•veed

  • Battery issues when plugging / unplugging

    Hi all, i noticed that if i use my laptop without battery then i plug it back on it doesn't recognise it
    ┌─[smau @ neplero]-[~]
    └─[14:04:09]-[ $ ]> acpi -V
    Battery 0: Discharging, 0%, discharging at zero rate - will never fully discharge.
    Adapter 0: off-line
    Cooling 0: LCD 1 of 10
    Cooling 1: Processor 0 of 7
    Cooling 2: Processor 0 of 7
    as you can see, battery is 0% but i'm running on battery and it's not 0% (my status bar tells me its +-4320000%...) why is there so many things wrong with battery? and why can't i see hours and minutes left (it says just N/A) but only percentage? thanks

    The battery indicator is well know for being inaccurate.
    Try this test.
    How to accurately determine your iPod battery life.
    When connected to the charger, the iPod still runs on battery power (it doesn't take the supply straight from the mains), so yes, it could be symptomatic of a bad battery.

  • Touchscreen (digitizer) inaccuracy when plugged in.

    All,
    I've been noticing that after my iPhone 4 is plugged in for a while, the touchscreen no longer registers touch instances accurately. This is particularly frustrating because I plug my iPhone in while I'm using it for gps navigation in my car and it's virtually impossible to manipulate anything in the application due to the touchscreen inaccuracy. Has anyone else had this issue? Is Apple aware?

    Absolutely. I found that if you touch the band around the phone with a finger, the screen reacts normally.
    Haven't quite pinned down the problem yet but must be an earthing issue.
    I've tried a non-Apple cable and two Apple cables and they all behave in the same way:
    All three cables (and the screen) don't work if you don't touch the outer band when plugged into my cheap mains plug.
    All three cables (and the screen) work correctly when used with a computer's USB port.
    Tomorrow I'll try the Apple mains plug that came with the iP4.
    (Having said that though, my car connector works fine and I can operate it one handed - Griffin PowerJolt SE)

  • My MacBook Pro just shut down without notice. It had about 40% of the battery life. It will not turn back on and I noticed when plugged in the little light on the power cord is blinking orange, not a solid green like normal.  Anyone have this issue before

    MacBook Pro just shut down without notice. It had about 40% of the battery life. It will not turn back on and I noticed when plugged in the little light on the power cord is blinking orange, not a solid green like normal.  Anyone have this issue before?  I've only had this for about 3mos.  I called apple support. They tried one thing then said I have to take to the apple store. Unfortunately I don't have one nearby. So before I travel an hour+ away I thought is give it a shot on here. Thank.

    Hi S,
    Did they have you try an SMC Reset: http://support.apple.com/kb/HT3964?

  • I just had 2 MacBook pro's stop working completely.  No previous issues.  Won't even turn on when plugged in.

    I just had 2 MacBook pro's stop working completely.  No previous issues.  Won't even turn on when plugged in.  Any ideas?

    See if a SMC reset will breath life into them:
    https://support.apple.com/en-us/HT201295
    If not, make an appointment at an Apple store genius bar for a FREE evaluation. Warranty status is irrelevant.
    Ciao.

  • Solved! NTFS-3G Issue on Mac Maverick when plugging a hard drive via USB

    This issue can be solved in less than 5 minutes, but it is not free. if you are willing to sort it out once and for good, read on, it’s well worth it!
    “I love my Mac!”, that is a common expression you might hear everyday, but not many people are willing to admit that Macs really suck and become a nightmare the moment you plug a hard drive, new or filled with those important files, via USB. Apparently most commercial backup hard drives are formatted with Windows file systems by default and Macs will only be able to read the contents of these discs after properly formatting them on Mac.
    I have 3 external hard drives filled with mp4 movies and uni files, and formatting is absolutely a no-no here. So I was forced to open those files using the Windows virtual machine (via Parallel) in my Mac, which really ***** too. According to the many websites I visited for solution, you either had to buy some apps or die with that NTFS-#G error message when plugging a USB hard drive. There is also an encouragement to either format the drives on Mac before you can use, and again, in my case, this is impossible.
    “NTFS-3G could not mount /dev/disk1s1 at /Volumes/Vuakalevu because the following problem occurred: dyld:
    Library not loaded: /usr/local/lib/libfuse.2.dylib Referenced from: /usr/local/bin/ntfs-3g
    Reason: image not found”
    I think I just solved that issue once and for all, but nothing comes for free, as in anything with Mac computers. The “Paragon NTFS for Mac OSX”, which cost me $19.99 from their official website seems to have sorted me out, now I can plug any hard drive, no matter the format, and Maverick will read it as it should (read and write). Well worth it, and i do recommend it.
    This was originally posted in my website, so feel free to come around if you like.
    http://journalsfromoceania.com/solved-ntfs-3g-external-drive-issue-solved-for-19 -99/

    Hi Linc Davis, yep! i did everything according to read me, tried all free ones, only made it worse. uninstalled the whole lot, didnt work either. I read around in forums the same thing "simply remove the app causing this issue and it will be sorted" didnt work for me. this Paragon sorted me out after 2 years of external hard drive issues. Im not sure if your reply was an assertion or a question though. cheers

  • Firewire issues (HD dismounts when plugging in other devices)

    I've got a brand new Mac Pro with a Seagate 1T external firewire drive connected to the firewire port on the back of the computer. I also have a Lexar firewire CF card reader plugged into the firewire port on the front of the computer. Whenever I insert a CF card into the reader the external drive drops off with the error that it was not put away correctly. When I eject the card the external appears back on the desktop. I've had the same thing happen when plugging in an old iPod that uses a firewire connection. When it appears on the desktop the other Firewire device drops off. Any ideas on how to troubleshoot?

    Try resetting the PRAM and resetting the Systems Management Controller.
    PRAM
    1. (Re)start and immediately press & hold the CommandOption+PR keys
    2. Listen for two startup chimes.
    3. Release all keys and let the Mac start normally.
    SMC
    1. Shut down the Mac and disconnect all attached cables; power, USB, FireWire, Ethernet, etc.
    2. WAit 15 seconds.
    3. Reattach the power cable and a USB keyboard & mouse.
    4. Restart the Mac.
    5. Reattach all hot attachable peripherals.
    Dah•veed

  • Brightness issue (when unplugging/plugging battery cable)

    Hi,
    on my laptop, when unplugging the battery cable, the screen becomes darker.
    When plugging it back, the screen becomes brighter, but not as bright as from start.
    To restore my previous brightness, I need to use xbacklight (or xrandr --brightness).
    Even, xbacklight -get is enough to restore the correct brightness.
    I don't have any of cpufrequtils, pm-utils, powernowd, laptop-mode-tools or any package to manage the power.
    My video driver is intel (i915).
    Do you have any idea of: what's causing the screen to change brightness when plugging/unplugging the battery ?
    Why, after plugging the battery back, it doesn't restore its previous brightness until I try to get the brightness from the os ?

    Hi, if you don't use any of the acpid, pm-utils, laptop-mode-tools, etc. "magic", it seems to be a BIOS feature. You may try to disable it via setup, or try to find a kernel module specific to your NB manufacturer/model (eg. dell-laptop) to override the ACPI BIOS.
    Last edited by laloch (2011-12-09 14:12:08)

  • Mid 2009 17" MacBook Pro battery shutdown issue when waking from sleep.

    My unibody 17" MacBook Pro occasionally shuts down on waking from sleep when it isn't plugged in.
    When I open the lid to wake it I can hear the hard drive and fans starting to spool, and then the next second it's off and silent. The laptop doesn't mind being turned on again after it does this and might go a week without doing it again, equally it might do it next time I try and wake it from sleep. It does this regardless of battery charge level.
    coconutBattery says the battery still has 86% of its designed capacity, and I haven't noticed anything else untoward regarding battery charging or performance when in use.
    So my question is two fold:
    1) Does it sound like the battery's internal processor is malfunctioning, or could it be something else?
    2) If it is the battery's internal processor, will replacing the battery replace the processor, or are they fitted separately (in defference to the 'internal' part of its name)?
    Cheers,
    James
    nb. just in case it makes any difference, the laptop is a 17" Mid-2009 MacBook Pro, 2.8GHz Core 2 Duo with 4Gb Ram running OSX 10.7.3

    James
    I have had issues when i press the space bar from sleep, sometimes it wakes but others i'm forced to power it on with the power button.
    Is this similar to anything you've experianced?
    Its so inconsistantly these days, but i'm also connected to an external screen.

  • Decided to update iphone 4 to ios 5.1 and mid update it froze and the screen is black.  Phone does not respond to any combinations of home and power buttons, when plugged into computer it does not see it is plugged in, any ideas?

    Decided to update iphone 4 to ios 5.1 and mid update it froze and the screen is black.  Phone does not respond to any combinations of home and power buttons, when plugged into computer it does not see it is plugged in so I cannot restore or anything.  Looks like the screen is on it's just unresponsive and black obviously.  Has anyone had this problem?  I was updating via wifi right in front of my router and my computer.

    Spoke to a "senior advisor" in the Apple TV department.  Her suggestions:  change channel in router to minimize/eliminate wifi interference from other users; move router away from any metal - i.e., DVD player, phone modem, etc.; keep router away from wireless 2.4 gH phones, which are "notorious" for crashing wifi routers.  So she confirms that the problem is one of connection to router suddenly dropping out.
    My own feeling is that none of these fixes will do the trick, because it seems pretty clear that there is a hardware component here - the timing of the drops seems like an overheating issue.  It takes 35-40 minutes for the box to warm up enough for the first drop; then each consecutive drop happens quicker than the one before, as it heats up more.  Each time it drops, its tiny brain gets a little more scrambled; last night it finally wouldn't start up again at all.
    My suggestion is that everyone who is experiencing this problem, please call Apple tech support and ask to speak to a senior advisor in the Apple TV department.  Make them aware of this problem!

  • BSOD when plugging into Dynadock U3

    Hi There,
    We have a wide number of Toshiba Dynadock u3.0's working with a number of Sony Vaio Laptops. In the main they have worked pretty well, and have improved over time as new releases have come out.
    At the moment we are rolling out the new Sony Vaio Pro laptops, and Dynadock is almost essential for users because the Vaio Pro's do not have an ethernet adapter. We are also downgrading them to Windows 7 from Windows 8 as we are not ready for Windows 8 on a large rollout, and holding off till 8.1 goes live.
    We have had a couple of blue screen of deaths on 2 Vaio Pro's when plugging into the Dynadock. Both have the latest dynadock drivers, and we have obtained the memory dump for the machines. Before they were plugged in, they were on the WLAN in the office.
    The other half a dozen devices we have in use at the moment have not yet reported this issue, and the BSOD has appeared on these two devices only once each, but I was asked to report this issue on these forums to just confirm there is no obvious issue with the Dynadocks.
    In the meantime we have 3 other Vaio pros which are being tested and have not yet experinced the same issue.
    Memory Dump below:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Scratch\100813-9796-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`020dc022?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00226022?
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.22411.amd64fre.win7sp1_ldr.130801-1934
    Machine Name:
    Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a76d0
    Debug session time: Tue Oct  8 11:46:36.236 2013 (UTC + 1:00)
    System Uptime: 0 days 3:57:23.966
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000009F, {4, 258, fffffa800672db50, fffff80000b9c3d0}
    Unable to load image \SystemRoot\system32\drivers\DNPFW.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for DNPFW.sys
    *** ERROR: Module load completed but symbols could not be loaded for DNPFW.sys
    Probably caused by : tcpip.sys
    Followup: MachineOwner
    0: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
        subsystem.
    Arg2: 0000000000000258, Timeout in seconds.
    Arg3: fffffa800672db50, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c3d0
    Debugging Details:
    DRVPOWERSTATE_SUBCODE:  4
    IMAGE_NAME:  tcpip.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  51d78659
    MODULE_NAME: tcpip
    FAULTING_MODULE: fffff88001800000 tcpip
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff880`03507ed0 fffff800`032cb972 : fffffa80`0672dc10 fffffa80`0672db50 00000000`00000000 00000000`0000000d : nt!KiSwapContext+0x7a
    fffff880`03508010 fffff800`032dcd8f : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`01801d60 : nt!KiCommitThreadWait+0x1d2
    fffff880`035080a0 fffff800`03332ee6 : fffff880`01801d00 fffff880`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
    fffff880`03508140 fffff880`0180289a : fffffa80`07609a10 fffffa80`071db1a0 00000000`00000000 fffffa80`000e0082 : nt! ?? ::FNODOBFM::`string'+0x12ef6
    fffff880`035081b0 fffff880`0174f375 : fffffa80`0a1cf8d0 fffffa80`00000000 fffff880`03508438 fffffa80`071db1a0 : tcpip!FlUnbindAdapter+0xaa
    fffff880`03508280 fffff880`01760adf : fffffa80`071db1a0 00000000`00000000 fffffa80`0a3357c0 00000000`00000000 : ndis!ndisUnbindProtocol+0x205
    fffff880`03508390 fffff880`01761c5b : 00000000`00000001 fffffa80`071db1a0 fffff880`03508420 00000000`00000001 : ndis!ndisCloseMiniportBindings+0x2df
    fffff880`035084a0 fffff880`016fabc2 : fffffa80`071db1a0 fffffa80`071db1a0 fffffa80`0cecfc10 fffffa80`071db1a0 : ndis!ndisPnPRemoveDevice+0x25b
    fffff880`03508640 fffff880`01764dc1 : 00000000`00000000 fffffa80`0cecfc10 00000000`00000000 fffffa80`071db1a0 : ndis!ndisPnPRemoveDeviceEx+0xa2
    fffff880`03508680 fffff880`01ba6537 : 00000000`00000300 00000000`00000000 fffff880`03508848 00000000`00000000 : ndis!ndisPnPDispatch+0x862
    fffff880`03508720 00000000`00000300 : 00000000`00000000 fffff880`03508848 00000000`00000000 00000000`00000020 : DNPFW+0x9537
    fffff880`03508728 00000000`00000000 : fffff880`03508848 00000000`00000000 00000000`00000020 00000000`000007ff : 0x300
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0x9F_4_IMAGE_tcpip.sys
    BUCKET_ID:  X64_0x9F_4_IMAGE_tcpip.sys
    Followup: MachineOwner
    0: kd> lmvm tcpip
    start             end                 module name
    fffff880`01800000 fffff880`019fe000   tcpip      (pdb symbols)          c:\symbols\tcpip.pdb\494FAD1F538A4ED5A2BF3CC62A5FFFCB2\tcpip.pdb
        Loaded symbol image file: tcpip.sys
        Mapped memory image file: c:\symbols\tcpip.sys\51D786591fe000\tcpip.sys
        Image path: \SystemRoot\System32\drivers\tcpip.sys
        Image name: tcpip.sys
        Timestamp:        Sat Jul 06 03:52:09 2013 (51D78659)
        CheckSum:         001D78AE
        ImageSize:        001FE000
        File version:     6.1.7601.22378
        Product version:  6.1.7601.22378
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.6 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     tcpip.sys
        OriginalFilename: tcpip.sys
        ProductVersion:   6.1.7601.22378
        FileVersion:      6.1.7601.22378 (win7sp1_ldr.130705-1532)
        FileDescription:  TCP/IP Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    Same user, different error, but still a BSOD.
    Turning on the laptop when plugged into the dynadock, and he gets a BSOD. I've pasted the bugcheck in below. We are in the process of uninstalling and reinstalling all the drivers, and replacing his dynadock with a known good one to determine if the issue resides with the laptop or not.
    *                        Bugcheck Analysis                                    *
    ACPI_BIOS_ERROR (a5)
    The ACPI Bios in the system is not fully compliant with the ACPI specification.
    The first value indicates where the incompatibility lies:
    This bug check covers a great variety of ACPI problems.  If a kernel debugger
    is attached, use "!analyze -v".  This command will analyze the precise problem,
    and display whatever information is most useful for debugging the specific
    error.
    Arguments:
    Arg1: 0000000000001000, ACPI_BIOS_USING_OS_MEMORY
        ACPI had a fatal error when processing a memory operation region.
        The memory operation region tried to map memory that has been
        allocated for OS usage.
    Arg2: 0000000000000000, The high portion of the physical address of the memory region.
    Arg3: 0000000000000ff0, The low portion of the physical address of the memory region.
    Arg4: 0000000000000025, The length of memory being mapped.
    Debugging Details:
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA5
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff88000fa330f to fffff8000328cf40
    STACK_TEXT:  
    fffff880`03723a58 fffff880`00fa330f : 00000000`000000a5 00000000`00001000 00000000`00000000 00000000`00000ff0 : nt!KeBugCheckEx
    fffff880`03723a60 fffff880`00fa5cfe : 00000000`00000ff0 00000000`00000000 00000000`00000000 fffffa80`07d59000 : ACPI!MapPhysMem+0xcf
    fffff880`03723ab0 fffff880`00fae0c0 : fffffa80`07d684f0 fffffa80`07d59000 00000000`00008000 00000000`00000000 : ACPI!OpRegion+0x136
    fffff880`03723af0 fffff880`00fa8ac2 : fffffa80`07d59000 00000000`00000000 00000000`00008000 00000000`00000000 : ACPI!ParseTerm+0x17c
    fffff880`03723b30 fffff880`00fa61a6 : fffff880`00fb90e0 fffff880`00fb9ac0 fffffa80`0671d740 fffff880`00fb90e0 : ACPI!RunContext+0x86
    fffff880`03723b70 fffff880`00fa1054 : fffff880`00fb91e8 fffff880`00fb9ac0 fffffa80`0671d740 fffffa80`099f09a8 : ACPI!StartTimeSlicePassive+0x8a
    fffff880`03723ba0 fffff800`0352d6ee : fffffa80`066d0b50 00000000`00000080 00000000`00000001 00000000`00000000 : ACPI!ACPIWorkerThread+0xd8
    fffff880`03723c00 fffff800`0327df26 : fffff880`03100180 fffffa80`066d0b50 fffffa80`06748660 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03723c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    ACPI!MapPhysMem+cf
    fffff880`00fa330f cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  ACPI!MapPhysMem+cf
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: ACPI
    IMAGE_NAME:  ACPI.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294
    FAILURE_BUCKET_ID:  X64_0xA5_ACPI!MapPhysMem+cf
    BUCKET_ID:  X64_0xA5_ACPI!MapPhysMem+cf
    Followup: MachineOwner

Maybe you are looking for