Windows BlueScreen Locale ID: 1033

Hi Guys, This is my first attempt at using this forum so excuse me if I haven't provided all the necessary information.
I have found recently that my computer has started to BSOD when playing games I'm wondering If my graphics card is on the way out.
The following is the Problem Signature.
Source
Windows
Summary
Shut down unexpectedly
Date
‎11/‎9/‎2013 7:40 AM
Status
Not reported
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Files that help describe the problem
110913-47720-01.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode: a
BCP1: 0000000000000001
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80004898DE4
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Regards
Dave

We do need the actual DMP file as it contains 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
Wanikiya and Dyami--Team Zigzag

Similar Messages

  • BlueScreen of Death. Windows 7 (64-bit) Locale ID: 1033

    Hello. I keep happening to get errors, when the computer Idles or goes in sleep mode. This isn't the first time, either.
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 116
      BCP1: FFFFFA8003EA34E0
      BCP2: FFFFF8800409EDC0
      BCP3: 0000000000000000
      BCP4: 000000000000000D
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1
    Files that help describe the problem:
      C:\Windows\Minidump\042514-19843-01.dmp
      C:\Users\Zach\AppData\Local\Temp\WER-70481-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
    Minidump: https://onedrive.live.com/?cid=f535c11f3f3b6b66&id=F535C11F3F3B6B66%21134#cid=14F604FB3205F70D&id=14F604FB3205F70D%21105

    ZV
    Two issues.  The driver verified crash was related to readyboost.  I would turn it off at least to test, the others were called BCC116
    "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
    Bugcheck code 00000116
    Bugcheck code 00000116
    Bugcheck code 00000116
    Bugcheck code 0000007F
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
    BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
    BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
    BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
    Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+9b )
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    SYSTEM UP-TIME
    System Uptime: 1 days 11:16:46.716
    System Uptime: 2 days 4:48:03.890
    System Uptime: 2 days 5:21:56.656
    System Uptime: 0 days 0:00:14.976
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Apr 25 04:47:05.280 2014 (UTC - 4:00)
    System Uptime: 1 days 11:16:46.716
    BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    BUGCHECK_STR: 0x116
    PROCESS_NAME: System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Apr 23 16:38:38.470 2014 (UTC - 4:00)
    System Uptime: 2 days 4:48:03.890
    BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    BUGCHECK_STR: 0x116
    PROCESS_NAME: System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Apr 21 04:18:13.236 2014 (UTC - 4:00)
    System Uptime: 2 days 5:21:56.656
    BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    BUGCHECK_STR: 0x116
    PROCESS_NAME: System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Sat Nov 9 07:15:24.664 2013 (UTC - 4:00)
    System Uptime: 0 days 0:00:14.976
    BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
    Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+9b )
    BUGCHECK_STR: 0x7f_8
    PROCESS_NAME: System
    Wanikiya and Dyami--Team Zigzag

  • Blue Screen of Death Windows 7 - (64bit) - Locale ID: 1033

    Hello there. I've been having issues with the blue screen that has been frequently occurring. I don't know a whole lot about computers so I was hoping if you could help me out. The Information regarding the bluescreen is below. 
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88004C9EE62
      BCP3: FFFFF880039854B8
      BCP4: FFFFF88003984D10
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1
    Files that help describe the problem:
      C:\Windows\Minidump\052214-21200-01.dmp
      C:\Users\Spencer\AppData\Local\Temp\WER-111119-0.sysdata.xml

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

  • Windows 7, Blue Screen Local ID: 1033

    Lately i get this Blue Screen error and i have no idea what i should do:
    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.256.1
      Locale ID:    1033
    Additional information about the problem:
      BCCode:    50
      BCP1:    FFFFFAFDF700001A
      BCP2:    0000000000000000
      BCP3:    FFFFF80003178F5C
      BCP4:    0000000000000005
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1
    Files that help describe the problem:
      C:\Windows\Minidump\020214-15740-01.dmp
      C:\Users\Maria\AppData\Local\Temp\WER-47221-0.sysdata.xml

    MH
    These were related to amifldrv64.sys belong to CLICKBIOSII module developed by MSI.  I would install the newest driver available.
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Machine Name:
    Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03056670
    Debug session time: Tue Sep 17 10:40:08.022 2013 (UTC - 5:00)
    System Uptime: 0 days 0:00:28.849
    Loading Kernel Symbols
    BugCheck 50, {fffffaf5b100001a, 0, fffff80002f7af5c, 5}
    *** WARNING: Unable to verify timestamp for amifldrv64.sys
    *** ERROR: Module load completed but symbols could not be loaded for amifldrv64.sys
    Could not read faulting driver name
    Probably caused by : amifldrv64.sys ( amifldrv64+188c )
    2: kd> !analyze -v
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffaf5b100001a, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002f7af5c, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000005, (reserved)
    Debugging Details:
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c0100
    GetUlongFromAddress: unable to read from fffff800030c01c0
    fffffaf5b100001a Nonpaged pool
    FAULTING_IP:
    nt!MmFreeContiguousMemory+ec
    fffff800`02f7af5c f6411a20 test byte ptr [rcx+1Ah],20h
    MM_INTERNAL_CODE: 5
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0x50
    PROCESS_NAME: SCEWIN_64.exe
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME: fffff8800b252610 -- (.trap 0xfffff8800b252610)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000058000000000 rbx=0000000000000000 rcx=fffffaf5b1000000
    rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f7af5c rsp=fffff8800b2527a0 rbp=fffff8800b252b60
    r8=fffffa800a0ae010 r9=00000000000000a0 r10=fffffa800670b210
    r11=fffffa800a0ae010 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po cy
    nt!MmFreeContiguousMemory+0xec:
    fffff800`02f7af5c f6411a20 test byte ptr [rcx+1Ah],20h ds:fffffaf5`b100001a=??
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80002f055a3 to fffff80002e88c00
    STACK_TEXT:
    fffff880`0b2524a8 fffff800`02f055a3 : 00000000`00000050 fffffaf5`b100001a 00000000`00000000 fffff880`0b252610 : nt!KeBugCheckEx
    fffff880`0b2524b0 fffff800`02e86d2e : 00000000`00000000 fffffaf5`b100001a fffffa80`08a81a00 fffff880`0273d000 : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`0b252610 fffff800`02f7af5c : fffffa80`0a0ae010 fffff880`0a4014e7 fffffa80`1fffc000 fffffa80`0a306290 : nt!KiPageFault+0x16e
    fffff880`0b2527a0 fffff880`0a40188c : fffffa80`0a0ae010 fffffa80`08a81980 fffffa80`08a81980 00000000`00000016 : nt!MmFreeContiguousMemory+0xec
    fffff880`0b2527e0 fffffa80`0a0ae010 : fffffa80`08a81980 fffffa80`08a81980 00000000`00000016 fffff800`03018730 : amifldrv64+0x188c
    fffff880`0b2527e8 fffffa80`08a81980 : fffffa80`08a81980 00000000`00000016 fffff800`03018730 fffffa80`08a81980 : 0xfffffa80`0a0ae010
    fffff880`0b2527f0 fffffa80`08a81980 : 00000000`00000016 fffff800`03018730 fffffa80`08a81980 fffffa80`0a269b10 : 0xfffffa80`08a81980
    fffff880`0b2527f8 00000000`00000016 : fffff800`03018730 fffffa80`08a81980 fffffa80`0a269b10 fffff880`0a4019b4 : 0xfffffa80`08a81980
    fffff880`0b252800 fffff800`03018730 : fffffa80`08a81980 fffffa80`0a269b10 fffff880`0a4019b4 00000000`00000001 : 0x16
    fffff880`0b252808 fffffa80`08a81980 : fffffa80`0a269b10 fffff880`0a4019b4 00000000`00000001 00000000`00000001 : nt!NonPagedPoolDescriptor+0x1b0
    fffff880`0b252810 fffffa80`0a269b10 : fffff880`0a4019b4 00000000`00000001 00000000`00000001 00000000`000000a8 : 0xfffffa80`08a81980
    fffff880`0b252818 fffff880`0a4019b4 : 00000000`00000001 00000000`00000001 00000000`000000a8 fffff800`02f93744 : 0xfffffa80`0a269b10
    fffff880`0b252820 00000000`00000001 : 00000000`00000001 00000000`000000a8 fffff800`02f93744 00000000`00000000 : amifldrv64+0x19b4
    fffff880`0b252828 00000000`00000001 : 00000000`000000a8 fffff800`02f93744 00000000`00000000 fffffa80`0a306290 : 0x1
    fffff880`0b252830 00000000`000000a8 : fffff800`02f93744 00000000`00000000 fffffa80`0a306290 fffffa80`0a269b10 : 0x1
    fffff880`0b252838 fffff800`02f93744 : 00000000`00000000 fffffa80`0a306290 fffffa80`0a269b10 fffff880`0a401bff : 0xa8
    fffff880`0b252840 fffff880`0b252928 : fffff880`0b252968 fffffa80`0a41b060 00000000`00000001 fffff880`0b252960 : nt!EtwpCCSwapTrace+0x4d4
    fffff880`0b252900 fffff880`0b252968 : fffffa80`0a41b060 00000000`00000001 fffff880`0b252960 00000008`0a43ab01 : 0xfffff880`0b252928
    fffff880`0b252908 fffffa80`0a41b060 : 00000000`00000001 fffff880`0b252960 00000008`0a43ab01 fffffa80`0a306290 : 0xfffff880`0b252968
    fffff880`0b252910 00000000`00000001 : fffff880`0b252960 00000008`0a43ab01 fffffa80`0a306290 00000000`00000008 : 0xfffffa80`0a41b060
    fffff880`0b252918 fffff880`0b252960 : 00000008`0a43ab01 fffffa80`0a306290 00000000`00000008 00000000`00000000 : 0x1
    fffff880`0b252920 00000008`0a43ab01 : fffffa80`0a306290 00000000`00000008 00000000`00000000 fffffa80`0a269b10 : 0xfffff880`0b252960
    fffff880`0b252928 fffffa80`0a306290 : 00000000`00000008 00000000`00000000 fffffa80`0a269b10 00000000`00000000 : 0x00000008`0a43ab01
    fffff880`0b252930 00000000`00000008 : 00000000`00000000 fffffa80`0a269b10 00000000`00000000 fffffa80`06743820 : 0xfffffa80`0a306290
    fffff880`0b252938 00000000`00000000 : fffffa80`0a269b10 00000000`00000000 fffffa80`06743820 fffffa80`0a3062e0 : 0x8
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    amifldrv64+188c
    fffff880`0a40188c ?? ???
    SYMBOL_STACK_INDEX: 4
    SYMBOL_NAME: amifldrv64+188c
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: amifldrv64
    IMAGE_NAME: amifldrv64.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4accc6d8
    FAILURE_BUCKET_ID: X64_0x50_amifldrv64+188c
    BUCKET_ID: X64_0x50_amifldrv64+188c
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0x50_amifldrv64+188c
    FAILURE_ID_HASH: {2881f1e0-4106-fe9b-c0f6-de1062eca6a6}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • BSOD Locale ID:1033

    Hello,
    Recently for no real reason that I can see, I started getting this error.
    Problem signature:
      Problem Event Name:BlueScreen
      OS Version:6.1.7601.2.1.0.256.1
      Locale ID:1033
    Additional information about the problem:
      BCCode:1000007e
      BCP1:FFFFFFFFC0000005
      BCP2:FFFFF8800F59ADBB
      BCP3:FFFFF88002BF4228
      BCP4:FFFFF88002BF3A80
      OS Version:6_1_7601
      Service Pack:1_0
      Product:256_1
    Files that help describe the problem:
      C:\Windows\Minidump\052414-16582-01.dmp
      C:\Users\Nephoros\AppData\Local\Temp\WER-29936-0.sysdata.xml
    From what I noted, its completly random, it happens when I play wow, and if only then, I am uncertain.
    Please assist me so that this will not happen again.

    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

  • Blue Screen Of Death (Please help) Locale ID: 1033

    So this computer is only 1 year old, I got this computer from cyberpower and the computer has been alright until out of no where i have been getting this blue screen
    This is the information it gives me about it, can someone please help me resolve this
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88011184DBB
      BCP3: FFFFF88003E72228
      BCP4: FFFFF88003E71A80
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 256_1
    Files that help describe the problem:
      C:\Windows\Minidump\061014-20342-01.dmp
      C:\Users\Toktz1\AppData\Local\Temp\WER-31746-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

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

  • Windows BlueScreen Error BCCode 124?

    Back in September I bought a custom built PC, and was having absolutely no problems with it until earlier this year. Whenever I tried to download something, stream a video, my computer will restart without warning, and upon completion would say this exactly:
    Windows has recovered from an unexpected shutdown
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 124
      BCP1: 0000000000000000
      BCP2: FFFFFA80081F38F8
      BCP3: 0000000000000000
      BCP4: 0000000000000000
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 256_1
    Files that help describe the problem:
      C:\Windows\Minidump\032014-32775-01.dmp
      C:\Users\Speric10\AppData\Local\Temp\WER-74958-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
    Upon trying to fix this solution myself I tried to run a stress test, and the BlueScreen happens once I start the test. I made sure my fans all worked properly and felt my PC and it is not hot, and a couple areas barely warm. I could be overclocking my PC
    but have not even touched that so I highly doubt it, so does anyone know why? Also, I already installed a fresh version of Windows 7 Ultimate 64 bit.

    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" re-installation 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 persists 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/
    Advice offered in good faith. It is your decision to implement same. Wanikiya and Dyami - Team ZigZag

  • Windows 7 BlueScreen locale ID: 2070

    Hello!
    I have just watched a film and then the notebook just was like running nothing, it was just "on" and suddendly it went with a blue screen in the middle with text. Could someone help me, please.
    I've seen some other similar problems, but i wanted to be specific on my case.
    I can send the minidump file.

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

  • After upgrading ACS 3.3.1 to 4.2 on windows the local database is not working

    Hi,
    I have upgaded the ACS 3.3.1 for windows server to 4.2. Everything went fine but the local database is not working.
    The CD is an upgrade kit from 3.x to 4.2 on windows. I tried to install directly the 4.2 I was able to install but integration with AD/LDAp is not working. Anysay its an upgrade kit so I cant expect it shoud work when install drectly the 4.2 but by upgrading from 3.3 to 4.2 everything should work fine.
    I followed the upgradation path as recomended.
    Also we have a requirment that once it is upgraded to 4.2 we need to shift the whole thing from the physical server to a virtual machine on VMware ESX server 3.5.
    Can anybody pls guide me if anything else to do after the upgradation.
    Thanks & Regards
    Sachi

    Hi Javier,
    First of all I was facing a problem of restoring the old database of 3.3 to 4.2. Somehow I overcame that issue by following the below steps. Now local authentication is working fine but AD/other External database authentication is not working. As you told the setting for the unknown users are configured to fetch the credentials from the external database if it is not in the local database.
    Do we need to do anything in the AD itself?
    Regards
    Sachi
    Steps for ACS upgrade to 4.2 version
    Below are the requested steps mentioned for the up gradation from ACS 3.3.2 to ACS 4.2.
            1)     Take a configuration backup from existing ACS. ACS--->System
    configuration----> ACS Backup
    2)    now if you have  ACS 3.3.2 on server. take backup of the ACS
    3)   Insert the cd or if you have the set up on the system then  Run the setup of ACS 3.3.4. During the process it will prompt you to
    upgrade existing configuration. Make sure you check that option else we will
    loose the database. Now you need to hit next.next to finish the 3.3.4 upgrade.
    4)     Once you are at 3.3.4, take a backup and keep it handy.
    5)     Run the setup of 4.1.1. During this process it will prompt you to
    upgrade existing configuration. Make sure you check that option else we will
    loose the database. Now you need to hit next.next to finish the 4.1 upgrade.
    6)Once you are at 4.1.1.24 take a backup and keep it handy.
    7)     Run the setup of 4.2. During this process it will prompt you to
    upgrade existing configuration. Make sure you check that option else we will
    loose the database. Now you need to hit next.next to finish the 4.2 upgrade.
    8)     Once you are at 4.2 take a backup and keep it handy. Now run the
    patch 12 and take a backup again.
    9)     Now fresh install 4.2 on your new production server and install patch
    12. Restore the 4.2 patch 12 backup and you should be all set.

  • How to make Windows 7 local admin user account transparent

    Previously with Windows XP, I would use the autolog.exe to have the local windows account login transparently while the user would login via their novell credentials. My company would like to roll out Windows 7 now, but unfortuantely, we are unable to make the windows local account log in transparent. I do not want my users to know this password - also it would really confuse them as they are not tech savvy to understand it.
    Is there a way that I can make this happen? If you need more information, please ask and I will provide. Not sure what other info may be required here.
    I am using Novell Client 2 SP2 - i find the SP3 to be problematic, but if SP3 would resolve this, I am open to the idea.

    Kristaranglack,
    > Previously with Windows XP, I would use the autolog.exe to have the
    > local windows account login transparently while the user would login via
    > their novell credentials. My company would like to roll out Windows 7
    > now, but unfortuantely, we are unable to make the windows local account
    > log in transparent. I do not want my users to know this password - also
    > it would really confuse them as they are not tech savvy to understand
    > it.
    The easy solution is autoadminlogon:
    https://wwwstage.provo.novell.com/su...php?id=7013307
    But a far more elegant solution would be to use ZENWorks
    Anders Gustafsson (NKP)
    The Aaland Islands (N60 E20)
    Have an idea for a product enhancement? Please visit:
    http://www.novell.com/rms

  • After iPhone3G, v2.1 & iTunes 8.0 - get windows bluescreen w/ usbaapl.sys

    On Thursday I downloaded and installed iTunes v8.0. all was working fine after that. On Friday, I installed the new 2.1 version for the iPhone as well as the latest for MobileMe. All appeared to be working fine.
    About 4 hours later, I docked my iPhone again and got a bluescreen crash. Here's some of the info.
    Stop: 0x0000007e
    usbaapl.sys - address 8CD4E515 base @ 8CD4C000 Datestamp 48AF5A44
    I have since uninstalled, and re-installed all of the above components with no improvement. The only other thing was an additional Windows Malicious Software update, that I installed, but I even rolled back to a restore point before the update, and I still can't resolve the problem.
    Any help would be appreciated.

    A bit more info here.
    I removed iTunes 8.0 & Apple Mobile Services (usbaapl.sys). I rebooted my machine - then installed iTunes 7.7.1. When I tried to open iTunes, it said that my library was unavailable as it had been created for a newer version. OK - that makes sense, but......when I docked my iPhone - the good ole USB - duh-dunk sound happened and no crash.
    I installed 8.0 on top of it, rebooted - and once I redocked the iPhone - CRASH. This time - no bluescreen - just a black screen and a reboot.

  • ODBC gateway in windows connecting local oracle to local mysql

    I have setup a test system in my local Vista pc with oracle 11g and mysql. Just installed ODBC gateway and follow the instruction. The listener sid for ODBC started OK. But when I tried tnsping <sid>, it failed with tns-03505 failed to resolve name.
    Any suggestions?
    Thanks,
    Lawrence

    [email protected] wrote:
    Here is the listener.ora for the gateway:# listener.ora Network Configuration File: C:\oracle\Gateway\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    LISTENERMYSQLSERVERDSN =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 2522))
    SID_LIST_LISTENERMYSQLSERVERDSN=
    (SID_LIST=
    (SID_DESC=
    (SID_NAME=MYSQLSERVERDSN)
    (ORACLE_HOME=C:\oracle\Gateway)
    (PROGRAM=dg4odbc)
    ADR_BASE_LISTENER = C:\oracle\Gateway
    TRACE_LEVEL_LISTENER=16
    TRACE_FILE_LISTENER=listener.trc
    TRACE_DIRECTORY_LISTENER=$ORACLE_HOME/network/trace
    #CONNECT_TIMEOUT_LISTENER = 0
    Here is the tnsnames for the database:
    # tnsnames.ora Network Configuration File: C:\oracle\db\product\11.2.0\dbhome_2\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    LISTENER_ORCL =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    ORCL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = orcl.myhost.COM)
    MYSQLSERVERDSN =
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=2522))
    (CONNECT_DATA=(SID=MYSQLSERVERDSN))
    (HS=OK)
    Here is the output from listener:
    C:\>lsnrctl start listenermysqlserverdsn
    LSNRCTL for 32-bit Windows: Version 11.2.0.1.0 - Production on 23-JUL-2010 15:11
    :37
    Copyright (c) 1991, 2010, Oracle. All rights reserved.
    Starting tnslsnr: please wait...
    TNSLSNR for 32-bit Windows: Version 11.2.0.1.0 - Production
    System parameter file is C:\oracle\Gateway\network\admin\listener.ora
    Log messages written to c:\oracle\gateway\log\diag\tnslsnr\myhost\listener
    mysqlserverdsn\alert\log.xml
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.64)(PORT=2522)
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.64)(PORT=2522)
    STATUS of the LISTENER
    Alias listenermysqlserverdsn
    Version TNSLSNR for 32-bit Windows: Version 11.2.0.1.0 - Produ
    ction
    Start Date 23-JUL-2010 15:11:40
    Uptime 0 days 0 hr. 0 min. 3 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File C:\oracle\Gateway\network\admin\listener.ora
    Listener Log File c:\oracle\gateway\log\diag\tnslsnr\myhost\listen
    ermysqlserverdsn\alert\log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.64)(PORT=2522)))
    Services Summary...
    Service "MYSQLSERVERDSN" has 1 instance(s).
    Instance "MYSQLSERVERDSN", status UNKNOWN, has 1 handler(s) for this service..
    The command completed successfully
    C:\>once again:
    03505, 00000, "Failed to resolve name"
    // *Cause:  The service name you provided could not be found in TNSNAMES.ORA,
    //          an Oracle Names server, or a native naming service.If the entry could not be found in tnsnames, the process never got far enough for the listener to come into play. Looking at the listener, the listener status, listener configuration, or listener logs is a waste of time for this error.
    You couldn't find the number you were looking for in the telephone directory. You don't solve that by looking to the telephone exchange switchboard.

  • Windows xp local printers offline

    Hi,
    We are currently in a queue-based-printing environment and are rolling out
    Windows XPSP2 to our users. The problem we are having is that when we add
    a local printer and configure that printer's port to use the Novell Print
    queue, the local printer goes offline after a system reboot. If you try
    to bring the printer back online, the message "Operation could not be
    completed" is displayed". Are there any fixes for this? I found a link
    that suggested updataing nwfs.sys or even trying an earlier version. I've
    tried both ways and no luck!
    Help! Any advice appreciated :)

    Is there a reason why you need to setup your printer as a local
    printer? Generally, NetWare printers work better if you install them
    directly as NetWare printers.
    If you really need a local printer for DOS programs, you can use the
    following tool to capture the port:
    http://www.novell.com/coolsolutions/tools/1910.html
    Marcel Cox (using XanaNews 1.17.1.0)

  • Copying itunes library from Mac to Windows over Local Network

    I am a recent switcher. When I first got my MacBook I connected my Windows formatted iPod to the MacBook to transfer my purchased iTunes music, and everything worked fine.
    Now I want to transfer the iTunes music folder from my Mac to a PC (both Vista and XP) over my local network. However, when I try to do this I get the following error message:
    Error 0x800700FE: The specified extended attribute name was invalid.
    I get the same error message if I try to transfer the individual music folders (eg Oasis).
    I have no trouble transferring the folders for song/albums that I have subsequently downloaded to the Mac from iTunes. I only have the problem with the music I originally transferred from the iPod.
    I have been trying to research extended attributes to see if I can edit this, but it all goes over my head. Any advice would be greatly appreciated.

    Hello,
    i'm also a new Mac user (Vista did the trick , and i found this article on the Apple support website.
    Below information can also be used to do the inverse... Mac to PC.
    http://docs.info.apple.com/article.html?artnum=302392
    It explains how to do a backup to CD/DVD. When you have a large library, multiple DVD's will be used.
    It tried it out with a portion of my lib, burned a backup with my PC, and imported it on my MacBook. Works great! All but last played information is copied over...
    Even Podcast, Movies etc are taken into account, also music not residing within the iTunes folder. After the restore on Mac, everything is properly placed within the iTunes folder you assigned.
    Enjoy,
    Roger
    PS: in fact this article is "on the top" of the following list: http://www.apple.com/support/itunes/ :-))

  • Mac - Windows Wireless Local Network

    Hello, everyone.
    I just got my new MacBook Pro.
    I have a desktop PC that I need to share/sync files with.
    How can I do that over wifi?
    I have no clue how to setup this local network, so please help?
    I can see the MacBook in my Windows, but not the other way around.
    Thank you!

    it is a windows 8

Maybe you are looking for