Starcraft 2 HotS problem (probably) caused by Killer E2200.

First of all i want to apologize if there already was similar topic but i could't find it.
Yesterday i bought MSI Z87 GD65 motherboard, i hooked up everything and started installing games, benchmarks etc.
Today i wanted to play some Starcraft 2 HotS with my friend and every time we try to start 2vs2 game (and SC2 is starting to download some stuff) skype is disconnecting us, also SC2 loses connection with Battle.net yet everything else (using internet) works just fine.
I think that this might be the problem with the Killer E2200.
My question is: am i the only one who got this issue?

Quote from: XFM on 20-June-13, 06:07:20
Have you tried re-installing drivers?
 List all of the components in your rig including brand and model of your PSU, see my signature below for example of listing components. Please make a similar signature.
      >> Posting Guide <<
Yes i did, twice.
So far i tested couple of multiplayer/MMO games and only SC2 HotS have this sort of issues.
Sorry for the lack of specs, i will put them a little bit later today.

Similar Messages

  • MSI Z87 Mpower Killer e2200 Connection problems

    Hi there, I've been having some major problems regarding the Bigfoot killer e2200 ethernet controller. I have loaded the latest drivers, but no matter what i do whenever i'm playing battlefield 4 i will lose my connection completely. I have set battlefield 4 to high priority in the killer network manager but nothing seems to help. After about 10 - 15 minutes of playing I lose the connection then it reconnects....
    I'm using a wired connection and have disabled the wireless on the board to eliminate that as the problem....
    Are there any drivers without the Killer Network manager.....
    This is driving me mad, I never had any problems at all regarding connection on my old gigabyte motherboad.

    Uninstall Killer software completely using >>Killer Cleaner<<. After reboot just install pure drivers you found: https://forum-en.msi.com/index.php?topic=174229.0 (prior uninstall with cleaner is a must!)

  • I keep getting this diologue box as I start up Firefox "Could not initialise the application's security component. The most probable cause is problems with files in your browser's profile directory. ... what should I do exactly?

    I keep getting the following dialogue box when I start Firefox " Could not initialise the application's security component. The most probable cause is problems with files in your browser's profile directory. Please check that this directory has no read/write restrictions." I am not sure how to find or change the profile directory. I have gone to the Options: General: Save files to ...box but it wont allow me to browse to another file and the box remains blank. ideas please!

    See [[Could not initialize the browser security component]]
    Continue here: [/questions/780717]

  • Why do I get an alert saying "Could not initialise the application's security component. The most probable cause is problems with files in your browser's profile directory. How can I solve it??

    The full alert is " Could not initialise the application's security component. The most probable cause is problems with files in your browser's profile directory. Please check that this directory has no read/write restrictions and your hard drive is not full or close to full. It is recommended that you exit the browser and fix the problem. If you continue to use this browser session, you might see incorrect browser behaviour when accessing security features."
    This is just started three/four days ago. I need assistance quickly as I can't access any secure sites e.g bank accounts/homepage etc.

    See [[Could not initialize the browser security component]]

  • HT201412 Have a problem with iPad2, apple logo appears but iPad won't boot up, then logo disappears & iPad dies - probably caused due to insufficient hard disk space (too many apps) - any help greatly appreciated

    I have a problem with iPad2, apple logo appears but iPad won't boot up, then logo disappears & iPad dies - probably caused due to insufficient hard disk space (foolishly loaded up too many apps) - any help/advice greatly appreciated

    What to Do When Your iPad Won't Turn On
    http://ipad.about.com/od/iPad_Troubleshooting/ss/What-To-Do-When-Your-Ipad-Wo-No t-Turn-On.htm
    iOS: Not responding or does not turn on
    http://support.apple.com/kb/TS3281
    iPad Frozen? How to Force Quit an App, Reset or Restart Your iPad
    http://ipadacademy.com/2010/11/ipad-frozen-how-to-force-quit-an-app-reset-or-res tart-your-ipad
    iPad: Basic troubleshooting
    http://support.apple.com/kb/TS3274
    Update and restore alert messages on iPhone, iPad, and iPod touch
    http://www.buybuyla.com/tech/view/012953a0d412000e.shtml
    iOS: Resolving update and restore alert messages
    http://support.apple.com/kb/TS1275
    iPad: Unable to update or restore
    http://support.apple.com/kb/ht4097
     Cheers, Tom

  • Certain web pages will not load and itunes and the appstore wont load either, what could be a probable cause and solution to this problem?

    certain web pages will not load and itunes and the appstore wont load either, what could be a probable cause and solution to this problem?

    the router is a netgear wireless extreme for pc and mac

  • 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.

  • Stop 0x0000001e (0xffffffffc0000005, 0xfffff8800a07d7f0 - Windows Server 2008r2 SP1 patch level March 2014 - WinDbg probably caused by mrxsmb10.sys

    we run several Windows Server 2008r2 SP1 Enterprise as VM on two Stratus Avance xenserver based VM hosts. On both hosts we run a VM as file-server, RDS server including a little bit of DFS traffic. the underling physical machines are Intel based S5520UR
    with plenty full of needed resources, running since 2012 more or less without problems.
    Recently we on both physical hosts the STOP error 0x0000001e (0xffffffffc0000005, 0xfffff8800a07d7f0, 0x0000000000000000, 0x0000000000000000).
    This has happended now twice and we have no clue or idea why the Stop error arrives now were the VM is running for month without such an error.
    We have tried to analyze the problem with WnDbg and the result reported: Probably caused by : mrxsmb10.sys ( mrxsmb10!MRxSmbDeferredCreate+18a )
    We have searched for a solution and have identified some hotfixes which could be related to our problem
    Hotfix http://support.microsoft.com/kb/2521220/en-us
    and / or
    Hotfix http://support.microsoft.com/kb/2764302/en-us
    The latter one matches the typical use of the VMs in question, file-server function and a flat file based database system with corresponding file I/O. (However, no dramatic system load and approx. 20 concurrent users on the system.)
    The file NTFS.sys in the folder System32 are with a newer date and version as the version from the hotfix and we are not sure if this would be a good idea to replace it with the hotfix version.
    As we are a small cap company we could not test the outcome of such a change of essential OS files and we tend to stay away from this approach. On the other hand we have a high pressure to solve this issue as we have to rely on the function of this core
    system.
    WinDbg points us towards mrxsmb10.sys as a possible root cause, but my believe is limited and we have not the knowledge to understand the output of the memory dump file. (mrxsmb was over the last 15 years always a difficult “thing”!)
    Would someone so kind to point us to some useful steps or direct us to any helpful advise?
    Thank you!

    1. Share your minidump file - someone may see content and help.
    2. Consider this
    http://support.microsoft.com/kb/2521220
    3. Error description
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557408(v=vs.85).aspx
    Regards
    Milos

  • Probably caused by : atikmdag.sys ( atikmdag+127f8 )

    I just purchased a new HP ProLiant MicroServer G7 N54L
    Here is a short history:
    I replaced the 4GB ECC memory to 8GN non-ECC 
    I originally used a 25ft VGA cable on the on-board VGA port, but had a blue tinge, couldn't recognize the monitor properly, and a bluescreen shutdown, so I removed it.
    There is nothing connected to the VGA port now
    I now connect using RDP only
    The computer freezes randomly and seems to happen when I launch the chrome browser (through RDP)
    The dump files are at: https://onedrive.live.com/redir?resid=A19E045098FB769C!1399&authkey=!APLz-efriDf5wAs&ithint=file%2czip
    According to my limited knowledge, it seems that the dump files indicate a video problem, but I am not completely sure. Can this be a problem with the motherboard?
    Any help is greatly appreciated.

    GG
    These were related to your 5 year old video driver and may simply need a driver update.  It is called a BCC116 and is either the driver or perhaps heat.  I would start by removing the current driver and installing the newest driver available.
    "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
    If so, it might be as simple as dust buildup and subsequently inadequate cooling.
    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
    For more information please read this blog  http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
    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-25833-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 (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0280a000 PsLoadedModuleList = 0xfffff800`02a4d890
    Debug session time: Tue Aug 26 23:27:25.092 2014 (UTC - 4:00)
    System Uptime: 8 days 2:58:31.684
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 116, {fffffa80093cd4e0, fffff88004cc57f8, 0, 2}
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+127f8 )
    Followup: MachineOwner
    0: kd> !analyze -v
    * Bugcheck Analysis *
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80093cd4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004cc57f8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    Debugging Details:
    FAULTING_IP:
    atikmdag+127f8
    fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
    CUSTOMER_CRASH_COUNT: 1
    BUGCHECK_STR: 0x116
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    STACK_TEXT:
    fffff880`05a5f9c8 fffff880`05327134 : 00000000`00000116 fffffa80`093cd4e0 fffff880`04cc57f8 00000000`00000000 : nt!KeBugCheckEx
    fffff880`05a5f9d0 fffff880`05326e3e : fffff880`04cc57f8 fffffa80`093cd4e0 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`05a5fa10 fffff880`04c0ff13 : fffffa80`093cd4e0 00000000`00000000 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`05a5fa40 fffff880`04c39cf1 : 00000000`ffffffff 00000000`02ae8b02 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`05a5fb20 fffff880`04c38437 : 00000000`00000102 00000000`00000000 00000000`02ae8b02 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`05a5fb50 fffff880`04c0b2d2 : ffffffff`ff676980 fffffa80`085ce010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`05a5fbf0 fffff880`04c37ff6 : 00000000`00000000 fffffa80`08641830 00000000`00000080 fffffa80`085ce010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`05a5fd00 fffff800`02b1b73a : 00000000`fffffc32 fffffa80`085cf610 fffffa80`06702040 fffffa80`085cf610 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`05a5fd40 fffff800`028708e6 : fffff800`029fae80 fffffa80`085cf610 fffff800`02a08cc0 fffff880`031b5801 : nt!PspSystemThreadStartup+0x5a
    fffff880`05a5fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    STACK_COMMAND: .bugcheck ; kb
    FOLLOWUP_IP:
    atikmdag+127f8
    fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
    SYMBOL_NAME: atikmdag+127f8
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: atikmdag
    IMAGE_NAME: atikmdag.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a8a1a8b
    FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
    BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmdag.sys
    FAILURE_ID_HASH: {7527b2fa-489f-c504-9452-1a10bd154401}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Killer e2200 Gigabit Ethernet Controller (NDIS 6.30) problem

    Hi everyone, i had this problem since november:i had a gaming pc(specifics below) with a Killer e2200 Gigabit Ethernet Controller (NDIS 6.30).The problem is that my pc disconnects every 30 min more or less,for a minute.I tried formatting my pc and installing windows 8.1 (before, i had win 7 home premium) but still nothing.I don't know where the problem could be, because other devices (smartphone,tablets adn also other pc) don't disconnect.
    If you could help me, i'll give you other informations as much as i can.
    Thanks
    i'm using a TP-LINK EXTENDER 300 Mbps which is connected with ethernet cable to my PC.It's an universal WI FI range extender.
    EDIT: I posted this topic into "other MSI product"

    Other topic is removed
    >>Please read and comply with the Forum Rules.<<
    WiFi does not use Killer network, and even though your device is connected through ethernet, it is still wireless. Might be that Killer NIC and your device (and its driver) cross over each other and cause random issues. Try standard Ethernet->Modem connection (straight 1m connection) and see if you get internet drops then too.

  • Blackberry Desktop Software has stopped working. A problem has caused the program to stop...

    I have a Tour 9630 and just installed v6.0 and receiving an error window "Blackberry Desktop Software has stopped working. A problem as caused the program to stop working correctly.  Windows will close the program and notify you if a solution is available."  I have not received any message from Windows after 2 days.  Has anyone experienced this problem?  If so, I would appreciate any guidance.  I have Windows 7, if that matters. Thank you. in advance.

    Hi somewhatstock
    How far did you get with them? Did they have any ideas what might be causing the problem? Trying to work on it myself, so trying to eliminate what others might have tried. Curious why it works on my Desktop however. Losing tethering really causes problems as I rely on tethering with my laptop quite a lot.  
    Any information most welcome,
    regards,
    John

  • 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.

  • How can I tell if my internet problem is caused by firefox, my computer, or my internet connection?

    At certain times of the day (usually only late at night), my internet becomes unusable. The websites take so long to load that they just time out (or I give up). It happens periodically in the early evening as well (I just tried to watch a two-minute video and it took me half an hour). I can't tell if the problem is caused by firefox, my computer, or my internet. What can I do to determine where the problem is?
    Thanks!

    You have several issues.
    *1
    Your System Details shows;
    Installed Plug-ins
    Adobe Shockwave for Director Netscape plug-in, version 12.1.1.151
    Adobe Shockwave for Director Netscape plug-in, version 12.0
    Having more than one version of a program may cause issues.
    Flash is notorious for not cleaning out the older version as part of an update.
    Grab the uninstaller from here:
    '''[http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-windows.html Uninstall Flash Player | Windows]'''
    '''[http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-mac-os.html Uninstall Flash Player | Mac]'''
    Then reinstall the latest version.
    Flash Player '''v15.0.0.223 http://get.adobe.com/flashplayer/'''
    Shockwave Director '''v12.1.4.154 http://get.adobe.com/shockwave/'''

  • 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

Maybe you are looking for