Probably caused by : ntoskrnl.exe ( nt+72f40 )

Dear Friend,
I have a windows server 2008R2 running on Hyper v .The host machine is running windows server2012.on this server,Exchange application is running.This server is getting rebooted itself on every 15-20 days.the mini blue dumb for the issue is as below.Please
help me for the solution.
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Administrator\Desktop\032214-16718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                   
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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 7601.22411.amd64fre.win7sp1_ldr.130801-1934
Machine Name:
Kernel base = 0xfffff800`01a07000 PsLoadedModuleList = 0xfffff800`01c4b6d0
Debug session time: Sat Mar 22 18:41:25.076 2014 (UTC + 5:30)
System Uptime: 38 days 7:36:33.296
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                   
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
*                        Bugcheck Analysis                                   
Use !analyze -v to get detailed debugging information.
BugCheck 4A, {7773132a, 2, 0, fffff88002594b60}
***** 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                                    
***    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                                     
***    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                                    
***    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                                     
***    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                                    
***    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                                    
***    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                                    
***    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+72f40 )
Followup: MachineOwner
---------

Hi,
Before you start to use WinDbg you also need to configure the symbol path – just go to file->symbol file path and the path you need to enter for the Microsoft public symbol
server is:
http://msdl.microsoft.com/download/symbols
The related article:
Setting up WinDbg and Using Symbols
http://blogs.msdn.com/b/emeadaxsupport/archive/2011/04/10/setting-up-windbg-and-using-symbols.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

  • Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )

    I am debugging a minidump file but I am not able to make out if the problem is related to hardware or software? The possible culprit could be “ntkrnlmp.exe” but which thread or process faulted is beyond my understanding. Please can someone help a newbie
    debugger.
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [D:\Items\Mini030413-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: srv*f:\symbols\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (16 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336
    Machine Name:
    Kernel base = 0xfffff800`01e08000 PsLoadedModuleList = 0xfffff800`01fccdd0
    Debug session time: Mon Mar  4 07:23:36.821 2013 (UTC + 13:00)
    System Uptime: 49 days 13:51:33.653
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 7F, {8, 80050033, 6f8, fffff80001e8b4af}
    Unable to load image spep.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for spep.sys
    *** ERROR: Module load completed but symbols could not be loaded for spep.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )
    Followup: MachineOwner
    6: kd> !analyze -v
    *                        Bugcheck Analysis              
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000006f8
    Arg4: fffff80001e8b4af
    Debugging Details:
    BUGCHECK_STR:  0x7f_8
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    PROCESS_NAME:  w3wp.exe
    CURRENT_IRQL:  1
    EXCEPTION_RECORD:  fffffa60122c30a8 -- (.exr 0xfffffa60122c30a8)
    ExceptionAddress: fffff80001e8767d (nt!RtlVirtualUnwind+0x000000000000016d)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000000d8
    Attempt to read from address 00000000000000d8
    TRAP_FRAME:  fffffa60122c2080 -- (.trap 0xfffffa60122c2080)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000000
    rdx=00000000000000d8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80001e8767d rsp=fffffa60122c2210 rbp=fffffa60122c2450
     r8=0000000000000005  r9=fffff80001e08000 r10=ffffffffffffff80
    r11=fffff80002006000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!RtlVirtualUnwind+0x16d:
    fffff800`01e8767d 488b02          mov     rax,qword ptr [rdx] ds:00000000`000000d8=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80001e5f86e to fffff80001e5fad0
    STACK_TEXT: 
    fffffa60`01f1da68 fffff800`01e5f86e : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
    fffffa60`01f1da70 fffff800`01e5e0b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
    fffffa60`01f1dbb0 fffff800`01e8b4af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
    fffffa60`122bdf40 fffff800`01e98d32 : fffffa60`122bed68 fffffa60`122bee90 fffffa60`122bee10 00000000`00000000 : nt!RtlDispatchException+0x2f
    fffffa60`122be630 fffff800`01e5f929 : fffffa60`122bed68 00000000`00000003 fffffa60`122bee10 00000000`00000114 : nt!KiDispatchException+0xc2
    fffffa60`122bec30 fffff800`01e5e725 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiExceptionDispatch+0xa9
    fffffa60`122bee10 fffff800`01e8767d : 00000000`00059d17 fffffa60`122bf078 fffff800`01e08000 fffff800`01e08000 : nt!KiPageFault+0x1e5
    fffffa60`122befa0 fffff800`01e8b598 : fffffa60`00000001 00000000`00000000 00000000`00000000 ffffffff`ffffff80 : nt!RtlVirtualUnwind+0x16d
    fffffa60`122bf010 fffff800`01e98d32 : fffffa60`122bfe38 fffffa60`122bf810 fffffa60`00000000 00000000`00000000 : nt!RtlDispatchException+0x118
    fffffa60`122bf700 fffff800`01e5f929 : fffffa60`122bfe38 00000000`00000003 fffffa60`122bfee0 00000000`00000114 : nt!KiDispatchException+0xc2
    fffffa60`122bfd00 fffff800`01e5e725 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiExceptionDispatch+0xa9
    fffffa60`122bfee0 fffff800`01e8767d : 00000000`00059d17 fffffa60`122c0148 fffff800`01e08000 fffff800`01e08000 : nt!KiPageFault+0x1e5
    fffffa60`122c0070 fffff800`01e8b598 : fffffa60`00000001 00000000`00000000 00000000`00000000 ffffffff`ffffff80 : nt!RtlVirtualUnwind+0x16d
    fffffa60`122c00e0 fffff800`01e98d32 : fffffa60`122c0f08 fffffa60`122c08e0 fffffa60`00000000 00000000`00000000 : nt!RtlDispatchException+0x118
    fffffa60`122c07d0 fffff800`01e5f929 : fffffa60`122c0f08 00000000`00000003 fffffa60`122c0fb0 00000000`00000114 : nt!KiDispatchException+0xc2
    fffffa60`122c0dd0 fffff800`01e5e725 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiExceptionDispatch+0xa9
    fffffa60`122c0fb0 fffff800`01e8767d : 00000000`00059d17 fffffa60`122c1218 fffff800`01e08000 fffff800`01e08000 : nt!KiPageFault+0x1e5
    fffffa60`122c1140 fffff800`01e8b598 : fffffa60`00000001 00000000`00000000 00000000`00000000 ffffffff`ffffff80 : nt!RtlVirtualUnwind+0x16d
    fffffa60`122c11b0 fffff800`01e98d32 : fffffa60`122c1fd8 fffffa60`122c19b0 fffffa60`00000000 00000000`00000000 : nt!RtlDispatchException+0x118
    fffffa60`122c18a0 fffff800`01e5f929 : fffffa60`122c1fd8 00000000`00000003 fffffa60`122c2080 00000000`00000114 : nt!KiDispatchException+0xc2
    fffffa60`122c1ea0 fffff800`01e5e725 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiExceptionDispatch+0xa9
    fffffa60`122c2080 fffff800`01e8767d : 00000000`00059d17 fffffa60`122c22e8 fffff800`01e08000 fffff800`01e08000 : nt!KiPageFault+0x1e5
    fffffa60`122c2210 fffff800`01e8b598 : fffffa60`00000001 00000000`00000000 00000000`00000000 ffffffff`ffffff80 : nt!RtlVirtualUnwind+0x16d
    fffffa60`122c2280 fffff800`01e98d32 : fffffa60`122c30a8 fffffa60`122c2a80 fffffa60`00000000 00000000`00000000 : nt!RtlDispatchException+0x118
    fffffa60`122c2970 fffff800`01e5f929 : fffffa60`122c30a8 00000000`00000003 fffffa60`122c3150 00000000`00000114 : nt!KiDispatchException+0xc2
    fffffa60`122c2f70 fffff800`01e5e725 : 00000000`00000000 fffffa60`122c31a0 fffffa80`69d06800 00000000`00000003 : nt!KiExceptionDispatch+0xa9
    fffffa60`122c3150 fffff800`01e8767d : 00000000`00059d17 fffffa60`122c33b8 fffff800`01e08000 fffffa60`122c3c80 : nt!KiPageFault+0x1e5
    fffffa60`122c32e0 fffff800`01e8b598 : fffffa60`00000001 00000000`00000000 fffffa60`00000000 ffffffff`ffffff80 : nt!RtlVirtualUnwind+0x16d
    fffffa60`122c3350 fffff800`01e98d32 : fffffa60`122c4178 fffffa60`122c3b50 fffffa60`00000000 fffffa60`0160a000 : nt!RtlDispatchException+0x118
    fffffa60`122c3a40 fffff800`01e5f929 : fffffa60`122c4178 00000000`00000003 fffffa60`122c4220 00000000`00000114 : nt!KiDispatchException+0xc2
    fffffa60`122c4040 fffff800`01e5e725 : 00000000`00000000 fffffa80`1cff1010 fffffa80`2340ae00 00000000`00000003 : nt!KiExceptionDispatch+0xa9
    fffffa60`122c4220 fffff800`01e8767d : 00000000`00059d17 fffffa60`122c4970 fffff800`01e08000 62206465`00000000 : nt!KiPageFault+0x1e5
    fffffa60`122c43b0 fffff800`020ec4b2 : fffff800`00000001 fffffa60`10893500 fffff880`00000000 ffffffff`ffffff80 : nt!RtlVirtualUnwind+0x16d
    fffffa60`122c4420 fffff800`01e8cf4d : ffffffff`ffffff80 fffffa80`695fe060 fffffa60`10893570 fffff800`01e08000 : nt!PspGetSetContextInternal+0x36a
    fffffa60`122c4970 fffff800`01e811ce : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspGetSetContextSpecialApc+0x9d
    fffffa60`122c4a80 fffff800`01e61faf : fffffa80`695fe310 00000000`00000000 00000000`00000000 fffffa80`695fe060 : nt!KiDeliverApc+0x19e
    fffffa60`122c4b20 fffff800`01e569bb : 00000000`00000007 fffffa60`0161e424 fffffa80`00000005 00000000`00000000 : nt!KiSwapThread+0x3ef
    fffffa60`122c4b90 fffff800`01e94dad : ffff0050`00000000 fffffa60`00000005 fffffa80`122c0000 fffffa60`00000000 : nt!KeWaitForSingleObject+0x2cb
    fffffa60`122c4c20 fffff800`01e81307 : 00000000`00000000 fffff880`082f6448 fffffa80`3ecdf064 00000000`00000000 : nt!KiSuspendThread+0x29
    fffffa60`122c4c60 fffff800`01e84c23 : fffffa60`122c4d80 00000000`00000000 fffff800`01e94d84 00000000`00000000 : nt!KiDeliverApc+0x2d7
    fffffa60`122c4d00 fffffa60`00c43093 : fffffa80`1ce4a180 fffffa60`01617601 fffffa80`5c527c40 fffff880`082f0100 : nt!KiApcInterrupt+0x103
    fffffa60`122c4e90 fffffa80`1ce4a180 : fffffa60`01617601 fffffa80`5c527c40 fffff880`082f0100 fffffa60`122c5390 : spep+0x40093
    fffffa60`122c4e98 fffffa60`01617601 : fffffa80`5c527c40 fffff880`082f0100 fffffa60`122c5390 fffffa80`1c000000 : 0xfffffa80`1ce4a180
    fffffa60`122c4ea0 fffff880`082f6140 : fffff880`082f6390 fffff800`01e6dc7c 00000000`00000000 fffffa80`69ae8110 : Ntfs!NtfsCleanupIrpContext+0xd1
    fffffa60`122c4ef0 fffff880`082f6390 : fffff800`01e6dc7c 00000000`00000000 fffffa80`69ae8110 fffffa80`69ae8420 : 0xfffff880`082f6140
    fffffa60`122c4ef8 fffff800`01e6dc7c : 00000000`00000000 fffffa80`69ae8110 fffffa80`69ae8420 fffffa80`67000d00 : 0xfffff880`082f6390
    fffffa60`122c4f00 fffff800`01e649a4 : fffffa80`1bf27000 fffffa60`122c4f68 fffffa80`1ce4a030 00000000`00000000 : nt!KiIpiProcessRequests+0x21c
    fffffa60`122c4f50 fffffa60`122c5220 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x114
    fffffa80`69ae8110 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa60`122c5220
    STACK_COMMAND:  kb
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    FOLLOWUP_NAME:  MachineOwner
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f79ae26
    FOLLOWUP_IP:
    nt!KiDoubleFaultAbort+b8
    fffff800`01e5e0b8 90              nop
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b8
    FAILURE_BUCKET_ID:  X64_TRAP_FRAME_RECURSION
    BUCKET_ID:  X64_TRAP_FRAME_RECURSION
    Followup: MachineOwner
    6: kd> .trap 0xfffffa60122c2080
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000000
    rdx=00000000000000d8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80001e8767d rsp=fffffa60122c2210 rbp=fffffa60122c2450
     r8=0000000000000005  r9=fffff80001e08000 r10=ffffffffffffff80
    r11=fffff80002006000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!RtlVirtualUnwind+0x16d:
    fffff800`01e8767d 488b02          mov     rax,qword ptr [rdx] ds:00000000`000000d8=????????????????

    Please understand that debugging is not officially supported in Technet forum, please contact Microsoft Customer Support Service (CSS) if you need any help on dump file debugging. To obtain the phone numbers for specific technology request, please refer
    to the website listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
    If you are outside the US, please refer to
    http://support.microsoft.com for regional support phone numbers.
    For your reference, you can start by implementing the following troubleshooting steps
    Run a chkdsk /r  with elevated privilege against the system drives to find out any filesystem corruption
    Run sfc /scannow to verify the protected Windows files from an administrative command prompt
    Do RAM test or use a third-party tool like MemTest86+
    Update BIOS and devices drivers.

  • Touchsmart 310-1110uk - BSoD caused by ntoskrnl.exe

    I have had seemingly random Blue Screens of Death when shutting down on my HP Touchsmart 310-1110uk over the last few months. Sometimes when shutting down, the "Shutting down..." message is displayed for a long time and then the BSoD appears. This only happens occasionally and most of the time it shuts down fine. The blue screen only ever appears when shutting down.
    It seemed to happen when Connectify was running but after looking into Connectify BSoD problems it seems that this bug was fixed after version 3, and I am running 3.3.0.23104 Pro. Therefore I don't think Connectify is the problem.
    I have uploaded the a .zip of the dump files from "C:\Windows\Minidumps" to Dropbox here:
    http://dl.dropbox.com/u/9154836/Minidump.zip
    I have also downloaded BlueScreenView to try and analyse the error logs. Most of the crashes seem to be the same with the following:
    Bug Check String: DRIVER_POWER_STATE_FAILURE
    Bug Check Code: 0x0000009f
    Caused By Driver: ntoskrnl.exe
    Caused By Address: [mostly "ntoskrnl.exe+7cd40" or "ntoskrnl.exe+7cc40"]
    I have uploaded the full HTML BlueScreenView report here:
    http://dl.dropbox.com/u/9154836/report.html
    I haven't installed many programs which might have caused the problem. This has been happening since November 2011 and the only thing I installed around then was Connectify.
    From what I can tell it seems to be a driver issue, but because this only happens occasionally (at seemingly random times when shutting down) it's almost impossible to troubleshoot by disabling individual drivers (i.e. trial and error).
    I would appreciate some help on this, if you could provide some guidance on fixing this or ask for more specific information.

    I have had seemingly random Blue Screens of Death when shutting down on my HP Touchsmart 310-1110uk over the last few months. Sometimes when shutting down, the "Shutting down..." message is displayed for a long time and then the BSoD appears. This only happens occasionally and most of the time it shuts down fine. The blue screen only ever appears when shutting down.
    It seemed to happen when Connectify was running but after looking into Connectify BSoD problems it seems that this bug was fixed after version 3, and I am running 3.3.0.23104 Pro. Therefore I don't think Connectify is the problem.
    I have uploaded the a .zip of the dump files from "C:\Windows\Minidumps" to Dropbox here:
    http://dl.dropbox.com/u/9154836/Minidump.zip
    I have also downloaded BlueScreenView to try and analyse the error logs. Most of the crashes seem to be the same with the following:
    Bug Check String: DRIVER_POWER_STATE_FAILURE
    Bug Check Code: 0x0000009f
    Caused By Driver: ntoskrnl.exe
    Caused By Address: [mostly "ntoskrnl.exe+7cd40" or "ntoskrnl.exe+7cc40"]
    I have uploaded the full HTML BlueScreenView report here:
    http://dl.dropbox.com/u/9154836/report.html
    I haven't installed many programs which might have caused the problem. This has been happening since November 2011 and the only thing I installed around then was Connectify.
    From what I can tell it seems to be a driver issue, but because this only happens occasionally (at seemingly random times when shutting down) it's almost impossible to troubleshoot by disabling individual drivers (i.e. trial and error).
    I would appreciate some help on this, if you could provide some guidance on fixing this or ask for more specific information.

  • BSOD SYSTEM_SERVICE_EXEPTION possibly caused by ntoskrnl.exe?

    Encounter 3 BSOD in a row within one single day.
    bluescreenview says ntoskrnl.exe was related during BSOD happened.
    BSOD just like happens every 3-4 hours, when I am opening, virtual box, VS 2013 Ultimate, Eclipse, Apache 2.4, PHP-cgi 5.5.15, MySQL 5.6.
    I suspected it was a hardware driver issues, so I tried remove my PCI-E creative sound card and uninstall its driver with only keyboard and mouse attached, but it still happen just moment ago.
    Moreover, it also happens before I install MSI Afterburner, so I don't think it was the cause.
    Any suggestions?
    Thank you very much.
    My spec
    I5-4670
    GTX-770
    AsRock Fatal1ty H87 Performance
    Crucial M4
    Win 8.1 Pro, fully patched
    Minidump attached.
    https://onedrive.live.com/redir?resid=609F4764A5939498!667&authkey=!AAO2J98g9BTc_d4&ithint=folder%2cdmp

    Hi,
    SYSTEM_SERVICE_EXCEPTION (3b)
    This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
    BugCheck 3B, {c0000005, fffff800d504d553, ffffd0002160fd50, 0}
    0: kd> ln fffff800d504d553
    (fffff800`d504d280) afd!AfdPoll64+0x2d9 | (fffff800`d504dad0) afd!AfdCheckPollEvents
    The exception occurred in afd!AfdPoll64+0x2d9.
    1. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented
    with the latest video card driver and many previous versions, please give the beta driver for your card a try.
    2. Navigate to services.msc and disable the nVidia Streaming Service, and then restart the computer.
    3. RTCore64.sys is listed and loaded which is RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Windows 7, 8, and 8.1). Please uninstall ASAP!
    4.
    0: kd> lmvm vuhub
    start end module name
    fffff800`d6400000 fffff800`d640f000 vuhub (deferred)
    Image path: vuhub.sys
    Image name: vuhub.sys
    Timestamp: Fri Nov 16 10:31:13 2007
    Eltima Software USB to Ethernet Connector driver, dated from 2007. This driver either needs to be updated, or if not available, completely uninstalled. It's not compatible with Windows 8/8.1.
    http://wiki.eltima.com/user-guides/usb-to-ethernet.html
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Thinkpad T60 Blue Screening when Idle. CSRSS.exe probable cause

    Hi All,
    I have a customer who leaves his computer on at work overnight and has received blue screens every night when he leaves his laptop.  Once he reboots, the laptop is fine until he leaves it idle again. 
    The bugcheck is BugCheck F4, {3, 86b9cab8, 86b9cc2c, 805d164c} and the probable cause is csrss.exe as noted in the minidump ( I still have to load symbols for the debug).
    I have updated bios and all necessary drivers and it still blue screens.  Any idea why this BSOD is still occurring?
    Any information is appreciated.
    Thanks,
    Phil

  • Windows 7 Ult 64 memory mgmt errors ntoskrnl.exe nt+75BC0

    Using WhoCrashed I get this error once in a while.  Where should I post this question?
    On Mon 4/14/2014 3:41:15
    PM GMT your computer crashed
    crash dump file:
    C:\Windows\Minidump\041414-5584-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x1A
    (0x411, 0xFFFFF6800014DFF8, 0xF86000032C9C8886, 0xFFFFF8A025364283)
    Error:
    MEMORY_MANAGEMENT
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a severe memory management
    error occurred.
    This might be a case of memory corruption. More often memory
    corruption happens because of software errors in buggy drivers, not because of
    faulty RAM modules.
    The crash took place in the Windows kernel. Possibly
    this problem is caused by another driver that cannot be identified at this time.
    I got this two days earlier.
    On Sat 4/12/2014 12:36:47
    AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\041114-6115-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x1A
    (0x5003, 0xFFFFF70001080000, 0x161, 0x163000000C2)
    Error: MEMORY_MANAGEMENT
    file path:
    C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that a severe memory management
    error occurred.
    This might be a case of memory corruption. More often memory
    corruption happens because of software errors in buggy drivers, not because of
    faulty RAM modules.
    The crash took place in the Windows kernel. Possibly
    this problem is caused by another driver that cannot be identified at this time.

    We do need the actual DMP file as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.
    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
    If you are using Blue screen view, who crashed, or a similar application don't.  They are wrong at least as often as they are correct
    Wanikiya and Dyami--Team Zigzag

  • BSOD ntoskrnl.exe?

    Got a bsod with 0x00000124 .
    Heard blue screen viewer can be wrong sometimes but it said ntoskrnl.exe was the problem?
    Not sure if I'm using this thing correctly but this is the minidump http://1drv.ms/1wvmcmq
    Also am running driver verifier and restarted.
    It's suppose to take a while right?
    And can I continue playing while it runs?

    Cshn
    This was called a BCC124 and it is related to hardware.  SInce the DMP references Genuine Intel I would start by running a CPU stress test
    Try this free stress test:  http://www.mersenne.org/freesoft/
    Prime95 Setup;
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
    The Test selection box and the stress.txt file describes what components that the program stresses.
    Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see
    if that helps.
    If you continue to get BSODs here are some more things you may want to consider.
    This is usually heat related, defective hardware, memory or even processor though
    it is"possible" that it is driver related (rare).
    Stop 0x124 - what it means and what to try
    Synopsis:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
     Generic "Stop 0x124" Troubleshooting Strategy:
    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
    ways.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
    free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications,
    games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether
    the machine is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
    Should you find yourself in the situation of having performed all of the steps
    above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
    More advanced reading can be found here from a MS MVP IT PRO
    http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\110414-2854-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e53890
    Debug session time: Tue Nov 4 01:05:10.806 2014 (UTC - 5:00)
    System Uptime: 0 days 0:26:06.602
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa800703c028, ba000000, 58000402}
    Probably caused by : GenuineIntel
    Followup: MachineOwner
    6: kd> !analyze -v
    * Bugcheck Analysis *
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800703c028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000058000402, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR: 0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: chrome.exe
    CURRENT_IRQL: f
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    STACK_TEXT:
    fffff880`0310ab58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME: GenuineIntel
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    IMAGE_VERSION:
    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae
    FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • BSOD "ntoskrnl.exe" - system recovery did not work

    Hi, I keep getting BSOD repeatedly whenever i log into windows normally. I can only access my laptop through safe mode w/networking. anyways i have narrowed the problem down to the driver "ntoskrnl.exe" However I dont know what is causing the problem
    and how to fix it.
    here is the link from my onedrive for kernel dump file:
    https://onedrive.live.com/redir?resid=9997264A2CACAA02%21116
    Dump File         : 082614-111447-01.dmp
    Crash Time        : 8/26/2014 3:04:11 PM
    Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code    : 0x0000000a
    Parameter 1       : 00000000`00000000
    Parameter 2       : 00000000`00000002
    Parameter 3       : 00000000`00000001
    Parameter 4       : fffff800`032e1c3f
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+75bc0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\082614-111447-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 287,608
    Dump File Time    : 8/26/2014 3:17:08 PM

    NHJ
    These crash was caused by your Symantec killing  netio.sys.  I would remov Symantec and use MSE in its place
    Symantec  is a frequent cause of BSOD's.  
    I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
    http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
    http://www.microsoft.com/security_essentials/
    For Norton 360 use this http://symantec.pcperformancetools.com/norton-360-how-to-uninstall.html
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\082614-111447-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    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 (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a6890
    Debug session time: Tue Aug 26 15:04:11.347 2014 (UTC - 4:00)
    System Uptime: 0 days 0:02:27.283
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {0, 2, 1, fffff800032e1c3f}
    *** WARNING: Unable to verify timestamp for SYMNETS.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
    Probably caused by : NETIO.SYS ( NETIO!WfpExpireEntryLru+17 )
    Followup: MachineOwner
    1: 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: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff800032e1c3f, address which referenced memory
    Debugging Details:
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003510100
    GetUlongFromAddress: unable to read from fffff800035101c0
    0000000000000000 Nonpaged pool
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+4f
    fffff800`032e1c3f 488713 xchg rdx,qword ptr [rbx]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0xA
    PROCESS_NAME: System
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    TRAP_FRAME: fffff8800a7f3230 -- (.trap 0xfffff8800a7f3230)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800a138b50 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff8800a7f3430 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800032e1c3f rsp=fffff8800a7f33c0 rbp=0000000000000008
    r8=fffff8800a7f3430 r9=fffff88001d8aca0 r10=0000000000000000
    r11=0000000000000040 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f:
    fffff800`032e1c3f 488713 xchg rdx,qword ptr [rbx] ds:00000000`00000000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff800032d8169 to fffff800032d8bc0
    STACK_TEXT:
    fffff880`0a7f30e8 fffff800`032d8169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0a7f30f0 fffff800`032d6de0 : 00000000`00000010 fffff880`0a7f3420 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0a7f3230 fffff800`032e1c3f : 00000000`00000003 00000000`00000002 00000000`00000003 00000000`00000002 : nt!KiPageFault+0x260
    fffff880`0a7f33c0 fffff880`01b419c7 : 00000000`00000008 fffff880`0a7f36a0 00000000`00008900 fffffa80`081b47c8 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f
    fffff880`0a7f3410 fffff880`01ce608d : fffffa80`0bfe79d0 fffffa80`0c08b8a0 fffff880`0a7f36a0 00000000`00008900 : NETIO!WfpExpireEntryLru+0x17
    fffff880`0a7f3460 fffff880`01cad7b7 : 00000000`00000004 fffff880`01b10030 fffffa80`0bfe7a20 00000000`00000001 : tcpip!WfpAleCloseRemoteEndpointConnection+0x2d
    fffff880`0a7f3490 fffff880`01d25e5b : fffffa80`0bfe79d0 fffffa80`0b9e2cda 00000000`00000001 fffffa80`0bfe79d0 : tcpip! ?? ::FNODOBFM::`string'+0x20f72
    fffff880`0a7f35e0 fffff880`01d261e2 : 00000089`00000000 fffffa80`0b9e2c10 fffffa80`089266a0 00000000`00000001 : tcpip!WfpAleHandleSendCompletion+0xeb
    fffff880`0a7f3700 fffff880`01d306b2 : fffff880`0a7f3ba8 00000000`00000001 00000000`00000000 fffffa80`08159f18 : tcpip!WfpAlepAuthorizeSendCompletion+0x32
    fffff880`0a7f3750 fffff880`01ba7af2 : fffffa80`00000089 fffff800`00000089 fffffa80`0bc9d370 00000000`00000001 : tcpip!WfpAleCompleteOperation+0x162
    fffff880`0a7f37f0 fffff880`076e67bb : 00000000`00000000 00000000`00000000 fffffa80`0bc737c0 00000000`00000030 : fwpkclnt!FwpsCompleteOperation0+0x1e
    fffff880`0a7f3820 00000000`00000000 : 00000000`00000000 fffffa80`0bc737c0 00000000`00000030 00000000`00000089 : SYMNETS+0x1e7bb
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    NETIO!WfpExpireEntryLru+17
    fffff880`01b419c7 488b4310 mov rax,qword ptr [rbx+10h]
    SYMBOL_STACK_INDEX: 4
    SYMBOL_NAME: NETIO!WfpExpireEntryLru+17
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: NETIO
    IMAGE_NAME: NETIO.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP: 5294760d
    IMAGE_VERSION: 6.1.7601.18327
    FAILURE_BUCKET_ID: X64_0xA_NETIO!WfpExpireEntryLru+17
    BUCKET_ID: X64_0xA_NETIO!WfpExpireEntryLru+17
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0xa_netio!wfpexpireentrylru+17
    FAILURE_ID_HASH: {fcdee258-ad7b-b100-5f3a-ac9544c5fd1f}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • BSOD DRIVER_POWER_STATE FAILURE 0x1000009f ntoskrnl.exe

    Hi there,
    I get a BSOD every once in a while, but only for a few weeks by now:
    Sometimes while working on the computer it just freezes (not using any certain program), I can't use my mouse/ keyboard, sound stops, waiting a long time sometimes helps, but after 10-15 minutes I usually give up and reset.
    Then rebooting most of the time does not work propperly: The computer waits about 30secs showing my motherboard instructions (BIOS key, boot menu key, ...), then freezes for about 5-10 minutes showing the windows logo and saying something like "windows
    is starting up" (the black screen with the 4 colored windows logo). Sometimes it doesn't continue from there at all. If it does the computer runs fine (after the 10min boot). Otherwise I reset it again, Windows asks whether I want to start normal or safe
    mode, normal works.
    Yesterday windows told me while booting that I'd need to do a system restore, did that. Works for now, but I'd like to really solve the problem.
    Checking the last crashes I always have the same BSOD:
    Problemsignatur
    Problemereignisame:    BlueScreen
    Betriebsystemversion:    6.1.7601.2.1.0.256.1
    Gebietsschema-ID:    1031
    Weitere Informationen über das Problem
    BCCode:    1000009f
    BCP1:    0000000000000004
    BCP2:    0000000000000258
    BCP3:    FFFFFA8003CFF040
    BCP4:    FFFFF80000B9C510
    OS Version:    6_1_7601
    Service Pack:    1_0
    Product:    256_1
    Bucket-ID:    X64_0x9F_4_IMAGE_nvstor.sys
    Serverinformationen:    7ef390d9-572b-4571-853a-9a9c91b1c365
    I'm not really into understanding the Minidump, just saw it it the ntoskrnl.exe at ntoskrnl.exe+ 78a8a causing the problem. My Minidump: https://www.dropbox .com/s/1351wa0e47hs4qt/042614-411998-01.dmp (delete the space behind dropbox. Can't upload files...)
    My system:
    AMD Athlon II X2 250 (3.0Ghz)
    Asus M4N68T-M LE V2
    Sapphire/ AMD HD4850
    2x2GB RAM
    anything missing?
    Thanks for your help!

    Thanks very much for the kernel-dump!
    DRIVER_POWER_STATE_FAILURE (9f)
    This bug check indicates that the driver is in an inconsistent or invalid power state.
    0: kd> knL
    # Child-SP RetAddr Call Site
    00 fffff800`00b9c4d8 fffff800`02d117e6 nt!KeBugCheckEx
    01 fffff800`00b9c4e0 fffff800`02ec234c nt!PnpBugcheckPowerTimeout+0x76
    02 fffff800`00b9c540 fffff800`02c8a85c nt!PopBuildDeviceNotifyListWatchdog+0x1c
    03 fffff800`00b9c570 fffff800`02c8a6f6 nt!KiProcessTimerDpcTable+0x6c
    04 fffff800`00b9c5e0 fffff800`02c8a5de nt!KiProcessExpiredTimerList+0xc6
    05 fffff800`00b9cc30 fffff800`02c8a3c7 nt!KiTimerExpiration+0x1be
    06 fffff800`00b9ccd0 fffff800`02c778ca nt!KiRetireDpcList+0x277
    07 fffff800`00b9cd80 00000000`00000000 nt!KiIdleLoop+0x5a
    Not really much info in the call stack, just a few PnP routines that call into the bugcheck eventually. No driver in the stack, etc.
    0: kd> !locks
    **** DUMP OF ALL RESOURCE OBJECTS ****
    KD: Scanning for held locks..
    Resource @ nt!IopDeviceTreeLock (0xfffff80002e83ce0) Shared 1 owning threads
    Threads: fffffa8003cff040-01<*>
    KD: Scanning for held locks.
    Resource @ nt!PiEngineLock (0xfffff80002e83be0) Exclusively owned
    Contention Count = 11
    NumberOfExclusiveWaiters = 1
    Threads: fffffa8003cff040-01<*>
    Threads Waiting On Exclusive Access:
    fffffa8003cfe660
    0: kd> !thread fffffa8003cff040
    THREAD fffffa8003cff040 Cid 0004.002c Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode Non-Alertable
    fffff88002fd21f0 SynchronizationEvent
    Not impersonating
    DeviceMap fffff8a0000060c0
    Owning Process fffffa8003cecb30 Image: System
    Attached Process N/A Image: N/A
    Wait Start TickCount 5039734 Ticks: 38462 (0:00:10:00.011)
    Context Switch Count 356079 IdealProcessor: 0 NoStackSwap
    UserTime 00:00:00.000
    KernelTime 00:00:05.896
    Win32 Start Address nt!ExpWorkerThread (0xfffff80002c89150)
    Stack Init fffff88002fd2db0 Current fffff88002fd1f10
    Base fffff88002fd3000 Limit fffff88002fcd000 Call 0
    Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP RetAddr : Args to Child : Call Site
    fffff880`02fd1f50 fffff800`02c755f2 : fffffa80`03cff040 fffffa80`03cff040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
    fffff880`02fd2090 fffff800`02c8699f : fffffa80`07524c80 fffff800`02c64a72 00000000`00000000 fffffa80`04686000 : nt!KiCommitThreadWait+0x1d2
    fffff880`02fd2120 fffff880`010dbf21 : fffffa80`06ea6600 00000000`00000000 fffff880`02fd2600 fffffa80`06ea6600 : nt!KeWaitForSingleObject+0x19f
    fffff880`02fd21c0 fffff880`010ddb41 : 00000000`00000000 fffff880`02fd2620 fffff880`010e9a60 00000000`00000000 : storport!RaSendIrpSynchronous+0x71
    fffff880`02fd2220 fffff880`010e13f1 : 00000000`00000000 fffff880`00000000 fffff880`02fd24c0 fffff880`02fd2628 : storport!RaidBusEnumeratorIssueSynchronousRequest+0x91
    fffff880`02fd2330 fffff880`010e151e : fffffa80`068d2ad0 fffff880`00000000 fffff880`02fd2420 fffff880`02fd24c0 : storport!RaidBusEnumeratorIssueReportLuns+0x71
    fffff880`02fd2380 fffff880`010e789b : 00000000`00000000 fffff6fc`00000000 00000000`00000000 fffff880`02fd24c0 : storport!RaidBusEnumeratorGetLunListFromTarget+0xae
    fffff880`02fd2400 fffff880`010e79e4 : fffff800`02eba540 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidBusEnumeratorGetLunList+0x5b
    fffff880`02fd2490 fffff880`010e7ad6 : fffffa80`047a81b0 00000000`00000001 00000000`00000000 fffffa80`047a81b0 : storport!RaidAdapterEnumerateBus+0x94
    fffff880`02fd2600 fffff880`01126812 : 00000000`00000000 fffff880`010ce8f1 fffff880`01126b20 00000000`000000ca : storport!RaidAdapterRescanBus+0x76
    fffff880`02fd2710 fffff880`01126a20 : fffffa80`055de090 00000000`00000000 fffffa80`047a81b0 fffffa80`055de090 : storport!RaidAdapterQueryDeviceRelationsIrp+0xa2
    fffff880`02fd2750 fffff880`01126bb4 : fffffa80`055de090 fffff880`010ec110 fffffa80`047a8060 00000000`00010286 : storport!RaidAdapterPnpIrp+0x150
    fffff880`02fd27b0 fffff800`0303c18e : fffffa80`055de090 fffffa80`0652cdc0 fffffa80`047a8060 fffff880`009ed180 : storport!RaDriverPnpIrp+0x94
    fffff880`02fd27f0 fffff800`0303c4fa : 00000000`00000000 fffffa80`0652cdc0 fffff800`02d7fed0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`02fd2830 fffff800`0303e847 : fffff800`02e839a0 fffffa80`03cb7b10 00000000`00000002 00000000`00000540 : nt!PnpQueryDeviceRelations+0xfa
    fffff880`02fd28f0 fffff800`0306ee3c : fffffa80`03cb7b10 fffffa80`03cb003c fffffa80`03cb7b10 00000000`00000002 : nt!PipEnumerateDevice+0x117
    fffff880`02fd2950 fffff800`0306f448 : fffff800`02e81560 00000000`00000000 00000000`00000001 fffff800`02eeae08 : nt!PipProcessDevNodeTree+0x21c
    fffff880`02fd2bc0 fffff800`02d82827 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
    fffff880`02fd2c10 fffff800`02c89261 : fffff800`02d82500 fffff800`02e25201 fffffa80`03cff000 fffffa80`00000000 : nt!PnpDeviceActionWorker+0x327
    fffff880`02fd2cb0 fffff800`02f1c2ea : 3155082d`4e082847 fffffa80`03cff040 00000000`00000080 fffffa80`03cecb30 : nt!ExpWorkerThread+0x111
    fffff880`02fd2d40 fffff800`02c708e6 : fffff880`009ed180 fffffa80`03cff040 fffff880`009f7f40 396b8f38`688d3667 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fd2d80 00000000`00000000 : fffff880`02fd3000 fffff880`02fcd000 fffff880`02fd29e0 00000000`00000000 : nt!KxStartSystemThread+0x16
    There's no IRP list to run !irp on, however, we have a bit more of an informative call stack. We can see various
    storport.sys (Microsoft Storage Port driver) calls. With that said, it looks like we may have possibly had an I/O request (ultimately an IRP) sent along the Disk, and to the storage driver. Now, the better question is, what did
    storport.sys do with it? Unfortunately, with no IRP list, I don't know!
    In the mean time, if you crash again, here's what I can tell you:
    1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.
    Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:
    C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
    and rename AODDriver2.sys to AODDriver.2old
    and then Restart.
    2. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes as it's very likely causing file system conflicts:
    Avira removal - http://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/88
    MSE -http://windows.microsoft.com/en-us/windows/security-essentials-download
    3.
    0: kd> lmvm asacpi
    start end module name
    fffff880`04232000 fffff880`0423a000 ASACPI (deferred)
    Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
    Image name: ASACPI.sys
    Timestamp: Sun Mar 27 22:30:36 2005
    ASACPI.sys is dated from 2005, Asus ATK0110 ACPI Utility (a known
    BSOD maker in Win7 and Win8). Also a part of many Asus utilities. The pre-2009 driver causes many BSOD's. With that said, either update your utilities via Asus' website, or uninstall
    all of them ASAP. I recommend the latter as Asus' bloatware is generally useless.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Windows Server 2008 Enterprise SP2 64bit BugCheck 3B Probably caused by : win32k.sys ( win32k!PFFOBJ::pPvtDataMatch+12 )

    Hi Guys,
    Has anyone come across this BSOD error and found a fix, as I'm at a lost as to what is causing the BSOD
    Please see Windows Debugger output below:-
    Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Transfer\Minidumps\Mini051414-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer
    Built by: 6002.23154.amd64fre.vistasp2_ldr.130707-1535
    Machine Name:
    Kernel base = 0xfffff800`01c18000 PsLoadedModuleList = 0xfffff800`01dd7e30
    Debug session time: Wed May 14 12:01:16.178 2014 (UTC + 1:00)
    System Uptime: 3 days 7:15:01.532
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff9600030271e, fffffa603d967ec0, 0}
    Probably caused by : win32k.sys ( win32k!PFFOBJ::pPvtDataMatch+12 )
    Followup: MachineOwner
    7: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff9600030271e, Address of the instruction which caused the bugcheck
    Arg3: fffffa603d967ec0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    win32k!PFFOBJ::pPvtDataMatch+12
    fffff960`0030271e f6430804        test    byte ptr [rbx+8],4
    CONTEXT:  fffffa603d967ec0 -- (.cxr 0xfffffa603d967ec0)
    rax=fffff900c277dd10 rbx=6364735523080013 rcx=fffffa603d968790
    rdx=fffff900c2cc92a0 rsi=fffff900c2ade350 rdi=fffffa80369f6680
    rip=fffff9600030271e rsp=fffffa603d968720 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa80369f6680 r10=fffffa803b6cdc48
    r11=fffffa603d9687c8 r12=fffffa603d968810 r13=0000000000000000
    r14=000000000000301f r15=0000000000000001
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    win32k!PFFOBJ::pPvtDataMatch+0x12:
    fffff960`0030271e f6430804        test    byte ptr [rbx+8],4 ds:002b:63647355`2308001b=??
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT_SERVER
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  chrome.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff960003009b1 to fffff9600030271e
    STACK_TEXT: 
    fffffa60`3d968720 fffff960`003009b1 : 00000000`0000301f 00000000`00004fbc 00000000`00000000 fffffa80`3b6cdbb0 : win32k!PFFOBJ::pPvtDataMatch+0x12
    fffffa60`3d968750 fffff960`001aacb6 : fffff900`c2ade350 fffff900`c3fa59e0 00000000`00000000 fffffa80`369f6680 : win32k!PFTOBJ::bUnloadWorkhorse+0x55
    fffffa60`3d9687d0 fffff960`001ab8d8 : fffff900`c2ade2d0 00000000`00000000 00000000`00000001 00000000`00000001 : win32k!vCleanupPrivateFonts+0x72
    fffffa60`3d968810 fffff960`0019fbc0 : 00000000`00000000 fffff800`01ebfe00 fffff900`c277dd10 fffffa80`38d5b800 : win32k!NtGdiCloseProcess+0x4a8
    fffffa60`3d968870 fffff960`0019f423 : 00000000`00000000 fffff900`c277dd10 00000000`00000000 fffff800`01ebfe48 : win32k!GdiProcessCallout+0x1f4
    fffffa60`3d9688f0 fffff800`01ecc924 : 00000000`00000000 00000000`00000000 fffff800`01db6ec0 00000000`00000000 : win32k!W32pProcessCallout+0x6f
    fffffa60`3d968920 fffff800`01ebfe65 : fffffa60`00000000 fffff800`01c89701 fffffa80`57c73810 00000000`78457350 : nt!PspExitThread+0x41c
    fffffa60`3d968a10 fffff800`01c89881 : fffffa60`3d968ad8 00000000`00000000 fffffa80`382fe430 00000000`00000000 : nt!PsExitSpecialApc+0x1d
    fffffa60`3d968a40 fffff800`01c8d935 : fffffa60`3d968ca0 fffffa60`3d968ae0 fffff800`01ebfe74 00000000`00000001 : nt!KiDeliverApc+0x441
    fffffa60`3d968ae0 fffff800`01c6721d : fffffa80`3b6cdbb0 00000000`0038f2f4 fffffa60`3d968bf8 fffffa80`597301e0 : nt!KiInitiateUserApc+0x75
    fffffa60`3d968c20 00000000`74c93d09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xa2
    00000000`000eebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c93d09
    FOLLOWUP_IP:
    win32k!PFFOBJ::pPvtDataMatch+12
    fffff960`0030271e f6430804        test    byte ptr [rbx+8],4
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  win32k!PFFOBJ::pPvtDataMatch+12
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  52f4cf4d
    STACK_COMMAND:  .cxr 0xfffffa603d967ec0 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!PFFOBJ::pPvtDataMatch+12
    BUCKET_ID:  X64_0x3B_win32k!PFFOBJ::pPvtDataMatch+12
    Followup: MachineOwner
    7: kd> lmvm win32k
    start             end                 module name
    fffff960`000e0000 fffff960`0039a000   win32k     (pdb symbols)          c:\symbols\win32k.pdb\E3E9D4C3813E470A90F52FAEC6461A252\win32k.pdb
        Loaded symbol image file: win32k.sys
        Mapped memory image file: c:\symbols\win32k.sys\52F4CF4D2ba000\win32k.sys
        Image path: win32k.sys
        Image name: win32k.sys
        Timestamp:        Fri Feb 07 12:19:25 2014 (52F4CF4D)
        CheckSum:         002AD344
        ImageSize:        002BA000
        File version:     6.0.6002.23325
        Product version:  6.0.6002.23325
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     win32k.sys
        OriginalFilename: win32k.sys
        ProductVersion:   6.0.6002.23325
        FileVersion:      6.0.6002.23325 (vistasp2_ldr.140207-0038)
        FileDescription:  Multi-User Win32 Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    7: kd> .cxr 0xfffffa603d967ec0
    rax=fffff900c277dd10 rbx=6364735523080013 rcx=fffffa603d968790
    rdx=fffff900c2cc92a0 rsi=fffff900c2ade350 rdi=fffffa80369f6680
    rip=fffff9600030271e rsp=fffffa603d968720 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa80369f6680 r10=fffffa803b6cdc48
    r11=fffffa603d9687c8 r12=fffffa603d968810 r13=0000000000000000
    r14=000000000000301f r15=0000000000000001
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    win32k!PFFOBJ::pPvtDataMatch+0x12:
    fffff960`0030271e f6430804        test    byte ptr [rbx+8],4 ds:002b:63647355`2308001b=??
    Thanks
    JT

    Getting BSOD's pointing to this dll also. Started at around the same date as Jitinder's post. Maybe a new issue introduced has been introduced?
    7: kd> !analyze -v
    *                        Bugcheck Analysis                                    *
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff9600011fda0, Address of the instruction which caused the bugcheck
    Arg3: fffffa6027acd1d0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    "kernel32.dll" was not found in the image list.
    Debugger will attempt to load "kernel32.dll" at given base 00000000`00000000.
    Please provide the full image name, including the extension (i.e. kernel32.dll)
    for more reliable results.Base address and size overrides can be given as
    .reload <image.ext>=<base>,<size>.
    Unable to add module at 00000000`00000000
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP: 
    win32k!PFEOBJ::vFreepfdg+e8
    fffff960`0011fda0 0fba60300f      bt      dword ptr [rax+30h],0Fh
    CONTEXT:  fffffa6027acd1d0 -- (.cxr 0xfffffa6027acd1d0)
    rax=00000000014c0000 rbx=0000000000000000 rcx=fffff900c009c2a0
    rdx=fffffa802735ab80 rsi=fffff900c0b9b010 rdi=fffffa6027acda80
    rip=fffff9600011fda0 rsp=fffffa6027acda30 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=fffffa802800a288
    r11=fffffa802800a060 r12=0000000000000000 r13=0000000000000000
    r14=000000001539ed50 r15=0000000000000001
    iopl=0         nv up ei pl nz na po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
    win32k!PFEOBJ::vFreepfdg+0xe8:
    fffff960`0011fda0 0fba60300f      bt      dword ptr [rax+30h],0Fh ds:002b:00000000`014c0030=????????
    Resetting default scope
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  iexplore.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff960002e66d4 to fffff9600011fda0
    STACK_TEXT:  
    fffffa60`27acda30 fffff960`002e66d4 : 00000000`00000000 fffffa80`2735ab50 00000000`00000001 00000000`746e6647 : win32k!PFEOBJ::vFreepfdg+0xe8
    fffffa60`27acda60 fffff960`002f0cb7 : 00000000`00000000 fffff900`c008f000 fffff900`c0010000 00000000`00000000 : win32k!RFONTOBJ::vDeleteRFONT+0x210
    fffffa60`27acdac0 fffff960`002f0926 : 00000000`00000000 fffff900`c2bfcca0 fffff900`c0ae4010 00000000`00000000 : win32k!vRestartKillRFONTList+0xab
    fffffa60`27acdb10 fffff960`00275c79 : 00000000`00000000 00000000`00000001 fffffa80`235762b0 fffff900`00000002 : win32k!PFTOBJ::bUnloadWorkhorse+0x196
    fffffa60`27acdb90 fffff960`002978e2 : fffffa80`2800a060 fffff900`c0b932a0 fffffa60`27acdca0 00000000`7457c444 : win32k!GreRemoveFontMemResourceEx+0xad
    fffffa60`27acdbf0 fffff800`01a64173 : fffffa80`2800a060 fffffa60`27acdca0 00000000`7ee9f000 fffffa80`25803040 : win32k!NtGdiRemoveFontMemResourceEx+0x12
    fffffa60`27acdc20 00000000`74513d09 : 00000000`74513cc5 00000023`77300682 00000000`00000023 00000000`00000202 : nt!KiSystemServiceCopyEnd+0x13
    00000000`1539ed48 00000000`74513cc5 : 00000023`77300682 00000000`00000023 00000000`00000202 00000000`1767d5e0 : wow64cpu!CpupSyscallStub+0x9
    00000000`1539ed50 00000000`7457ab36 : 00000000`77120000 00000000`1539fd20 00000000`60c8f022 00000000`1539f450 : wow64cpu!Thunk0Arg+0x5
    00000000`1539edc0 00000000`7457a13a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64!RunCpuSimulation+0xa
    00000000`1539edf0 00000000`771847c8 : 00000000`00000000 00000000`00000000 00000000`7efdf000 00000000`00000000 : wow64!Wow64LdrpInitialize+0x4b6
    00000000`1539f350 00000000`771461be : 00000000`1539f450 00000000`00000000 00000000`7efdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x1fba1
    00000000`1539f400 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe
    FOLLOWUP_IP: 
    win32k!PFEOBJ::vFreepfdg+e8
    fffff960`0011fda0 0fba60300f      bt      dword ptr [rax+30h],0Fh
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  win32k!PFEOBJ::vFreepfdg+e8
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5202fc4d
    STACK_COMMAND:  .cxr 0xfffffa6027acd1d0 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
    BUCKET_ID:  X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
    Followup: MachineOwner
    7: kd> lmv m win32k
    start             end                 module name
    fffff960`000d0000 fffff960`00389000   win32k     (pdb symbols)          c:\symcache\win32k.pdb\54B8C53009264F08A9D8CF1B4B56BCDC2\win32k.pdb
        Loaded symbol image file: win32k.sys
        Image path: \SystemRoot\System32\win32k.sys
        Image name: win32k.sys
        Timestamp:        Thu Aug 08 04:02:53 2013 (5202FC4D)
        CheckSum:         002B126B
        ImageSize:        002B9000
        File version:     6.0.6002.18912
        Product version:  6.0.6002.18912
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     win32k.sys
        OriginalFilename: win32k.sys
        ProductVersion:   6.0.6002.18912
        FileVersion:      6.0.6002.18912 (vistasp2_gdr.130807-1537)
        FileDescription:  Multi-User Win32 Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    7: kd> .cxr 0xfffffa6027acd1d0
    rax=00000000014c0000 rbx=0000000000000000 rcx=fffff900c009c2a0
    rdx=fffffa802735ab80 rsi=fffff900c0b9b010 rdi=fffffa6027acda80
    rip=fffff9600011fda0 rsp=fffffa6027acda30 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=fffffa802800a288
    r11=fffffa802800a060 r12=0000000000000000 r13=0000000000000000
    r14=000000001539ed50 r15=0000000000000001
    iopl=0         nv up ei pl nz na po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
    win32k!PFEOBJ::vFreepfdg+0xe8:
    fffff960`0011fda0 0fba60300f      bt      dword ptr [rax+30h],0Fh ds:002b:00000000`014c0030=????????

  • An error occurred during olap API metadata retrieval. This is probably caus

    this is what i have done so far. i really nead some help asap!!!
    1. Install Oracle 9i Release 2 (9.2.0.1) Enterprise Edition with the General purpose database configuration (Data warehouse works as well). At the end of the installation I chose the password management button to change passwords for the few necessary accounts: SYS, SYSTEM, OLAPSYS, SH.
    2. Download the p3948480_9206_WINNT.zip from metalink, the 9.2.0.6 patchset
    3. Shut down any existing Oracle9i database instances with normal or immediate priority. Stop all listener and other services running in the Oracle home directory where you want to install the patch set.
    4. unzip the content of thepatch to a temp directory
    5. start setup.exe under the temp directory (it will start the Oracle Universal installer 10.1.0.3)
    6. install the patchset to your Oracle home, selecting the source in the temp_dir\stage\products.jar file
    7. review carefully the post-installation tasks for the patchset:
    Review the following sections before upgrading a database (quote from the patchset html readme):
    8.2.1.1If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.
    8.2.1.2 Check XDB Tablespace Size
    For RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
    8.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
    Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
    Start the database:
    SQL> STARTUP
    If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
    SQL> SHOW PARAMETER PFILE;
    This command displays the name and location of the server parameter file or the initialization parameter file.
    Determine the current values of these parameters:
    SQL> SHOW PARAMETER SHARED_POOL_SIZE
    SQL> SHOW PARAMETER JAVA_POOL_SIZE
    If the system is using a server parameter file:
    If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
    SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
    If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
    SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
    If the system uses an initialization parameter file, if necessary, change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).
    Shut down the database:
    SQL> SHUTDOWN
    8.2.2 Upgrade the Database
    After you install the patch set, you must complete the following steps on every database associated with the upgraded Oracle home:
    Log on as a member of the Administrators group to the computer where the Oracle components are installed.
    Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:
    sqlplus /NOLOG
    CONNECT SYS/password AS SYSDBA
    Enter the following SQL*Plus commands:
    SQL> STARTUP MIGRATE
    SQL> SPOOL patch.log
    SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sql
    SQL> SPOOL OFF
    Restart the database:
    SQL> SHUTDOWN
    SQL> STARTUP
    Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
    SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
    12. Install JDeveloper 9.0.4 (download it from OTN and just unzip it in a directory ... it doesn't require an oracle home)
    13. Install BI Beans 9.0.4 (download it from OTN as well), run the setup.exe that comes with it and in the destination oracle home select the directory where you installed JDeveloper and give an oracle home name to it)
    14. Install the BIBDEMO schema:
    Create a directory on the computer that is running the Oracle9i database. This install_home directory is the location to which you will upload the data files that are required to build the BIBDEMO schema.
    On the computer where BI Beans is installed, locate the bibeans_home\bibdemo_schema folder (where bibeans_home is the root folder of your BI Beans installation). Copy all of the files found in this folder to the install_home folder on your server machine.
    Open a DOS prompt and navigate to the install_home folder.
    Run bibdemo.bat to install the schema, using the following syntax:
    bibdemo.bat <path to Oracle database files >
    For example, for an instance named my9iService, enter the following:
    bibdemo.bat D:\OraHome1\oradata\my9iService
    You are prompted for the password for the sys as sysdba user.
    The script takes approximately 15 minutes to run, depending on the machine specifications. It is normal to see some error messages while the script is running. In addition, when materialized views are being created in the database, the script will appear to stop; this is also normal. A clear message will tell you when the script has completed.
    The log files (*.log) that are generated by the installation script are stored in the folder from which you ran the script.
    Here's what
    bi_checkconfig.bat -h ana -po 1521 -sid proiect -u bibdemo -p bibdemo -q
    returned:
    BI Beans Diagnostics(v1.0.2.0) 2/28/05
    ===============================================================================
    JDEV_ORACLE_HOME .......................... = E:\OraDS
    JAVA_HOME ................................. = E:\OraDS\jdk
    JDeveloper version ........................ = 9.0.4.1.1.1436
    BI Beans release description .............. = BI Beans 9.0.4 Production Release
    BI Beans component number ................. = 9.0.4.23.0
    BI Beans internal version ................. = 2.7.5.32
    Connect to database ....................... = Successful
    JDBC driver version ....................... = 9.2.0.4.0
    JDBC JAR file location .................... = E:\OraDS\jdev\lib\patches
    Database version .......................... = 9.2.0.6.0
    OLAP Catalog version ...................... = 9.2.0.1.0
    OLAP AW Engine version .................... = 9.2.0.1.0
    OLAP API Server version ................... = 9.2.0.1.0
    BI Beans Catalog version .................. = N/A; not installed in bibdemo
    OLAP API JAR file version ................. = 9.2
    OLAP API JAR file location ................ = E:\OraDS\jdev\lib\ext
    Load OLAP API metadata .................... = Successful
    Number of metadata folders ................ = 2
    Number of metadata measures ............... = 12
    Number of metadata dimensions ............. = 8
    Testing sample query for measures and dimensions
    (S=Schema, C=Cube, M=Measure, D=Dimension)
    1/21) Measure Budget ................... = Successful
    S=BIBDEMO, C=BIBDEMO_BUDGET_CUBE, M=BUDGET
    2/21) Measure Actual ................... = Successful
    S=BIBDEMO, C=BIBDEMO_ACTUAL_CUBE, M=ACTUAL
    3/21) Measure Close Price .............. = Successful
    S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_CLOSE
    4/21) Measure Open Price ............... = Successful
    S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_OPEN
    5/21) Measure Low Price ................ = Successful
    S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_LOW
    6/21) Measure High Price ............... = Successful
    S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_HIGH
    7/21) Measure Stock Volume ............. = Successful
    S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_VOLUME
    8/21) Dimension Division ............... = Successful
    S=BIBDEMO, D=DIVISION
    9/21) Dimension Line Items ............. = Successful
    S=BIBDEMO, D=LINE
    10/21) Dimension Time ................... = Successful
    S=BIBDEMO, D=TIME
    11/21) Dimension Day .................... = Successful
    S=BIBDEMO, D=DAY
    12/21) Dimension Stock .................. = Successful
    S=BIBDEMO, D=STOCK
    13/21) Measure Costs .................... = Successful
    S=BIBDEMO, C=ANALYTIC_CUBE, M=F.COSTS
    14/21) Measure Promotion ................ = Successful
    S=BIBDEMO, C=ANALYTIC_CUBE, M=F.PROMO
    15/21) Measure Quota .................... = Successful
    S=BIBDEMO, C=ANALYTIC_CUBE, M=F.QUOTA
    16/21) Measure Units .................... = Successful
    S=BIBDEMO, C=ANALYTIC_CUBE, M=F.UNITS
    17/21) Measure Sales .................... = Successful
    S=BIBDEMO, C=ANALYTIC_CUBE, M=F.SALES
    18/21) Dimension Channel ................ = Successful
    S=BIBDEMO, D=CHANNEL
    19/21) Dimension Geography .............. = Successful
    S=BIBDEMO, D=GEOGRAPHY
    20/21) Dimension Product ................ = Successful
    S=BIBDEMO, D=PRODUCT
    21/21) Dimension Time ................... = Successful
    S=BIBDEMO, D=TIME
    Metadata output location .................. = E:\OraDS\bibeans\bi_checkconfig\bi
    _metadata.txt
    To interpret this output, see the "Displaying Information about your Oracle9i Bu
    siness Intelligence Beans Client Configuration" technical note, whose file name
    is bi_checkconfig_tn.html
    These diagnostics are captured in: E:\OraDS\bibeans\bi_checkconfig\bi_checkconfi
    g.xml
    now: i have created some new stuff:
    1). user ana with roles:
    -dba
    -olap_dba
    -connect
    -resource
    (same roles as bibdemo)
    2).schema ana; tablespace ana (permanent), tablespace anatemp (temporary)
    3).i have created some relational tables and i have inserted some data in them:
    agent, aparat (cofee machines), beneficiar (clients), locatii (city), raport (REPORT), timp (time), tipaparat (types of cofee machines), tipbautura (products : types of cofee made by all the cofee machines), zone (state)
    4). one fact table with:
    - sold cantity (measure)
    - id_bautura (id_product) primary key
    - id_timp(id_time) primary key
    - id_beneficiar (id_client) primary key
    - id_agent primary key
    - id_locatie (id_city) primary key
    - id_aparat (id_cofee_machine)primary key
    i have inserted some data also
    5).dimensions:
    AGENT_DIM :levels: codag(id_agent), numeag (agent name), telefag (agent phone number)from relational table agent
    BENEFICIAR_DIM :levels: codben (id_client), denumire (client name), adresa (adress) ,codl (id_city) etc from relatinal table beneficiar (clients)
    TIMP_DIM :levels: id, year, month from relational table timp (time)
    TIPBAUTURA_DIM :levels: codbautura (id_product), numebautura (product name)from relational table tipbautura (products)
    ZONA_DIM :levels: codzona (id state), numezona (state name), codoras (id city), numeoras (city name) with ierarhy id_state---id_city FROM 2 RELATINAL TABLES CITY AND STATE!!!!!!!! AM I ALOUD TO DO THAT?????
    DO I NEED TO CREATE A DIMENSION FROM ONLY ONE TABLE???????
    APARAT_DIM :LEVELS: codben (id client), codtip (id machine type), denumireap (machine type name), matricolap ((machine id) (FROM 2 RELATIONAL TABLES ALSO!!!!!!! FROM TYPES OF COFEE MACHINES AND COFEE MACHINES!!!!!
    6). I HAVE NOW CREATED THE CUBE FROM THE FACT TABLE AND WITH ALL THE DIMENSIONS
    7). summary advisor wizard NOT WORKING! IT NEVER STOPS!
    8). I HAVE CREATED ALSO ONE materialized view FOR THE CUBE
    IF I COMPILE IT... NO ERRORS
    9). CUBE VIEWER NOT WORKING!!!!!!! IT ONLY APEARS A BELL!!!
    NOW IF I RUN BI_CHECK CONFIG ON ANA AND ALSO ON BIBDEMO!!!!!!!!!!!!
    IT SAYS:
    1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
    ============================================================================
    oracle.express.ExpressServerExceptionError class: Unknown Error
    Server error descriptions:
    INI: System failure, Generic at TxsOqConnection::getDefaultDatabase
    at oracle.express.olapi.data.full.ExpressDataProvider.getMetadataProviderInterface(ExpressDataProvider.java:1003)
    at oracle.olapi.metadata.MetadataFetcher.initialize(MetadataFetcher.java:73)
    at oracle.olapi.metadata.MetadataFetcher.<init>(MetadataFetcher.java:45)
    at oracle.olapi.metadata.BaseMetadataProvider.<init>(BaseMetadataProvider.java:47)
    at oracle.olapi.metadata.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:130)
    at oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider(ExpressDataProvider.java:964)
    at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getMdmMetadataProvider(MDMMetadataDriverImpl_92.java:1133)
    at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.attach(MDMMetadataDriverImpl_92.java:810)
    at oracle.dss.metadataManager.server.drivers.mdm.MDMMetadataDriverImpl.attach(MDMMetadataDriverImpl.java:125)
    at oracle.dss.metadataManager.server.MetadataManagerImpl.buildObjectModel(MetadataManagerImpl.java:1092)
    at oracle.dss.metadataManager.server.MetadataManagerImpl.attach(MetadataManagerImpl.java:969)
    at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:876)
    at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:799)
    at BICheckConfig.checkConnection(BICheckConfig.java:277)
    at BICheckConfig.main(BICheckConfig.java:1348)
    I TRYED ALSO WITH USER ANA WITH ROLES:
    - DBA
    - CONNECT
    -RESOURCE
    - OLAP_USER
    NOT WORKING! AND ALSO BIBDEMO NOT WORKING!
    WHAT AM I MISSING? SHOULD I USE AW MANAGER? OR DO I NEED TO CREATE AN AMNALITIC WORKSPACE???
    WHAT ARE THE STEPS TO CREATE A GOOD METADATA????

    Hi,
    The issue here is if the whole catalog is corrupt or just one schema. So to try and determine the status of the catalog I would try:
    1) Using OEM remove all the objects you created
    2) I presume you created your database using the Database Configuration Assistant? You should have used the warehouse template
    3) Make sure the following accounts are unlocked and also not expired : SH, OLAPSYS
    4) Make sure the password for the SH schema is SH
    5) Make sure the password for the OLAPSYS account is manager
    6) Install the BIBDEMO schema that is shipped with BI Beans. This in the jdev_home/bibeans/bibdemo_schema
    The installation process will remove SH schema from the OLAP catalog.
    7)Once this is installed use JDeveloper to see if you can create a crosstab or graph.
    8) If the BIBDEMO schema works try creating your new schemas one at a time.
    9) Make sure the if you define the a dimension as type time it has END_DATE (column type DATE) and TIME_SPAN (column type number) defined. Otherwise don't define the dimension as type time.
    Hope this helps
    Keith Laker
    Product Manager
    Oracle Business Intelligence Beans

  • Ntoskrnl.exe 100% disk usage windows 8.0 and 8.1

    This is a bug report. I hope Microsoft will take it seriously as it took me a whole day and much stress to track it down. Basically my problem was the same as this: http://slopjong.de/2013/04/23/extremely-high-disk-activity-with-windows-8-and-how-to-fix-it/
    However in the graphic on this site it appears to show that Virtualbox is the culprit. However this is unlikely to be the case, as the author of the site fixed his problem by following his own advice. This is an extremely common problem as this Google search
    indicates:
    https://www.google.co.uk/#q=ntoskrnl.exe+100+disk+usage+windows+8
    To attempt to address my own problem first I disabled all non-microsoft services in Windows 8.1 professional. When this had no effect on the problem, I then disabled all non-essential Microsoft services. In turn. when this has no effect I disabled all user
    installed start-up items. Again when this failed to have an impact, I changed my browser from Firefox to Google Chrome, as I noted that the extremely high disk utilisation was at it's worst when using Firefox. This also had no effect.
    I then tried a variation of my search on Google "ntoskrnl.exe 100 disk usage windows 8" (I can't remember the exact variation) and stumbled over the above site at the beginning of this message. I had by that point tried everything that was in my power
    to try. But I noted from this article that the author recommended changing the power plan from 'balanced', to 'high performance'. Since I had   exhausted every other avenue, I decided to try this and like magic, instantly it worked. So there is clearly
    a bug in Windows 8.1 (and 8 prior to this) that causes 100% disk utilisation. I thought someone at MS might like to know about it and come up with a way to fix it.
    Below is my system configuration. Please note this system configuration may contain a number of errors, as it was generated with several non-essential Microsoft services disabled. I do not believe these issues need to be addressed. However the issue of 100%
    disk utilisation when using a 'balanced' power plan on Windows 8.1 (and 8.0) almost certainly does.
    PS
    This message board system will not allow me to post my full system configuration. MS need a better bug reporting system! Apple allow the public to submit bug reports, so why not Microsoft too. The public can find useful bugs!

    Hi,
    Thanks for your detailed description.
    We considered that the culprit for every computer is different. For the specific PC, we need to analyze the specific issue.
    Please trace the performance using the Windows performance toolkit.
    http://msdn.microsoft.com/en-us/library/hh162945.aspx
    The download link is below:
    http://www.microsoft.com/en-US/download/details.aspx?id=39982
    Then upload the .etl file to Skydrive. We will help you analyze.
    Karen Hu
    TechNet Community Support

  • Windows 8.1 installation first reboot 0xc000007b ntoskrnl.exe missing or contains errors

    I'm trying to install Windows 8.1 (with updata 1) using UEFI on my Intel DP45SG.
    Starting up the installation by using UEFI works fine, but after the files have been copied and the system reboots I get the following error code: 0xc000007b ntoskrnl.exe missing or contains errors
    I've tried reformatting my USB stick and recopying the files, as well as re downloading the installation files but this hasn't resolved the problem.
    Is there anything I can try to fix this? Perhaps give some commands in the commands prompt?

    Hi Gi,
    It might be caused by changes in Windows 8 PnP in which Boot Start Drivers are not installed by default.
    Please try following
    the instructions as mentioned in the KB aticle.
    https://support.microsoft.com/en-us/kb/2751461?wa=wsignin1.0
    Regards,
    D. Wu
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • System (ntoskrnl.exe) high cpu usage in Windows 8.1

    Sir/Mam,
    I'm having this issue since last week, when i checked it is the "system" (ntoskrnl.exe) file which is using upto 18-24% of my CPU and causing all other applications to stutter for a second (incluuding Media player, mouse pointer, everything).
    By using a Process Explorer software i found out that it's related to these values running under that file:
    " ntoskrnl.exe!RtlSidHashLookup+0x1ffc  "
    It slows down my PC for a second and it happens after every 5-6 seconds (approx.).
    Using Microsoft Windows 8.1
    Lenovo Z50-70
    Need help.

    Hi,
    The WPA shows that it is WmiPrvSE.exe (WMI Provider Host)that occupies up to 20% CPU, and three threads are the causes, 8328\7988\8828. but hard to find deeper information from this, so please use process Explorer or process monitor to find more information
    about WmiPrvSE.exe and the 3 threads, you can refer to this link
    http://social.technet.microsoft.com/Forums/en-US/77f8bc7d-663c-4c33-b732-f362c5585300/service-host-local-system-is-intermittently-using-30-of-my-cpu-windows-81?forum=w8itproperf
    Regarding to the wireless or LAN driver, I suggest you update the driver to latest version if it doesn't work fine.
    Yolanda Zhu
    TechNet Community Support

Maybe you are looking for

  • Can I use it for both a backup drive and shared network drive?

    Is it possible to use the Time Capsule for both an automatic backup drive for my Mac AND use it as a shared network drive to store my large library of home videos?  If so, does it require partitioning the drive and are there instructions available? 

  • Driver for Hp cddvdw TS l633n drive.

    I need to find a different driver for the HP cddvdw Ts l633n drive that came in my laptop.  I'm running windows 7 64.  The driver that window provides does not work when trying to burn with nero10.  Does anyone know where I can find an HP driver?  Th

  • How to upload email from outlook to a sharepoint document library programatically.

    Hi , I have a requirement where I need to create a outlook plugin which will upload selected emails to sharepoint document library. I am able to hold email using by creating the object of outlook.item.  but could n't find a way to upload created com

  • Identifying the xml file

    String contextName = request.getContextPath(); String imageDir = contextName + "/resources/images"; String xmlName = "Resources.xml"; String contextDir = contextName + "/resources/xml/" + xmlName; String userName = (String) session.getAttribute("User

  • BerkeleyDB hangs trying to read corrupted database

    The provided corrupted database file causes reproducible hang in db->get method of Berkeley DB. Reproduced with Berkeley DB 4.8.30 and 4.3.29 under Linux. Corrupted database file: https://cfengine.com/bugtracker/file_download.php?file_id=123&type=bug