Random BSODs from ntoskrnl

Hi there, I'm using an Asus laptop (about 2 years old now) and recently started getting random blue screens. They aren't constant, but frequent enough to be a problem. I've tried doing a memory test on my RAM and did a full scan/repair of my hard drive and
didn't find any errors. Sometimes these blue screens come while i'm logging in (usually the cancel_state_in_completed_irp) after having closed the laptop for the night, sometimes they happen completely randomly while using it or even idling (driver_irql_not_less_or_equal).
I'm living in China so taking it somewhere to be looked at isn't an option, so I was hoping I could find some help here. I'm not exactly sure how to post the dump file info, I've just been using BlueScreenView to look at it, here's the info it gives me:
100214-27705-01.dmp 10/2/2014 1:26:51 PM
CANCEL_STATE_IN_COMPLETED_IRP 0x00000048
fffffa80`0d772590 fffff8a0`196743b8
00000000`00000000 00000000`00000000
PECKP_x64.SYS PECKP_x64.SYS+1160
x64 ntoskrnl.exe+75bc0
C:\Windows\Minidump\100214-27705-01.dmp
8 15 7601
262,144 10/2/2014 1:28:27 PM
093014-28626-01.dmp 9/30/2014 7:26:05 PM
DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1
00000000`00000020 00000000`00000002
00000000`00000000 fffff880`0b37ec24
PECKP_x64.SYS PECKP_x64.SYS+5c24
x64 ntoskrnl.exe+75bc0
C:\Windows\Minidump\093014-28626-01.dmp
8 15 7601
262,144 9/30/2014 7:27:15 PM
I'm not sure these will be helpful but if more info is needed, please let me know. Thanks a lot!

Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
-- %systemroot% is the environment variable for your Windows directory. For example, C:\Windows.
2. Copy any and all .DMP files in the Minidump folder to your Desktop, create a new folder on the Desktop to put these .DMP files in, and then zip the folder. You can then either use a 3rd party tool such as 7-Zip/Winrar, or you can use Windows'
default method of zipping folders.
Compress and uncompress files (zip files).
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, and your Minidump folder is empty, you will need
to allow the system to crash once again to generate a crash dump.
3. Upload the .ZIP containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply.
Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel Memory Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel Memory Dumps in the simplest definition is a Kernel Memory Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel Memory Dump is
the best choice. Do note that Kernel Memory Dumps are much larger
in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for
all drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the
system log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Similar Messages

  • Randomly BSODs caused by ntoskrnl.exe

    I have random BSODs, this is the dump file... any ideas? I tried to update all drivers, but I solved nothing.
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\061114-29937-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Error: Attempts to access '061114-29937-01.dmp' failed: 0x0 - The operation completed successfully.
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Error                                          061114-29937-01.dmp
    Symbol search path is: 061114-29937-01.dmp
    Executable search path is:
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff800`6e28e000 PsLoadedModuleList = 0xfffff800`6e5582d0
    Debug session time: Wed Jun 11 20:29:12.062 2014 (UTC + 2:00)
    System Uptime: 0 days 0:22:21.219
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    ************* Symbol Loading Error Summary **************
    Module name            Error
    ntoskrnl               The system cannot find the file specified
    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 133, {1, 1e00, 0, 0}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    5 times more...
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    Probably caused by : ntoskrnl.exe ( nt+153fa0 )
    Followup: MachineOwner
    Systeminfo:
    OS Name:                   Microsoft Windows 8.1 Pro
    OS Version:                6.3.9600 N/A Build 9600
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Standalone Workstation
    OS Build Type:             Multiprocessor Free
    Original Install Date:     30/10/2013, 13:43:05
    System Boot Time:          11/06/2014, 20:29:52
    System Manufacturer:       TOSHIBA
    System Model:              Satellite L500
    System Type:               x64-based PC
    Processor(s):              1 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 37 Stepping 2 GenuineIntel ~2261 Mhz
    BIOS Version:              TOSHIBA 2.10, 17/05/2011
    Windows Directory:         C:\WINDOWS
    System Directory:          C:\WINDOWS\system32
    Boot Device:               \Device\HarddiskVolume2
    Total Physical Memory:     3.958 MB
    Available Physical Memory: 1.792 MB
    Virtual Memory: Max Size:  7.926 MB
    Virtual Memory: Available: 5.492 MB
    Virtual Memory: In Use:    2.434 MB
    Page File Location(s):     C:\pagefile.sys
    Domain:                    WORKGROUP
    Logon Server:             
    \\MicrosoftAccount
    Hotfix(s):                 56 Hotfix(s) Installed.
                               [01]: KB2899189_Microsoft-Windows-CameraCodec-Package
                               [02]: KB2843630
                               [03]: KB2868626
                               [04]: KB2883200
                               [05]: KB2887595
                               [06]: KB2889543
                               [07]: KB2891214
                               [08]: KB2893294
                               [09]: KB2894029
                               [10]: KB2894179
                               [11]: KB2898868
                               [12]: KB2900986
                               [13]: KB2901125
                               [14]: KB2901128
                               [15]: KB2903939
                               [16]: KB2904440
                               [17]: KB2911106
                               [18]: KB2912390
                               [19]: KB2913152
                               [20]: KB2916036
                               [21]: KB2919355
                               [22]: KB2919394
                               [23]: KB2919442
                               [24]: KB2920189
                               [25]: KB2923528
                               [26]: KB2923768
                               [27]: KB2926765
                               [28]: KB2928680
                               [29]: KB2931358
                               [30]: KB2931366
                               [31]: KB2939153
                               [32]: KB2939576
                               [33]: KB2950153
                               [34]: KB2953522
                               [35]: KB2954879
                               [36]: KB2955164
                               [37]: KB2956575
                               [38]: KB2957151
                               [39]: KB2957189
                               [40]: KB2957689
                               [41]: KB2958262
                               [42]: KB2959977
                               [43]: KB2961908
                               [44]: KB2962140
                               [45]: KB2964718
                               [46]: KB2964736
                               [47]: KB2965065
                               [48]: KB2965142
                               [49]: KB2965500
                               [50]: KB2965699
                               [51]: KB2965788
                               [52]: KB2966072
                               [53]: KB2966407
                               [54]: KB2966804
                               [55]: KB2969817
                               [56]: KB976002
    Network Card(s):           10 NIC(s) Installed.
                               [01]: Realtek PCIe FE Family Controller
                                     Connection Name: Ethernet
                                     DHCP Enabled:    Yes
                                     DHCP Server:     N/A
                                     IP address(es)
                               [02]: Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC
                                     Connection Name: Wi-Fi
                                     Status:          Hardware
    not present
                               [03]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 6
                                     Status:          Media
    disconnected
                               [04]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 3
                                     Status:          Media
    disconnected
                               [05]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 5
                                     DHCP Enabled:    Yes
                                     DHCP Server:     192.168.1.1
                                     IP address(es)
                                     [01]: 192.168.1.129
                                     [02]: fe80::1513:f368:3c1e:c173
                               [06]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 4
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: 169.254.80.80
                                     [02]: fe80::4892:9cb3:7a80:2057
                               [07]: VMware Virtual Ethernet Adapter for VMnet1
                                     Connection Name: VMware Network Adapter VMnet1
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: 192.168.223.1
                                     [02]: fe80::a11c:f4d5:c02f:9fcf
                               [08]: VMware Virtual Ethernet Adapter for VMnet8
                                     Connection Name: VMware Network Adapter VMnet8
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: 192.168.132.1
                                     [02]: fe80::fc9a:9075:a71e:776c
                               [09]: TAP-Windows Adapter V9
                                     Connection Name: Local Area Connection 3
                                     Status:          Media
    disconnected
                               [10]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: vEthernet (TAP-Windows Adapter V9 Virtual Switch)
                                     Status:          Media
    disconnected
    Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

    Hi,
    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
    If you don't know where .DMP files are located, here's how to get to them:
    1. Navigate to the %systemroot%\Minidump folder.
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
    between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
    much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
    choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
    If you are going to use Onedrive but don't know how to upload to it, please visit the following:
    Upload photos and files to Onedrive.
    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
    Share files and folders and change permissions and view 'Get a link'.
    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
    If your computer is not generating .DMP files, please do the following:
    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
    drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
    log'.
    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
    4. Double check that the WERS is ENABLED:
    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
    Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
    If you cannot get into normal mode to do any of this, please do this via Safe Mode.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Windows server 2012 R2 randomly BSOD's

    Dear all,
    Since recently we suffering from random BSOD's on a Windows 2012 R2 terminal server. We already checked if there has been any changes, updates, new drivers installed, etc. around the time we receive the first one, but we cannot find anything. The server
    is a virtual server on Hyper-V but the Hyper-V host doesn't suffer from BSOD's and is working properly. We updated the servers with newest windows updates. Could someone please help me debugging this minidump:
    Loading Dump File [C:\Users\admtem\Desktop\031915-48906-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*c:\cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (16 procs) Free x64
    Product: Server, suite: TerminalServer
    Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
    Machine Name:
    Kernel base = 0xfffff801`f4489000 PsLoadedModuleList = 0xfffff801`f4762250
    Debug session time: Thu Mar 19 01:55:51.856 2015 (UTC + 1:00)
    System Uptime: 0 days 2:21:59.525
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {fffff90140599000, 2, 0, fffff801f45280ab}
    Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+3fb )
    Followup: MachineOwner
    6: kd> !analyze -v
    * Bugcheck Analysis *
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffff90140599000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801f45280ab, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff801f47ec138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    fffff90140599000
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!KeSetEvent+3fb
    fffff801`f45280ab 488b09 mov rcx,qword ptr [rcx]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR: AV
    PROCESS_NAME: System
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    TRAP_FRAME: ffffd00142686900 -- (.trap 0xffffd00142686900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffd001475bc4e8 rbx=0000000000000000 rcx=fffff90140599000
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff801f45280ab rsp=ffffd00142686a90 rbp=0000000000000000
    r8=0000000000000000 r9=fffff801f492c628 r10=fffff90140599000
    r11=ffffd00142686b00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz ac po nc
    nt!KeSetEvent+0x3fb:
    fffff801`f45280ab 488b09 mov rcx,qword ptr [rcx] ds:fffff901`40599000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff801f45e54e9 to fffff801f45d99a0
    STACK_TEXT:
    ffffd001`426867b8 fffff801`f45e54e9 : 00000000`0000000a fffff901`40599000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`426867c0 fffff801`f45e3d3a : 00000000`00000000 ffffd001`475bc4e0 ffffe001`26538900 ffffcf81`0df3afa0 : nt!KiBugCheckDispatch+0x69
    ffffd001`42686900 fffff801`f45280ab : 00000000`00002608 00000000`00000000 00000000`00000030 00000000`00000000 : nt!KiPageFault+0x23a
    ffffd001`42686a90 fffff801`f45343ac : fffff901`40599000 ffffe001`00000000 ffffe001`25f34800 fffff801`00000000 : nt!KeSetEvent+0x3fb
    ffffd001`42686b50 fffff801`f4561280 : 13131313`13131313 ffffe001`25f34880 00000000`00000080 ffffe001`25f34880 : nt!ExpWorkerThread+0x28c
    ffffd001`42686c00 fffff801`f45dffc6 : ffffd001`42040180 ffffe001`25f34880 ffffd001`4204c5c0 13131313`13131313 : nt!PspSystemThreadStartup+0x58
    ffffd001`42686c60 00000000`00000000 : ffffd001`42687000 ffffd001`42681000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!KeSetEvent+3fb
    fffff801`f45280ab 488b09 mov rcx,qword ptr [rcx]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nt!KeSetEvent+3fb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 54c832b2
    IMAGE_VERSION: 6.3.9600.17668
    BUCKET_ID_FUNC_OFFSET: 3fb
    FAILURE_BUCKET_ID: AV_VRF_nt!KeSetEvent
    BUCKET_ID: AV_VRF_nt!KeSetEvent
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:av_vrf_nt!kesetevent
    FAILURE_ID_HASH: {3ff99d47-0a85-0b19-f59a-c152651b9c12}
    Followup: MachineOwner
    Any help would be much appriciated!
    Kind Regards,
    Thijs

    Hi Thijs,
    Just addition, please also check if all necessary windows updates were installed in this problematic server. Please check if drivers need to be updated.
    Please also refer to following thread and check if can help you.
    Blue Screen Error (Probably caused by : ntkrnlmp.exe)
    If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
    To obtain the phone numbers for specific technology request, please refer to the web site listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Random BSOD after installing Windows 8.1 on Lynx K3011

    I upgraded the graphics drivers as intructed her in another thread and that works now. However I keep getting a random BSOD with the error MEMORY_MANAGEMENT.
    I did a bug check analysis and this is the result:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Windows\Minidump\101413-9031-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.16384.x86fre.winblue_rtm.130821-1623
    Machine Name:
    Kernel base = 0x81c14000 PsLoadedModuleList = 0x81e0e218
    Debug session time: Mon Oct 14 12:47:54.837 2013 (UTC - 7:00)
    System Uptime: 0 days 0:00:09.648
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                    *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1A, {1238, 85ea6368, 802, 0}
    Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c )
    Followup: MachineOwner
    3: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00001238, The subtype of the bugcheck.
    Arg2: 85ea6368
    Arg3: 00000802
    Arg4: 00000000
    Debugging Details:
    BUGCHECK_STR:  0x1a_1238
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 81d63c8d to 81d14ce4
    STACK_TEXT: 
    8b90ebf0 81d63c8d 0000001a 00001238 85ea6368 nt!KeBugCheckEx
    8b90ec38 82d1abb4 85ea6368 8506b040 00000162 nt! ?? ::FNODOBFM::`string'+0x355e7
    8b90ec54 82d18dec 00000000 8506bd10 00000001 rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+0x4c
    8b90ecc4 82d1704b 00000000 86291040 8506b008 rdyboost!ST_STORE<SMD_TRAITS>:tDmPageRemove+0x3ac
    8b90ed00 82d1739e 00000000 8506c200 83a4b040 rdyboost!ST_STORE<SMD_TRAITS>:tWorkItemProcess+0xf3
    8b90ed40 82d266a0 ce25f08e 00000000 8506c200 rdyboost!SMKM_STORE<SMD_TRAITS>:mStWorker+0xfc
    8b90ed70 81cc36a8 8506b008 61b2fcc6 00000000 rdyboost!SMKM_STORE<SMD_TRAITS>:mStWorkerThread+0x1d
    8b90edb0 81d2a701 82d26683 8265bf68 00000000 nt!PspSystemThreadStartup+0x58
    8b90edbc 00000000 00000000 2444c718 80000010 nt!KiThreadStartup+0x15
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c
    82d1abb4 6a00            push    0
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: rdyboost
    IMAGE_NAME:  rdyboost.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  52158f40
    BUCKET_ID_FUNC_OFFSET:  4c
    FAILURE_BUCKET_ID:  0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_:tReleaseRegion
    BUCKET_ID:  0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_:tReleaseRegion
    Followup: MachineOwner
    Any ideas? Probably more incompatible drivers. If I can't get Windows 8.1 running correctly, does anyone know how to restore the system image?
    Solved!
    Go to Solution.

    this error is so much obvius.
    just look on internet on how to disable readyboost. additional just turn off the hybrid function and u will never see this bsod again, even i dont know how dumb ur mediacenter edition is and want to give u other bsods. btw i only seen bsods couse of **bleep** driver on my devices. donno how u manage to get such bluescreens......
    btw according to the results i recommning ya to use ckhdsk /f to ur disk. mstWorker is mentioned wich means read write issues on access files. mstworker is microsoft Tiworker, an process wich examines files an bit. used by winupdate and the indexer. 

  • Random BSOD - Toshiba Qosmio X500 13R (Windows 7 Home Premium x64) have min

    I've been having some problems with random BSODs on my laptop.
    The laptop itself is fairly new,bought in March this year,really good model but refently I started having problems.
    One day I closed the laptop and thinking it went into sleep mode but a few hours later when I opened it a BSOD stared me in the face,the processor part was pretty hot so I immediately restarted it to lower the temperature,but I remember that the BSOD had something about "Kernel Power" written on it.
    It happend 3-4 times since then,the third time it happened I enabled minidump logging so now I also have the log from the last time it happened,can anyone take a look at it and tell me what is going on and how to fix it??
    I still have a guarantee on this baby so I can get it fixed for free if it's a hardware issue, still I have some important work to do this week (already almost lost a crucial project file on this) so I want to try and fix it myself for now,until I get this project done.
    Thanks!!!
    LAPTOP MODEL:
    Toshiba Qosmio X500 13R
    Specs:
    QOSMIO X500-13R - RED
    Intel Core i7-740QM Processor, 1.73 GHz
    Windows 7 Home Premium 64-bit
    18.4'' Toshiba TruBrite Full HD 1,920x1080
    1000GB HardDisk (500GB + 500GB [7200rpm])
    8GB RAM DDR3 (1,066 MHz) max 8GB
    NVIDIA GeForce GTS 460M (1.50GB)
    Wireless LAN b/g/N-Bluetooth
    TV Tuner
    Rewritable Blu-ray Disc
    HD Web Camera with built-in Mic
    Minidump file:
    http://www.mediafire.com/?94akhevoscc8197

    >I still have a guarantee on this baby so I can get it fixed for free if it's a hardware issue, still I have some important work to do this week (already almost lost a crucial project file on this) so I want to try and fix it myself for now,until I get this project done.
    The BSOD can be caused by software of hardware issue.
    You can check if new OS installation would solve this if its software issue then a fresh OS installation is the right workaround. Before starting a OS installation, backup the data ;)
    But of course the issue could be related to hardware; for example high temperature.
    You said that you have noticed higher temperature while happening.
    So maybe the memory modules are affected by higher temperature and this leads to BSOD. In most cases clogged fans are reason for that. Check if dust and debris needs to be removed you can remove dust using compressed air spray.
    But if this does not help, I would recommend checking the hardware under warranty conditions

  • Random BSOD/Crackle Pop in BF2/BSOD in BF2142 on X-FI Fatality FPS Champ

    Using latest drivers from Creative v2.9.7 not the June/July update through windows update because it kills the DTS and makes the sound sound all monolike. Ok so here it goes, the driver support says that the latest should've fixed the BF2 crack/snap/pop sounds but I just reinstalled the game recently and I still hear it even with the current version I use so I guess it isn't fixed. 2nd issue is when setting it audio to x-fi with Ultra High, it BSOD's after awhile or so of playing with ha20x2k.sys. Also I get random BSOD's from doing various things such as I could be watching a movie then wanted to play a game or something then a BSOD occurs thereafter with ha20x2k.sys issue again. No this doesn't happen all the time just after my computer has been used for a few days and when I have been listening to various audio's from being a movie or music. On some games it just gives BSOD as if it were random. After a quick reboot I can play the game fine so I just know it's random to the point where it can happen if maybe multiple files with audio are initiated either it being a game and/or movie. And last issue is BF242. I find it funny how it says certified for 242 and/or best heard with on X-fi and yet it gives these casual BSOD after playing for an hour or so using X-FI ultra high settings. I was wondering what can be done to fix any of the 3 possible issues already said on the topic. Yes I've reinstalled them again and still no go. I only have the drivers instealled, EAX, audio console, volume properties, DTS NEO:6, and GO launcher v5.0. Everything else I got rid of... so if anyone knows of a solution or suggestion please let me know. Thanks. P.S. Was looking around but I don't see a Fatality FPS Champion edition no more. Only Xtremegamer Fatality... discontinued? Problem related issues?

    Using latest drivers from Creative v2.9.7 not the June/July update through windows update because it kills the DTS and makes the sound sound all monolike. Ok so here it goes, the driver support says that the latest should've fixed the BF2 crack/snap/pop sounds but I just reinstalled the game recently and I still hear it even with the current version I use so I guess it isn't fixed. 2nd issue is when setting it audio to x-fi with Ultra High, it BSOD's after awhile or so of playing with ha20x2k.sys. Also I get random BSOD's from doing various things such as I could be watching a movie then wanted to play a game or something then a BSOD occurs thereafter with ha20x2k.sys issue again. No this doesn't happen all the time just after my computer has been used for a few days and when I have been listening to various audio's from being a movie or music. On some games it just gives BSOD as if it were random. After a quick reboot I can play the game fine so I just know it's random to the point where it can happen if maybe multiple files with audio are initiated either it being a game and/or movie. And last issue is BF242. I find it funny how it says certified for 242 and/or best heard with on X-fi and yet it gives these casual BSOD after playing for an hour or so using X-FI ultra high settings. I was wondering what can be done to fix any of the 3 possible issues already said on the topic. Yes I've reinstalled them again and still no go. I only have the drivers instealled, EAX, audio console, volume properties, DTS NEO:6, and GO launcher v5.0. Everything else I got rid of... so if anyone knows of a solution or suggestion please let me know. Thanks. P.S. Was looking around but I don't see a Fatality FPS Champion edition no more. Only Xtremegamer Fatality... discontinued? Problem related issues?

  • MSI Z97 MPOWER MAX AC, getting Random Bsod

    I installed my new msi z97 mpower and i7 4790k and iv gotten random bsod, mostly when running youtube videos in fullscreen 1080p and when i tried to defrag my hdd i always got bsod. I formated everything and only installed the LAN driver from my dvd so i could get internet going and then i updated all up to windows 8.1, wich i then proceded to download the drivers from MSI Updater Live.
    Main Board: MSI Z97 MPOWER MAX AC
    Bios Version: 1.60
    Video Card: Gigabyte GeForce GTX 980 4GB G1 Gaming
    PSU:   Corsair AX 850W 80+ Gold
    12v rail Rating of listed PSU:
    CPU: Intel Core i7 4790K 4GHz, 8MB
    Memory:Corsair 16GB (4x4GB) CL9 1600Mhz VENGEANCE Quad Channel
    SSD/ HDD: Corsair SSD Force 3 Series 180GB + 2TB WD Black 7200rpm 64MB
    CPU COOLER: Corsair Hydro H100
    Raid Card: None
    Sound Card: None
    Any Additional hardware plugged into your system: Gigabyte GTX 980
    OC: No
    Operating System: Windows 8.1 64bit
    Drivers i have installed:
    The bsod I'v gotten since i formated my harddrives, using WhoCrashed:
    (This happen when i was typing this thread and it also knocked my mouse and keyboard out so i had to change their usb slots to make them work again)
    I'v watched some other threads who had similar problems but i couldnt come to a conculsion on what problem i had, so any help would be very appriecated.

    I have not tried the clear cmos guide and I will try it.
    I have tried memtest, and passed. But iv only let it pass once after closing it because I didnt know how it worked.
    Its 4x4gb singlekit. I will try the 'Exclude method' next
    Here is the messages i got after clearing cmos
    Edit: Clearing CMOS did not solve my problem.

  • W701 BSOD from nvlddmkm

    I've been getting these random BSOD for awhile now, upgrading the display drivers generally doesn't fix the problem.  I know several people have had issues with this before, what's the deal with this, is this Lenovo or Nvidia or both fault?  How can this be fixed once and for all?

    I used to have this problem, too. A workaround is disabling the PowerMizer of the graphics card: http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/W701ds-Nvidia-display-driver-crashes-frequentl... . This eliminates random system lock-ups from all 2xx.xx drivers to date.

  • Random BSOD after migrated to SCCM 2012 R2 - System Endpoint Protection

    We are currently experiencing random BSOD after upgrade to SCCM 2012 R2 from SCCM 2012. These BSOD are happening on our Windows 7 x64 machines. With the upgrade, we switched to System Center Endpoint Protection for the anti-virus protection and start
    to notice this problem. Have anyone else experiencing the same issue? I'm trying to run adplus right now on 2 machines to try and capture the error but so far no luck. This BSOD is so random and we are getting at least 5 calls a day from users about this.
    The only similarity with these BSOD is usually the user is away from keyboard and after the BSOD, System Center Endpoint cannot connect to update virus definition.
    Below is a screenshot of the BSOD and it didn't create any memory dump file. We are currently running Windows 7 x64.
    Message was: "STOP:
    C000021a [fatal system error].  The Windows subsystem process terminate
    unexpectedly with a status of 0xC0000005

    - Event Type : Stopped working (APPCRASH)
          Application Name: Client Server Runtime Process
          Path:             C:\windows\system32\csrss.exe
          Event Time      : 03/22/2014 12:30:26 AM
              Application Name: csrss.exe
              Application Version: 6.1.7600.16385
              Application Timestamp: 4a5bc115
              Fault Module Name: sxs.dll
              Fault Module Version: 6.1.7601.17514
              Fault Module Timestamp: 4ce7c9cc
              Exception Code: c0000005
              Exception Offset: 0000000000011b2f
          Memory dump     : Not created

  • Random BSOD 0x124

    Hi,
    If you remember me I&#39;ve posted on the G.Skill ram topic, hopping to solve my BSOD problem. Unfortunately, I&#39;ve done tons of researchs without finding my problem...
    I have random BSOD, always 0x124 with hal.dll pointed out, during gaming, sometimes ...

    Quote from: cmplieger on Today at 14:36:09You should reset your computer int he pc settings. A clean install will probably solve all issues. Should take 20 min or so
    I did try to reset but it would not le...

  • New Stream 7 Randomly BSOD

    I bought a stream 7 from the Microsoft Store and got it a couple of days ago.  Shortly after, I noticed I would get random BSOD.  Sometimes, after a BSOD, it would also BSOD during start up and automatic startup repair would start and fail.  Then it would start normally.  I've tried doing refresh and reset.  I still get random BSOD.  What could be wrong?
    This question was solved.
    View Solution.

    yea BSOD is very rare in windows 8 and is usualy the cause of two things, failing hardware, and incorrect driver installed. 
    You will need to give us the information on the blue screen though for us to answer any further, HOWEVER... since I doubt you installed any rogue drivers I suspect a piece of hardware has failed and considering nothing in the tablet is replaceable, you should arrange for a return to the microsoft store for a refun or replacement. 

  • Random bsod windows 7 64bit

    i have a random bsod on windows 7 64bit
    windows say its a driver issue i have downloaded the latest driver from msi ati catalist 10.7 still no joy.
    Problem signature
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 2057
    Extra information about the problem
    BCCode: 116
    BCP1: FFFFFA8006265010
    BCP2: FFFFF88003F087F8
    BCP3: 0000000000000000
    BCP4: 0000000000000002
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1
    Bucket ID: X64_0x116_TdrBCR:2_Tdr:2_IMAGE_atikmdag.sys
    Server information: 58f61974-4324-4f0b-9d1d-be5b9ed45f4e
    system
    amd penom ll x4 965
    msi dka790 platinum m/board
    4gb crucial 1066mhz ram
    1tb samsung f1 spinpoint h/drive
    onboard graphics ati hd3300

    This issue is related to ATI driver atikmdag.sys. From ATI forum I found that user can resolve this issue by updating all hard ware drivers.
    AMD Game Forums - atikmdag.sys bsod
    Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    If any of the drivers are not indicated to be compatible with Windows 7, that may be the root cause.
    You can also remove this file from your system as a workaround to avoid this issue.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

  • P67A-GD55 - Random BSODs with varying codes

    Hey guys,
    I'm sort of reaching the end of the line with my troubleshooting resources, so I'm hoping someone here can possibly provide me a little assistance.  As the title indicates, I'm experiencing random BSODs on a newly built system.  Below is what I have done to troubleshoot, as well as the specs.
    MOBO - MSI P67A-GD55 (B3)
    CPU - Intel Core i5 - PN BX80623I52500K
    PSU - CORSAIR HX Series CMPSU-850HX 850W
    Memory - Corsair XMS3 DDR3 1333 (2x4GB) - PN CMX8GX3M2A1333C9
    HD - OCZ Vertex Series OCZSSD2-1VTX30GXXX SSD
    HD - Seagate Barracuda 7200.12 ST31000528AS x2 (Raid 0)
    Video - EVGA 01G-P3-1373-AR GeForce GTX 460
    Updated all drivers to current revisions
    Updated BIOS to latest revision
    memtest86 - Over 24 hours of testing, all testing options, 10x passes - No errors
    Windows Memory Tester - Over 24 hours of testing, full options - No errors
    PSU Test - Checked every connection coming off of the PSU and all voltages are appropriate
    Just for fun I've run the system with memory in varying slots and with varying sticks.  No dice.
    superpi - I've run this up to 32m on all cores on the CPU multiple times just to see if this causes any crashes despite the CPU being at stock config.  - No errors
    BSODs I have seen:
    APC_INDEX_MISMATCH
    MEMORY_MANAGEMENT
    SYSTEM_SERVICE_EXCEPTION
    dxgmms1.sys
    And about 12 others that I didn't note at the time for some reason.
    Other odd behavior:
    After some BSODs, the system rediscovers all my USB devices that I have attached.
    I've done research on the individual codes, but the solutions are like throwing darts at a dart board.  I'm suspecting at this point that I either have a bad CPU or Mobo.
    Also note that nothing is overclocked.
    Any thoughts or ideas?
    TYVM in advance.
    -JT

    Quote from: Somewords on 07-May-11, 06:47:01
    PSU - CORSAIR HX Series CMPSU-850HX 850W
    is your psu over powered?
    mine is 500w silverstone.
    running i5 2400
    gskill 4gbx2 10666cl7
    palit 550 ti sonic
    wd cavier blue 320gb 6gb/s and seagate 320gb 3gb/s
    sony dvd-rw lightscribe

  • GT70 DE Random BSOD

    hi
    i recently bought a GT70 (Dragon edition 2) and keep getting random BSODs 0.5~2 hours apart. i don't have direct access to msi but the place i bought it from provides a 1 yr warranty. i took it to the "technical support" section and after 5 days they told me they haven't encountered any kind of issue (which i know they're lying). so i want to know if there's something i can do on my own. i currently don't have access to it to attach the dump files but i will as soon as i take it back.
    i read somewhere that i should update the LAN/WLAN driver so i did but after a reboot everything went to s***. all i got was "Please Wait" for an hour so i used system restore point to undo what i did. i was lucky steam made one before installing DX bcs i didn't even have recovery disks made. i may have made a mistake by downloading the latest drivers from qualcomm's website instead of msi.
    now i'm back to square one. any thoughts ?
    EDIT : Dump files : https://onedrive.live.com/redir?resid=C5320B97C53E21BD!207&authkey=!AG33p9do1Ed2x-A&ithint=file%2c.rar

    those BSOD's hapends while during what?
    I've checked your dump files, its return this:
    Quote
    On Sat 28.6.2014 г/ 01:24:29 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\062714-7453-01.dmp
    This was probably caused by the following module: iastora.sys (iaStorA+0x61729)
    Bugcheck code: 0xD1 (0xFFFFFA811C1A6268, 0x2, 0x1, 0xFFFFF88001510729)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\iastora.sys
    product: Intel(R) Rapid Storage Technology driver
    company: Intel Corporation
    description: Intel(R) Rapid Storage Technology driver - x64
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastora.sys (Intel(R) Rapid Storage Technology driver - x64, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
    On Fri 27.6.2014 г/ 22:09:43 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\062814-6968-01.dmp
    This was probably caused by the following module: hidclass.sys (HIDCLASS+0x1F59)
    Bugcheck code: 0xD1 (0x400000004, 0x2, 0x1, 0xFFFFF88005244F59)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\hidclass.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hid Class Library
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Fri 27.6.2014 г/ 21:54:38 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\062814-6843-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880063CC25E)
    Bugcheck code: 0xD1 (0x28B93020, 0x2, 0x0, 0xFFFFF880063CC25E)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 340.43
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 340.43
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.43 , NVIDIA Corporation).
    Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
    On Fri 27.6.2014 г/ 21:36:36 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\062814-7343-01.dmp
    This was probably caused by the following module: akw8x64.sys (0xFFFFF8800530E2C4)
    Bugcheck code: 0x3D (0xFFFFF800FAB86DF0, 0x0, 0x0, 0xFFFFF8800530E2C4)
    Error: INTERRUPT_EXCEPTION_NOT_HANDLED
    Bug check description: This bug check appears very infrequently.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: akw8x64.sys .
    Google query: akw8x64.sys INTERRUPT_EXCEPTION_NOT_HANDLED
    those errors are too random,
    which suggest probably hardware failure, [memory issue or other kind of instability]
    test memory with http://www.memtest.org/
    leave it over night for a test loop

  • My phone will randomly disconnect from the wifi and when I retype the password it says it is wrong. It will eventually work but I have to wait for a message to pop up on my screen to allow me to retype the wifi password.

    When I first got my phone it worked perfectly fine with the wifi. Although later on I began to have problems connecting it. It will randomly disconnect from the wifi and when I try to retype the password it tells me it is wrong, although it is right. It will eventually work but in its own time, a message will pop up and allow me to type in the password and it will work. But sometimes it takes an hour or more and sometime it takes 10 minutes. I've seen where other people have had this problem but I don't know how to fix it. I'm not sure if it's an issue with my phone or if it's with my wifi. Does anyone know how to fix this?

    Does this happen with all Wi-Fi hotspots?  A specific one?
    Have you tried forgetting the Wi-Fi connection and then reconnecting to it?
    What about power cycling the Wi-Fi router?

Maybe you are looking for

  • Error in Jsp page - undefined type

    <html> <%@ page contentType="text/html; charset=utf-8" import="java.io.InputStream, java.io.IOException, javax.xml.parsers.SAXParser, java.lang.reflect.*, java.io.Writer.*, java.util.*, javax.xml.parsers.SAXParserFactory" session="false" %> <% * Copy

  • Doubt in message monitoring

    Hi, For a file-file scenario, in sxmb_moni, the message has AENGINE as both inbound and outbound. But should it not be AENGINE-IENGINE and IENGINE-AENGINE, since the message is transferred from sender adapter to IE (where mapping is done) and then tr

  • Help regarding display of rows

    Hi, I have a table a1 , when a select is made the output is OPT_NUM     PRI_GRANT_NUM     ANC_GRANT_NUM     VESTING_ORDER 34928     281048     281053     1 34928     281048     281054     2 34928     281048     281055     3 34928     281048 281056   

  • IPhoto will not launch--what do I do?

    When I try to open iPhoto it gives me the "quit unexpectedly" message.  I cannot access any of my photos.  What do I do?

  • Error consolidating music

    I'm getting the following error when I try to consolidate my tunes: "Copying music failed. You do not have enough access privileges for this operation." What gives? I'm running this from an admin account on Windows XP SP2. All files are marked as rea