NX 8600GT - Constant BSODs

I just bought a NX8600GT, a K8V-XE motherboard and a 650W PSU did a fresh install of XP, so far so good.
But as soon as I install the Nvida drivers the computer will crash with a bluescreen if I as much as dare to open the browser, change refresh rate or try to open the Nvidia control panel.
This a known issue and does anyone have suggestion for a fix?

Quote from: flobelix on 12-January-08, 22:34:01
This is surely no known issue for a nx8600gt, don't know if it is with this asus board but if that's true we can't help you.
If no known issue we might help you if you privide proper sys info. What driver version have you tried for the 8600? Latest VIA chipset drivers installed before installing vga drivers? What kind of psu do you have? (650w means nothing, we need amps on +12v and the model/manufacturer)
The PSU is a Corsair TX650W the amp on the 12V is 52A, I installed the Via hyperion 5.15 drivers before installing 169.21 Nvidia drivers. Earlier I tried the drivers the MSI live update suggested with no luck.
Err one little thing though. The quick installation guide mentions a SPDIF internal cable I couldn't find one in the box, is that needed?
Quite green when it comes to this hightech PCI-express stuff :P

Similar Messages

  • Constant BSODs MSi hd 6970

    First of all sending shouts to all on this forum.
    Been searching through various forums and seeking the solution.
    A month ago I´ve upgraded my old 4890 to MSi HD 6970 and since then my problems have started.
    I´ve  found that several other MSi HD 6970 and 6*** users have this problem, albeit no solution has worked for me yet.
    Gonna keep it short.
    What´s the problem:
    - constant BSODs / vertical stripes and crashes while playing 3d games (Bad Company 2, AC: Brotherhood) - sometimes after 10 mins of gameplay, sometimes after an hour
    - no BSODs in Win 7 itself
    - no BSODs during movies / videos
    - no BSODs while dual monitor setup and both in use as extended (dvi Asus 24´´ and hdmi 42´´ LCD TV Samsung)
    What I´ve tried:
    - various drivers (original drivers supplied with the card, 11.4 to 11.8 CCC) - no change, still crashing
    - sweeped the old drivers in safe mode - no change
    - uninstalled the Afterburner app; from what I´ve learned it´s in conflict w/ punkbuster which is sort of mandatory for Bad Company 2
    - not using ANY kind of GPU utility (except CCC)
    - temps max 90 celsius in heavy load
    - fan running on 35% in heavy load
    My specs:
    CPU: INTEL Core 2 Duo E8500 - 3,16GHz
    RAM: 6GB  DDR3 1333MHz PC10666 CL6-6-6-18 OCZ Reaper HPC Edition
    Motherboard:INTEL DP45SG Skyberg
    Sound: firewire Edirol FA-66; on-board audio disabled
    VGA:MSI Radeon 6970 2PM2D2GD5
    HDD: WESTERN DIGITAL Caviar Black 500GB, SATA II, WESTERN DIGITAL Caviar Green 1000GB, SATA II
    PSU:TAGAN TG600-U88 600W ATX 2.2
    case: Antec P182
    OS:Windows 7 home premium x64
    Is it PSU, MB or any other component in conflict with the GPU?
    So lads, is it time for RMA?
    All your help and suggestions will be much appreciated

    Registered only to say: had same issues and solved it myself. I sent back the card to the vendor but they refused to do anything because according to their test softwares, the card was fine, the issue did not come up. Yet when I started playing 3D games, my card and PC froze after a few minutes.
    I spent hours searching for the solution and tested all that was suggested without resolution. In the end I took it apart, cleaned the original thermal paste from and around the GPU (it was clearly a mess, spilled around the  GPU and not evenly applied, plus it felt somehow very dry), then I applied a better quality paste that I previously purchased for my new CPU.  I put the card back into my PC and issue gone. I used to get above 95C  (especially the second GPU) just before the PC crashed, now the maximum is around 69-70 Celsius and no crash for a month (playing Guild wars2, assassins creed etc)
    It is very easy to do all this, even if you are a noob like myself. I 'm not a technical person, so I looked it up all on youtube: how to take the heatsink apart, how to clean the orignal paste and how to apply new paste.
    There is another issue I was also facing, with the famous atikmdag crash during games (freeze for a few seconds, then it comes back with the mesage that it has been recovered successfully) - the only workaround I found was to lower the GPU clock from 940 to 900MHz. Error disappeared completely and games are still runnig great on max graphics. It is fine for now, but I'm sure I wont buy another ATI graphic card

  • GTX 560 ti constant BSOD`s .. Troubling me ...

    Hi guys ...
    First things first, here are my system specs :
    core i5 760 @2.8GHz
    Asus P7P55D-E
    Corsair 2X2GB RAM
    MSI NGTX560ti Twin Frozr II OC Edition
    CM Hyper 212+
    Corsair GS600
    Windows 7 64bit
    I was using my XFX HD4350 for over a year now .. was running perfect .. When I upgraded my GPU about a week ago to MSI NGTX560ti Twin Frozr II OC Edition .. I am getting constant BSoD`s while playing games ... IT`s getting on my nerves ...
    I tried clearing CMOS , checked all power cables, Updated to latest Drivers from nVidia (ie: 285.62), Even did a fresh install of windows .. but to no avail ...
    The error on the blue screen I get is BAD POOL CALLER .. I don`t know what it means ... I`ve searched countless forums and did all the above which were recommended ...
    I request forum members and senior members to help me out of this problem ...
    Thank you,
    vizkid2005

    you can try this:
    1) first, update the BIOS of your motherboard, if you have been do it this, proced with the next tip
    2) upgrade bios of the VGA
    3) watch the TEMPS, and if your PSU is enough for the card
    4) change slot of the motherboard and test
    when i buyed this card, after install the card, i updated my BIOS of the motherboard, and later the BIOS of the card.

  • GT70 - Constant BSoDs

    Hello
    I am constantly getting BSoD with my GT70. I am running Windows 8, I cleaned out the Killer Network drivers and reinstalled, I updated my nVidia drivers, and it is still unstable
    I ran memory validater and there doesn't seem to be any issues with the RAM
    I get BSoDs for a variety of reasons. I paid quite a handsome chunk of cash for this thingy and I'm more than a little miffed with the constant BSoD. The latest issue was a KMODE Exception but with USBPORT.sys??
    I can post the logs if needed, there's a veritable horde of them.
    Thanks

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    Machine Name:
    Kernel base = 0xfffff801`c8c7b000 PsLoadedModuleList = 0xfffff801`c8f44a80
    Debug session time: Sat Apr 12 11:28:50.542 2014 (UTC - 4:00)
    System Uptime: 0 days 12:44:11.552
    *                        Bugcheck Analysis                                    *
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000f88, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
       bit 0 : value 0 = read operation, 1 = write operation
       bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801c8ceb220, address which referenced memory
    Debugging Details:
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff801c8fd0168
    GetUlongFromAddress: unable to read from fffff801c8fd01f8
     0000000000000f88 Nonpaged pool
    CURRENT_IRQL:  2
    FAULTING_IP:
    nt!KiInsertTimerTable+90
    fffff801`c8ceb220 488906          mov     qword ptr [rsi],rax
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  AV
    PROCESS_NAME:  audiodg.exe
    TRAP_FRAME:  fffff8801add3790 -- (.trap 0xfffff8801add3790)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa80277cc320 rbx=0000000000000000 rcx=fffff801c8f5f520
    rdx=fffffa8028e5a1a0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff801c8ceb220 rsp=fffff8801add3920 rbp=0000006ac1ac41bc
     r8=0000006ac1ac09c6  r9=000000000000006b r10=fffff801c8c7b000
    r11=fffff8801add3978 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!KiInsertTimerTable+0x90:
    fffff801`c8ceb220 488906          mov     qword ptr [rsi],rax ds:00000000`00000000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff801c8cf4369 to fffff801c8cf5040
    STACK_TEXT: 
    fffff880`1add3648 fffff801`c8cf4369 : 00000000`0000000a 00000000`00000f88 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`1add3650 fffff801`c8cf2be0 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`1add3790 : nt!KiBugCheckDispatch+0x69
    fffff880`1add3790 fffff801`c8ceb220 : fffff880`1add3ab8 fffff801`c90c08f5 00000000`00140000 00000000`00000002 : nt!KiPageFault+0x260
    fffff880`1add3920 fffff801`c8ce1403 : fffff880`02ee8180 ffffffff`fffb6c20 00000000`00000000 ffffffff`fffb6c20 : nt!KiInsertTimerTable+0x90
    fffff880`1add3980 fffff801`c8ce197e : fffffa80`2534c740 00000000`00000001 fffff880`1add3ab8 00000000`00000000 : nt!ExpSetTimer+0x203
    fffff880`1add3a60 fffff801`c8cf4053 : fffffa80`27bfc080 00000000`0000001e 00000000`00000000 fffffa80`269c4d60 : nt!NtSetTimerEx+0x10d
    fffff880`1add3b00 000007fe`878c447b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    0000004b`f4f4f8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`878c447b
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt!KiInsertTimerTable+90
    fffff801`c8ceb220 488906          mov     qword ptr [rsi],rax
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!KiInsertTimerTable+90
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  50ecec77
    FAILURE_BUCKET_ID:  X64_AV_nt!KiInsertTimerTable+90
    BUCKET_ID:  X64_AV_nt!KiInsertTimerTable+90
    Followup: MachineOwner
    This was after resetting to factory defaults using Windows 8 advanced startup

  • Constant BSOD (Blue Screen of Death) on Windows 7 w/ Bootcamp 4

    Please see below for what comes up constantly while doing work on the Windows 7 side of my iMac while running Bootcamp 4.
    So here is my setup:
    Brand New 27" iMac (just got it new in August 2011)
    Intel core i5 2.7 Ghz
    8GB RAM
    AMD Radeon HD 6770M
    I am running Lion latest version on Mac OS X side.
    I installed Windows 7 Home Premium SP1 with Bootcamp 4.
    I loaded the drivers like I am so supposed to with my Mac Disk.
    When in Windows 7 Home Premium SP1, everything works fine for the most part, except sometimes it just freezes up and the BSOD pops up (see below for exact message)
    It's completely random. Sometimes I can play a hardcore 3D war game or an MMO for 6 hours with no problem, sometimes I am just watching a video on youtube for a minute and it just stops.
    I called Apple, they don't really care. They said to start from scratch and do a full clear and reinstall, so I did. I cleared my Bootcamp partition, then I made a new one and completeley reinstalled Windows 7 Home Premium.  I have done this 4 times. I have also tried to make new disks for the updated drivers for my installation on Windows side. The problem persists.
    Everything is completely updated and all the newest patches and versions are installed on both the Windows and Mac side. I am at a complete loss as to what to do with this.
    I cannot update my video card from within Windows - Apple must provide the updated drivers themselves. In fact, I can update NO drivers of the iMac hardware from the Windows side.
    PLEASE HELP ME!!!

    If you haven't already I recommend reposting in the Boot Camp forum. That's where the Boot Camp guys tend to hang out.

  • Constant BSOD errors

    I get BSOD errors fairly often. This may have started to happen after enabling
    Asus Optimal power plan in BIOS, I can't tell that by looking at dump files.
    Shared link to dump files: http://1drv.ms/1DCaKcG
    Please tell me what's wrong and help me to fix this problem.

    These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them in this
    wiki
    Since yours references "genuine Intel" I would start with a cpu stress test
    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\zigza\Desktop\041415-21312-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
    Machine Name:
    Kernel base = 0xfffff802`22c1a000 PsLoadedModuleList = 0xfffff802`22ef3250
    Debug session time: Tue Apr 14 14:27:53.505 2015 (UTC - 4:00)
    System Uptime: 0 days 3:51:33.144
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, ffffe001cc1f1028, bf800000, 124}
    Probably caused by : GenuineIntel
    Followup: MachineOwner
    2: kd> !analyze -v
    * Bugcheck Analysis *
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe001cc1f1028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR: 0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: SpecOpsTheLine
    CURRENT_IRQL: f
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    STACK_TEXT:
    ffffd000`5256edf8 fffff802`233e5213 : 00000000`00000124 00000000`00000000 ffffe001`cc1f1028 00000000`bf800000 : nt!KeBugCheckEx
    ffffd000`5256ee00 fffff802`22de05a9 : 00000000`00000001 ffffe001`c16af310 ffffe001`c16af310 ffffe001`cc1f1028 : hal!HalBugCheckSystem+0xcf
    ffffd000`5256ee40 fffff802`233e56a0 : 00000000`00000728 00000000`00000002 ffffd000`5256f230 00000000`00000000 : nt!WheaReportHwError+0x22d
    ffffd000`5256eea0 fffff802`233e5a0d : ffffe001`00000010 ffffe001`c16af310 ffffd000`5256f048 ffffe001`c16af310 : hal!HalpMcaReportError+0x50
    ffffd000`5256eff0 fffff802`233e58f8 : ffffe001`c16aeca0 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
    ffffd000`5256f040 fffff802`233e5b42 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
    ffffd000`5256f080 fffff802`233e5ccf : ffffe001`c16aeca0 ffffd000`5256f2b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    ffffd000`5256f0b0 fffff802`22d754bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    ffffd000`5256f0e0 fffff802`22d75271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd000`5256f220 fffff800`eb9d133f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    ffffd000`24731870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x3bf
    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME: GenuineIntel
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    IMAGE_VERSION:
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
    BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache
    FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Re: Windows 8 constant BSOD

    Hello friends. I am having a major problem with my bootcamp partition. I just installed windows 8 as an upgrade from windows 7 after a successful installation. However, when i booted up the partition it gives me the BSOD error almost every time i boot up. It lets you use for 2 minutes and then immediately BSOD. I cannot install bootcamp drivers because it keeps crashing. Can someone help me? I am using a mid 2010 macbook pro 13 inch. I do know that it is not officially supported but my friend managed to install on his 13 inch mid 2010 mbp as well. Thank you!

    Hi
    One very important point is that your Satellite L555 is not officially Win 8 supported.
    What does this means?
    This means that there are no Toshiba Win 8 drivers for this series.
    But this does not mean that you cannot use the Win 8.
    You can install the Win 8 and can use it if you purchased the Microsoft licence
    Regarding the drivers:
    Well you will need to search drivers at your own hand and in some cases Win 7 drivers can be installed on Win 8 system

  • Help with constant BSOD

    I keep getting BSOD.  At first I had windows vista installed, I tried updating everything, bios, memory drivers, graphics drivers, again still BSOD.  I downgrading to windows XP(because of this and other reasons).  I still get BSOD.
    The messages associated with it are:
    1)no message given
    2)memory_management
    3)irql_not_less_or_equal
    I have the Lenovo T61p.
    Any assistance would be greatly appreciated.

    Hello David,
    The Sequence setting needs to match the video and audio of the incoming files. When this occurs correctly rendering is minimized.
    Sequence settings are selected by choosing the correct _Easy Setup_ before the material is edited to the Timeline.
    Note: The Material has to match the Sequence settings not the other way round. FCE works with fixed formats.
    If you provide details of the footage you are working with and how they arrived into FCE, we may be able to help.
    Al

  • Constant BSOD, Can't seem to fix

    My board crashed so I replaced it and my memory with an MSI 970A-G46.  My RAM is running in dual channel with 8GB on each side.  I reinstalled Win 64 bit and it started crashing almost immediately.  It would run for a few hours but then crash. 
    It only crashes while browsing the internet.  I use Firefox and thought maybe it was my browser. I tried Chrome though with the same effect.   My Video Card is a GEForce 460.  Finally I decided to try a new hard drive and reinstall Windows
    again.  This time it worked a few days and started to crash again. Same issue, only when browsing.  I have tried updating every driver I have to no effect.  Windows update tried to install a new service pack yesterday but that took forever and
    got rolled back because of an error.  Basically the only hardware I have left is the Power Supply, processor and video card.  I keep my processor fan and heatsink clean, I have tried a different video card with the same issue so I really don't think
    it is my hardware. 
    My last crash brought this up in Event Vewer:Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          2/20/2014 10:24:53 AM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOME-PC
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000102, 0x0000000000000002, 0x0000000000000001, 0xfffffa800e2722e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022014-26988-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-20T16:24:53.000000000Z" />
        <EventRecordID>17716</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>HOME-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x000000d1 (0x0000000000000102, 0x0000000000000002, 0x0000000000000001, 0xfffffa800e2722e0)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">022014-26988-01</Data>
      </EventData>
    </Event>
    As well as this message from the previous BSOD
    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          2/20/2014 10:49:45 AM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOME-PC
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022014-27565-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-20T16:49:45.000000000Z" />
        <EventRecordID>17829</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>HOME-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x0000001e (0xffffffffc0000005, 0x0000000000000000, 0x0000000000000008, 0x0000000000000000)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">022014-27565-01</Data>
      </EventData>
    </Event>

    Hi,
    I have checked with the dmp files uploaded.
    Most of them showed that there are some hardware issues with BugCHeck ID 1E and 3B. (25412,14414,24242,21964,22885,28095, 18688, 20576, 18064.)
    Only two of them(19125,19671) indicate that your AMD processor failure error with BugCheck ID 124.
    See: Dump file:
    Dump file 19125:
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa800dae6028, b66b4000, 135}
    Probably caused by : AuthenticAMD
    Followup: MachineOwner
    2: kd> !analyze -v
    * Bugcheck Analysis *
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800dae6028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR: 0x124_AuthenticAMD
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: FlashPlayerPlu
    CURRENT_IRQL: f
    STACK_TEXT:
    fffff880`02f6ca88 fffff800`0301e903 : 00000000`00000124 00000000`00000000 fffffa80`0dae6028 00000000`b66b4000 : nt!KeBugCheckEx [d:\win7_gdr\minkernel\ntos\ke\amd64\procstat.asm @ 177]
    fffff880`02f6ca90 fffff800`031da543 : 00000000`00000001 fffffa80`0de98ea0 00000000`00000000 fffffa80`0de98ef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`02f6cad0 fffff800`0301e5c8 : 00000000`00000728 fffffa80`0de98ea0 fffff880`02f6ce30 00000000`098f8b00 : nt!WheaReportHwError+0x263 [d:\win7_gdr\minkernel\ntos\whea\whea.c @ 773]
    fffff880`02f6cb30 fffff800`0301df1a : fffffa80`0de98ea0 fffff880`02f6ce30 fffffa80`0de98ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02f6cc80 fffff800`03011e8f : 00000000`00000097 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02f6ccc0 fffff800`030c312c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`02f6ccf0 fffff800`030c2f93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1322]
    fffff880`02f6ce30 00000000`6c40e2e1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1282]
    00000000`042df810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6c40e2e1
    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME: AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    Followup: MachineOwner
    Dump file 19671:
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa800de0e028, b669c000, 135}
    Probably caused by : AuthenticAMD
    Followup: MachineOwner
    2: kd> !analyze -v
    * Bugcheck Analysis *
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800de0e028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b669c000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR: 0x124_AuthenticAMD
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    CURRENT_IRQL: f
    STACK_TEXT:
    fffff880`02d6ca88 fffff800`03601903 : 00000000`00000124 00000000`00000000 fffffa80`0de0e028 00000000`b669c000 : nt!KeBugCheckEx [d:\win7_gdr\minkernel\ntos\ke\amd64\procstat.asm @ 177]
    fffff880`02d6ca90 fffff800`0319a543 : 00000000`00000001 fffffa80`0c710010 00000000`00000000 fffffa80`0c710060 : hal!HalBugCheckSystem+0x1e3
    fffff880`02d6cad0 fffff800`036015c8 : 00000000`00000728 fffffa80`0c710010 fffff880`02d6ce30 00000000`00000000 : nt!WheaReportHwError+0x263 [d:\win7_gdr\minkernel\ntos\whea\whea.c @ 773]
    fffff880`02d6cb30 fffff800`03600f1a : fffffa80`0c710010 fffff880`02d6ce30 fffffa80`0c710010 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02d6cc80 fffff800`035f4e8f : fffff900`c2ad6490 00000000`00000001 fffff880`02d6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02d6ccc0 fffff800`0308312c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`02d6ccf0 fffff800`03082f93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1322]
    fffff880`02d6ce30 fffff960`001ab04a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 [d:\win7_gdr\minkernel\ntos\ke\amd64\trap.asm @ 1282]
    fffff880`089f9910 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff960`001ab04a
    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME: AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN
    BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN
    Followup: MachineOwner
    The other dump files showed the reason for BSOD is probably caused by some system files like dxgkrnl.sys, ntfs.sys and win32K.sys, which I think is related with(or caused by) the hardware failure.
    For BugCheck information, please see:
    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
    Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED
    Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR
    Hope this might help
    Best regards
    Michael Shao
    TechNet Community Support

  • LR4 RC2:  Constant BSOD, Event ID: 1000.  Resolution????

    My PC constantly BSODs when running LR4 RC2.  This will happen within 5 minutes of attempting to Upload to the WEB.
    I have also experienced BSOD while processing photos in LR.
    PC Config:
    Gigabyte GA-P55M-UD2 mobo
    Intel I7 870, 2.93 ghz
    16 gb Crucial Ram
    Samsung SSD 830, 256 gb System Drives
    WD + Seagate Data drives
    XFX HD 4870 Video
    Here is the most recent Error log from Event Viewer:
    Log Name: 
    Application
    Source:   
    Application Error
    Date:     
    5/24/2012 11:26:35 PM
    Event ID: 
    1000
    Task Category: (100)
    Level:    
    Error
    Keywords: 
    Classic
    User:     
    N/A
    Computer: 
    PJR-QUAD-112009
    Description:
    Faulting application name: lightroom.exe, version: 4.1.0.11, time stamp: 0x4f9700dd
    Faulting module name: CameraRaw.dll, version: 4.1.0.7, time stamp: 0x4f9700ab
    Exception code: 0xc0000005
    Fault offset: 0x0000000000176005
    Faulting process id: 0x1434
    Faulting application start time: 0x01cd3a251ed7b04b
    Faulting application path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\lightroom.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\CameraRaw.dll
    Report Id: 6d9c47d1-a619-11e1-95cd-00241ddafbbb
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-05-25T03:26:35.000000000Z" />
    <EventRecordID>136058</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PJR-QUAD-112009</Computer>
    <Security />
      </System>
      <EventData>
    <Data>lightroom.exe</Data>
    <Data>4.1.0.11</Data>
    <Data>4f9700dd</Data>
    <Data>CameraRaw.dll</Data>
    <Data>4.1.0.7</Data>
    <Data>4f9700ab</Data>
    <Data>c0000005</Data>
    <Data>0000000000176005</Data>
    <Data>1434</Data>
    <Data>01cd3a251ed7b04b</Data>
    <Data>C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\lightroom.exe</Data>
    <Data>C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\CameraRaw.dll</Data>
    <Data>6d9c47d1-a619-11e1-95cd-00241ddafbbb</Data>
      </EventData>
    </Event>
    It appears that 'CameraRaw.dll' may be causing the problem.
    Can you suggest a solution?

    My PC constantly BSODs when running LR4 RC2.  This will happen within 5 minutes of attempting to Upload to the WEB.
    I have also experienced BSOD while processing photos in LR.
    PC Config:
    Gigabyte GA-P55M-UD2 mobo
    Intel I7 870, 2.93 ghz
    16 gb Crucial Ram
    Samsung SSD 830, 256 gb System Drives
    WD + Seagate Data drives
    XFX HD 4870 Video
    Here is the most recent Error log from Event Viewer:
    Log Name: 
    Application
    Source:   
    Application Error
    Date:     
    5/24/2012 11:26:35 PM
    Event ID: 
    1000
    Task Category: (100)
    Level:    
    Error
    Keywords: 
    Classic
    User:     
    N/A
    Computer: 
    PJR-QUAD-112009
    Description:
    Faulting application name: lightroom.exe, version: 4.1.0.11, time stamp: 0x4f9700dd
    Faulting module name: CameraRaw.dll, version: 4.1.0.7, time stamp: 0x4f9700ab
    Exception code: 0xc0000005
    Fault offset: 0x0000000000176005
    Faulting process id: 0x1434
    Faulting application start time: 0x01cd3a251ed7b04b
    Faulting application path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\lightroom.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\CameraRaw.dll
    Report Id: 6d9c47d1-a619-11e1-95cd-00241ddafbbb
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-05-25T03:26:35.000000000Z" />
    <EventRecordID>136058</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PJR-QUAD-112009</Computer>
    <Security />
      </System>
      <EventData>
    <Data>lightroom.exe</Data>
    <Data>4.1.0.11</Data>
    <Data>4f9700dd</Data>
    <Data>CameraRaw.dll</Data>
    <Data>4.1.0.7</Data>
    <Data>4f9700ab</Data>
    <Data>c0000005</Data>
    <Data>0000000000176005</Data>
    <Data>1434</Data>
    <Data>01cd3a251ed7b04b</Data>
    <Data>C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\lightroom.exe</Data>
    <Data>C:\Program Files\Adobe\Adobe Photoshop Lightroom 4 RC2\CameraRaw.dll</Data>
    <Data>6d9c47d1-a619-11e1-95cd-00241ddafbbb</Data>
      </EventData>
    </Event>
    It appears that 'CameraRaw.dll' may be causing the problem.
    Can you suggest a solution?

  • MSI 770-C45 Constant BSOD

    Hi,
    About a month ago I updated my video card drivers, bios and chip set drivers to their latest versions. After doing this my system has become increasingly more unstable giving me BSOD with PFN_LIST_CORRUPT and MEMORY_MANAGEMENT reasons. I am also getting a lot of application crashes (Explorer, Display Device, Direct Show) and freezes.
    The BSOD's seem to disappear sometimes for a few days (usually after I've gone into safe mode to check something) and then after a cold boot come back again.
    My first thought was that this is due to the display driver as the system can be completely stable when running from a DVI connection and then gives these BSOD's when the HDMI connection with HDMI audio is connected. However after lots of good support from ATI/AMD they are pointing the finger at other hardware (memory/motherboard).
    I have run memtest86+ against my OCZ Gold 12800 Dual Channel however it shows no errors. I checked my timings and found them to be off: had 7-7-7-16 in BIOS and 6-6-6-15 in CPUID (anyone know why these would be different). So I changed the settings to force 8-8-8 (could not change TRAS so it is still showing as 16 rather than 24). I also read a few other forum posts that boosted the voltage to the NB and DRAM... therefore I set the voltage to the NB CPU at 1.6 (max before red) and DRAM at 1.63 (max before red). I also changed the spread spectrum to disabled and forced the 1T/2T to 2T. However after all these changes, the system has become slightly more stable (would run a few benchmarks) but would then crash again while doing something random (playing a game or using notepad) with another BSOD with MEMORY MANAGEMENT error.
    Anyone know what settings I should be using for my OCZ3G16002G? Could the fact that the memory states 1.7 volts and I can only set 1.63? Could it be that I cannot seem to change the TRAS and it seems to auto set it to 16? Any other ideas?
    I'm at a loss with this system, any help would be much appreciated.
    Gary
    AMD Phenom II X4 955 BE
    MSI 770-C45
    ATI RADEON 5670 HD
    4GB OCZ 1600 Gold Edition Dual Channel

    Hi,
    I have a 500 watt Coolermaster 80+ PSU. The memory is 2 DIMMS of OCZ3G16002G (by OCZ) rated for 8-8-8-24. I have no overclocking running... if fact this is a media system and thus I am running AMD cool and quiet.
    I am running Win 7 64 bit with latest updates.
    As further information, tonight I tried to change the memory timings again, but can only set the CAS, TRCD and TRP. I don't seem to be able to change the TRAS (states auto in bios and defaults to 16). When running benchmarks on the system tonight, the crashes appear less frequent but happen after the system is placed under more stress. I have also started to see two new BSOD messages: "Bad Pool Headers" and "Bad Pool Caller".
    Cheers,
    Gary

  • Constant BSOD with nidgpibk.sys when receiving GPIB commands

    Greetings,
    I have a mainframe with a PXI GPIB card installed.  I'm controlling the mainframe with my PC using GPIB and very frequently, the mainframe crashes (BSOD) listed nidgpibk.sys as the culprit.  Them mainframe manufacturer says they can only use NI-Device 1.1 since it's the only version compatible with their system.
    Is nigpibk.sys part of the NI-Device install?  Is there any way to debug or fix this problem?
    Thanks,
    Jason

    Hi,
    Was there ever a solution found for this? I'm getting the same BSOD using the
    nidmgpib.sys driver (v1.5).
    The company we're working with says upgrading is not a quick fix, as they have
    a lot invested in this driver.
    Attached is the dump file.
    Thanks,
    Jeff
    Attachments:
    DumpAnalyzed.TXT ‏10 KB

  • Constant BSOD after fresh Lion Install

    I have installed Lion from Apple recently and now I get a costant stream of Black Screen of Deaths.
    It happens when I scroll usually (mouse or touchpad)... but has happened during other times...
    I am now running gfxCardStatus to lock it into Integrated Only mode to try and get some work done.
    Please help us fix this Apple.   We paid A LOT for these MacBook Pros and I do not want to tell people that buying one was a mistake.
    I already have clients wondering why I am having problems with my Apple notebook.
    Hoping for a fix soon!
    Here is the last panic report, which I did send to Apple... I send it every time.
    Interval Since Last Panic Report:  150594 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    A26AACC3-94C9-495B-AD9C-7BA5A27522B2
    Mon Jul 16 10:05:18 2012
    panic(cpu 2 caller 0xffffff7f80958947): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff809f398000 0x0a5480a2, D0, P3/4
    Backtrace (CPU 2), Frame : Return Address
    0xffffff807bcaafb0 : 0xffffff8000220792
    0xffffff807bcab030 : 0xffffff7f80958947
    0xffffff807bcab0c0 : 0xffffff7f80a48aa4
    0xffffff807bcab110 : 0xffffff7f80a48b64
    0xffffff807bcab170 : 0xffffff7f80cf5749
    0xffffff807bcab2b0 : 0xffffff7f80a67bed
    0xffffff807bcab2e0 : 0xffffff7f809622c2
    0xffffff807bcab390 : 0xffffff7f8095dbc4
    0xffffff807bcab580 : 0xffffff7f8095ee97
    0xffffff807bcab640 : 0xffffff7f817ee216
    0xffffff807bcab6f0 : 0xffffff7f81815a6d
    0xffffff807bcab770 : 0xffffff7f8180044b
    0xffffff807bcab7d0 : 0xffffff7f81800846
    0xffffff807bcab820 : 0xffffff7f81800abb
    0xffffff807bcab8b0 : 0xffffff7f8180180f
    0xffffff807bcab8e0 : 0xffffff7f817b90b0
    0xffffff807bcabaa0 : 0xffffff7f81801f68
    0xffffff807bcabb60 : 0xffffff7f817b6119
    0xffffff807bcabbc0 : 0xffffff800065501e
    0xffffff807bcabbe0 : 0xffffff80006558fa
    0xffffff807bcabc40 : 0xffffff800065609b
    0xffffff807bcabd80 : 0xffffff80002a3f08
    0xffffff807bcabe80 : 0xffffff8000223096
    0xffffff807bcabeb0 : 0xffffff80002148a9
    0xffffff807bcabf10 : 0xffffff800021bbd8
    0xffffff807bcabf70 : 0xffffff80002aef20
    0xffffff807bcabfb0 : 0xffffff80002daa33
          Kernel Extensions in backtrace:
             com.apple.NVDAResman(7.1.8)[560E1257-BF5E-3B0B-95F0-15033A0D1B97]@0xffffff7f808 f8000->0xffffff7f80bd1fff
                dependency: com.apple.iokit.IOPCIFamily(2.6.8)[06C77CAA-586C-3AA7-94B7-A544F470025E]@0xffff ff7f80883000
                dependency: com.apple.iokit.IONDRVSupport(2.3.2)[D05CFB53-FB72-3613-8162-2D188DB04738]@0xff ffff7f808e6000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[2D2A4A31-EB4F-3730-BE3A-76C061685FC5]@0 xffffff7f808ae000
             com.apple.nvidia.nv50hal(7.1.8)[7596DB8C-AE9D-3C87-B11A-0ED8F940CAF8]@0xffffff7 f80bd2000->0xffffff7f80ef3fff
                dependency: com.apple.NVDAResman(7.1.8)[560E1257-BF5E-3B0B-95F0-15033A0D1B97]@0xffffff7f808 f8000
             com.apple.GeForce(7.1.8)[00925AF3-22EE-3858-8BD3-06AE57DFCC86]@0xffffff7f817ab0 00->0xffffff7f8186afff
                dependency: com.apple.NVDAResman(7.1.8)[560E1257-BF5E-3B0B-95F0-15033A0D1B97]@0xffffff7f808 f8000
                dependency: com.apple.iokit.IONDRVSupport(2.3.2)[D05CFB53-FB72-3613-8162-2D188DB04738]@0xff ffff7f808e6000
                dependency: com.apple.iokit.IOPCIFamily(2.6.8)[06C77CAA-586C-3AA7-94B7-A544F470025E]@0xffff ff7f80883000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[2D2A4A31-EB4F-3730-BE3A-76C061685FC5]@0 xffffff7f808ae000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    11E53
    Kernel version:
    Darwin Kernel Version 11.4.0: Mon Apr  9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
    Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
    System model name: MacBookPro6,2 (Mac-F22586C8)
    System uptime in nanoseconds: 2557261426519
    last loaded kext at 146897699361: com.apple.filesystems.smbfs          1.7.2 (addr 0xffffff7f807f2000, size 241664)
    loaded kexts:
    com.apple.filesystems.smbfs          1.7.2
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.filesystems.autofs          3.0
    com.apple.filesystems.ntfs          3.10.1
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.driver.AudioAUUC          1.59
    com.apple.driver.AppleHDAHardwareConfigDriver          2.2.0f3
    com.apple.driver.AppleHDA          2.2.0f3
    com.apple.driver.AppleMikeyDriver          2.2.0f3
    com.apple.driver.AppleIntelHDGraphics          7.1.8
    com.apple.driver.AppleTyMCEDriver          1.0.2d2
    com.apple.driver.AGPM          100.12.42
    com.apple.driver.AppleUpstreamUserClient          3.5.9
    com.apple.driver.AppleMCCSControl          1.0.26
    com.apple.driver.AppleIntelHDGraphicsFB          7.1.8
    com.apple.driver.SMCMotionSensor          3.0.2d6
    com.apple.driver.AppleSMCPDRC          5.0.0d0
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.driver.AppleSMCLMU          2.0.1d2
    com.apple.iokit.IOBluetoothSerialManager          4.0.5f11
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AudioIPCDriver          1.2.2
    com.apple.driver.ACPI_SMC_PlatformPlugin          5.0.0d0
    com.apple.GeForce          7.1.8
    com.apple.driver.AppleMuxControl          3.0.16
    com.apple.driver.AppleLPC          1.5.8
    com.apple.driver.AppleBacklight          170.1.9
    com.apple.driver.AppleUSBTCButtons          225.2
    com.apple.driver.BroadcomUSBBluetoothHCIController          4.0.5f11
    com.apple.driver.AppleUSBCardReader          3.0.1
    com.apple.driver.AppleIRController          312
    com.apple.driver.AppleUSBTCKeyEventDriver          225.2
    com.apple.driver.AppleUSBTCKeyboard          225.2
    com.apple.iokit.SCSITaskUserClient          3.2.0
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          33
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCISerialATAPI          2.0.3
    com.apple.iokit.IOAHCIBlockStorage          2.0.3
    com.apple.driver.AppleUSBHub          4.5.0
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.iokit.AppleBCM5701Ethernet          3.1.2b2
    com.apple.driver.AppleEFINVRAM          1.5.0
    com.apple.driver.AirPort.Brcm4331          530.4.20
    com.apple.driver.AppleAHCIPort          2.3.0
    com.apple.driver.AppleUSBUHCI          4.4.5
    com.apple.driver.AppleUSBEHCI          4.5.8
    com.apple.driver.AppleACPIButtons          1.5
    com.apple.driver.AppleFWOHCI          4.8.9
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.6
    com.apple.driver.AppleSMBIOS          1.8
    com.apple.driver.AppleACPIEC          1.5
    com.apple.driver.AppleAPIC          1.5
    com.apple.driver.AppleIntelCPUPowerManagementClient          193.0.0
    com.apple.nke.applicationfirewall          3.2.30
    com.apple.security.quarantine          1.3
    com.apple.driver.AppleIntelCPUPowerManagement          193.0.0
    com.apple.kext.triggers          1.0
    com.apple.driver.DspFuncLib          2.2.0f3
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.iokit.IOSurface          80.0.2
    com.apple.iokit.IOFireWireIP          2.2.4
    com.apple.iokit.IOSerialFamily          10.0.5
    com.apple.driver.AppleHDAController          2.2.0f3
    com.apple.iokit.IOHDAFamily          2.2.0f3
    com.apple.iokit.IOAudioFamily          1.8.6fc17
    com.apple.kext.OSvKernDSPLib          1.3
    com.apple.driver.ApplePolicyControl          3.0.16
    com.apple.driver.AppleSMC          3.1.3d8
    com.apple.driver.IOPlatformPluginLegacy          5.0.0d0
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.driver.AppleGraphicsControl          3.0.16
    com.apple.driver.IOPlatformPluginFamily          5.1.0d17
    com.apple.driver.AppleBacklightExpert          1.0.3
    com.apple.nvidia.nv50hal          7.1.8
    com.apple.NVDAResman          7.1.8
    com.apple.iokit.IONDRVSupport          2.3.2
    com.apple.iokit.IOGraphicsFamily          2.3.2
    com.apple.driver.AppleUSBBluetoothHCIController          4.0.5f11
    com.apple.iokit.IOBluetoothFamily          4.0.5f11
    com.apple.driver.AppleFileSystemDriver          13
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.2.0
    com.apple.iokit.IOUSBMassStorageClass          3.0.1
    com.apple.driver.AppleUSBMultitouch          227.1
    com.apple.iokit.IOUSBHIDDriver          4.4.5
    com.apple.driver.AppleUSBMergeNub          4.5.3
    com.apple.driver.AppleUSBComposite          4.5.8
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.2.0
    com.apple.iokit.IOBDStorageFamily          1.6
    com.apple.iokit.IODVDStorageFamily          1.7
    com.apple.iokit.IOCDStorageFamily          1.7
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.2.0
    com.apple.iokit.IOUSBUserClient          4.5.8
    com.apple.iokit.IOEthernetAVBController          1.0.1b1
    com.apple.iokit.IO80211Family          420.3
    com.apple.iokit.IONetworkingFamily          2.1
    com.apple.iokit.IOAHCIFamily          2.0.8
    com.apple.iokit.IOUSBFamily          4.5.8
    com.apple.driver.AppleEFIRuntime          1.5.0
    com.apple.iokit.IOHIDFamily          1.7.1
    com.apple.iokit.IOFireWireFamily          4.4.5
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          177.5
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          331.6
    com.apple.iokit.IOStorageFamily          1.7.1
    com.apple.driver.AppleKeyStore          28.18
    com.apple.driver.AppleACPIPlatform          1.5
    com.apple.iokit.IOPCIFamily          2.6.8
    com.apple.iokit.IOACPIFamily          1.4

    Then you have a hardware problem. Take it to Apple and have it checked out.

  • Re: Intel 4790k / MSI Z97A Gaming 7 / GSkill ripjawsx 16Gb - New PC constant BSOD.

    Be careful when removing/inserting the memory not to damage the slots or the PCB.
    Normally I would recommend doing all installation and tests outside the case before assembling it in.

    Temps are fine..
    CPU is hovering between 40-50C and likewise for the GPU.
    I should add that recently I had my i7 4790K replaced on an RMA and after getting the new one I seem to be facing the same issue.
    My system is starting up with minimal services a...

  • BSoD on a new machine

    Hi, people.
    I've just bought and assembled a new computer and I'm having constant BSoDs (usually with disturbing sound effect like looping the last bit of sound, which sounds like "bzzzzz" or "brrrrrr", or even "beeeeep"), game crashes (always
    c0000005 code) and "video driver has stopped responding and recovered" messages at random moments.
    Specs (used Piriform Speccy):
    OS: Windows 7 Ultimate 64-bit SP1 (not activated yet)
    CPU: Intel Core i7 4770 @ 3.40GHz    27 °C Haswell 22nm Technology
    RAM: 16,0GB 2-channel DDR3 @ 799 MHz (9-11-11-29)
    Motherboard: Gigabyte Technology Co., Ltd. Z87X-D3H-CF (SOCKET 0)    28 °C
    GPU: Intel HD Graphics 4600 (Gigabyte)
            4095 МБNVIDIA GeForce GTX 760 (Gigabyte)    32 °C
            4095 МБNVIDIA GeForce GTX 760 (Gigabyte)    29 °C
    Storage: 111GB ATA Samsung SSD 840 SCSI Disk Device (SSD)    32 °C
    Disk drive: Optiarc DVD RW AD-7280S SCSI CdRom Device
    Sound devices: Creative Sound Blaster Z
    Power Supply: ATX Corsair HX 1050, CP-902, 1200W
    DxDiag: DirectX 11, driver version 9.18.13.3182, driver model WDDM 1.1
    GeForce Experience Info: GeForce R331 Game Ready Driver, version 331.82, timestamp 19.11.2013
    BSoD codes:
    driver_irql_not_less_or_equal
    page_fault_in_nonpaged_area
    BSoD driver file: dxgmms1.sys (attempting to corrupt the system, revealed using the Windows Driver Verifier)
    So, I've downloaded and installed the latest motherboard, GPU, SSD and soundcard drivers from their official sites, deinstalling older versions using Driver Cleaner and CCleaner. I've tested my RAM with memtest and found no problems. I've done a stress-test
    using the AIDA64 - no errors. Monitoring the temperature during the stress-test and usual activities revealed no overheat. AHCI mode is set. SLI is configured through the NVidia panel. No overclocked CPU. No problems when rendering with GPU (i.e. no artifacts/hangs).
    BIOS menu displays no voltage problems. No cable connection problems seen at the moment.
    Also, tried with two different Windows - Professional and Ultimate, same errors. HALP PLEASE.
    Minidumps: http://anonymousdelivers.us/97897
    P.S. Forgot to say, the computer is connected through a voltage regulator APC Line-R 1200. Instead of a monitor I use my TV (Samsung) connected via HDMI to the top GPU.
    UPD 1: Okay, tried both of available WHQL driver versions for my GPU (320.49 and 327.23, now using 320.49) Still having random BSoDs with no driver specified (usually 0x0000001E) with weird noises when BSoD (using the motherboard output or the soundcard
    changes nothing).
    Also, the Windows Driver Verifier now does not give a BSoD.
    UPD: Noticed strange temperature changes on the top GPU: fading from 45° to 39° when writing this post. No game or other graphics rendering program is running, only Firefox (both of the NVidia 3d VISION plugins disabled) and Speccy.
    UPD 2: Got another SYSTEM_SERVICE_EXCEPTION BSoD while scrolling a page with Mozilla.
    UPD 3: Experiencing strange application unstability - crashes & hangs (seen crashing AC3, Firefox, Flash Player, Samsung Magician, dwm.exe, all with c0000005 error).

    Dverlik
    These were Related to
    nvlddmkm.sys nVidia Display Driver.  There is a known problem with the current version (which is yours).   I would revert back to a much older one (say a generation).
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {e1, a, 0, fffff8800f88238f}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+738f )
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000000000e1, memory referenced
    Arg2: 000000000000000a, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800f88238f, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c0100
    GetUlongFromAddress: unable to read from fffff800034c01c0
    00000000000000e1 Nonpaged pool
    CURRENT_IRQL: a
    FAULTING_IP:
    nvlddmkm+738f
    fffff880`0f88238f 4c8bb8e0000000 mov r15,qword ptr [rax+0E0h]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    PROCESS_NAME: System
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    DPC_STACK_BASE: FFFFF80000BA2FB0
    TRAP_FRAME: fffff80000b9bf70 -- (.trap 0xfffff80000b9bf70)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=fffffa80146d7000
    rdx=fffff80000b9c4f8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800f88238f rsp=fffff80000b9c100 rbp=fffff80000b9c200
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    nvlddmkm+0x738f:
    fffff880`0f88238f 4c8bb8e0000000 mov r15,qword ptr [rax+0E0h] ds:00000000`000000e1=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80003288169 to fffff80003288bc0
    STACK_TEXT:
    fffff800`00b9be28 fffff800`03288169 : 00000000`0000000a 00000000`000000e1 00000000`0000000a 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9be30 fffff800`03286de0 : 00000001`0000000f 00000002`00000001 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9bf70 fffff880`0f88238f : 00000438`00000780 00000000`00000000 fffff800`00b9c200 00000000`00000000 : nt!KiPageFault+0x260
    fffff800`00b9c100 00000438`00000780 : 00000000`00000000 fffff800`00b9c200 00000000`00000000 fffffa80`25306640 : nvlddmkm+0x738f
    fffff800`00b9c108 00000000`00000000 : fffff800`00b9c200 00000000`00000000 fffffa80`25306640 fffff880`03974180 : 0x00000438`00000780
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nvlddmkm+738f
    fffff880`0f88238f 4c8bb8e0000000 mov r15,qword ptr [rax+0E0h]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nvlddmkm+738f
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME: nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75
    FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+738f
    BUCKET_ID: X64_0xD1_nvlddmkm+738f
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0xd1_nvlddmkm+738f
    Wanikiya and Dyami--Team Zigzag

Maybe you are looking for