P67A-C43 - Windows 7 64bit - Random BSOD

Quote
Machine Specs:
P67A-C43 (B3) 1.14, i5 2500k
Windows 7 Ultimate 64bit
16GB (4x4GB) Corsair CMZ8GX3M2A1600C9
Coolermaster GX650 (+12v~52a, +5v~25A, 3.3v~25A)
Gigabyte GeForce GTX 460 1GB Super Overclock Edition
Sata 1: Western Digital 750GB WDC WD5 00AACS-00D6B0 (Boot Drive)
Sata 2: Seagate Barracuda Green 2TB ST2000DL003
Sata 3: Seagate Barracuda Green 2TB ST2000DL003
Sata 4: Seagate 1.5TB ST315003 41AS
Sata 5: LG Blu-ray/HD-DVD Drive GGw-H20L
Sata 6: LG DVD-Rom GH22NS70
Hotway HUR1-SU3S2 USB3.0/eSATA Dual Bay
1x Western Digital 750GB WDC WD5 00AACS-00D6B0
1x Seagate 1.5TB ST315003 41AS
Permanent/Regular programs running:
AVG Anitu-Virus Free Edition 2012
WinVNC (to connect with HippoRemote on my iphone)
Itunes Helper and Apple Push (in startup items under msconfig)
RazerHID Application (for my mouse)
jdownloader - not a startup application. But is open most of the time even when I'm not downloading
A few common BSOD messages I've had:
STOP: 0x0000003B didn't get the string code
STOP: 0x00000024 (0x00000000000c08a2....) didn't get rest of string
STOP: 0x0000001A (0x0000000000041790, 0xFFFFFA8008CD2190, 0x000000000000FFFF, 0x0000000000000000) - Memory management... got this the last 2 times it crashed
Although there have been a few others. This one seemed to be a one off while trying to install Windows Updates)
STOP: 0x00000051   (0x0000000000000001, 0xFFFFF8A018295010, 0x0000000084919000, 0x0000000000000465) - Registry Error
The crashes seem to be at random, but most often they occur while browsing the internet. For example I can be watching movies or tv shows through XBMC for hours and it runs perfect. Then I'll load up an internet browser and it will crash not long after.
Although the last crash I had was while watching a TV Show in XBMC. My computer had not been on very long, and it was only 10 minutes into the show. Although I was running jdownloader in the background. I also have AVG 2012 Free Edition running permanently.
Things I've tried that didn't work:
I've disabled the USB3.0 drives and the problem still occured. I thought they might have been the issue as they cause my computer to freeze on boot or in the BIOS (or boot EXTREMELY slowly) when it's switched on. Although the second I switch it off everything continues as normal. Would like to fix this issue too, but compared to the BSOD it's really a nothing issue.
I've updated my video card, USB 3.0 and Ethernet drivers.
I've upped the voltage on the RAM (not by much).
I've fiddled with some of the Turbo etc. settings for CPU.
I updated to the most recent BIOS.
I switched web browsers. Originally I had Chrome and each crash seemed to happen while using it, so I went to Firefox and it didn't change at all.
I switched my RAM around (Blue slots to black and vice-versa)
Currently trying:
I've removed 2 sticks of RAM. When/if it crashes again I'll swap in the other two sticks. Unfortunately it can run for ages before it crashes, so it's hard to tell whether an attempted fix has worked until it crashes and I know for certain that it hasn't.
Im pretty sure RAM is the most likely cause of the problem. But the PC was running fine up until the last 3 weeks or so. I got a BSOD a few weeks back which seemed to be a one off. Then a week or so later another one. Now it's happening daily.. sometimes 3 or 4 times. I would google the codes back when they happened and was lead toward different possibilities.. which is why I tried Chrome, Drivers and unplugging USB devices. Although obviously RAM seemed to be the most common possibility.

When did you start to see this crashing start?
Try running >>Memtest86<< on the RAM individually.
Try to uninstall jdownloader.

Similar Messages

  • P67A-C43 / Windows 7 64-bit freezes when idle or during low activity

    Greetings,
    I've seen a few similar topics regarding freezes when idle or near-idle, but the troubleshooting steps I've tried don't seem to work. My P67A-C43 with an Intel 2500K Core i5 is not overclocked. It is repeatedly freezing in Windows 7 64-bit. It also did this when I was running Vista 64-bit. I also have Mac OS X Lion on this PC, and I never get freezes under OS X. This appears to be something related to how Windows interacts with idling or lower-power states. But I can't figure out what.
    I have tried this with windows on a mechanical HDD and with the current SSD - no change.
    I have tried running just one RAM module at a time - they both individually exhibit the behavior.
    I have tried switching graphics cards from a GeForce 6500 GT to the current Radeon HD 6850 - no change.
    I have tried switching power supplies from an Inland Gold 500W to the current OCZ 650W - no change.
    I have tried switching from Intel SVID to APS mode stepping - no change.
    I have tried switching C-States off - the system didn't freeze, but it got VERY hot under no load. Without C-states turned on, the CPU temperatures quickly reach 95C to 98C.
    I've got the latest BIOS, the latest drivers, and everything else I can think of. Any more ideas?

     
    WOW do I feel silly.
    I opened the case to take a good look at the processor cooling, and found that the fan/heatsink assembly was not snapped in on one of the posts. The pre-applied thermal paste was only flattened on one side of the copper contacts for the heatsink.
    I re-attached and snapped it all back in, and now my BIOS temperature reading is about 55C, whether C-State is on or off. In Windows without much of a load, it was 40-45C with C-States off, and 33-45C with C-States on.
    What I've learned:
    - double check your connections
    - C-States is an amazingly effective system
    - Intel makes some darn tough chips. They'll work (sort of) even if you install them wrong. 
    I'm still not sure if the freezing is fixed - I don't know how long I've been running without a proper heat sink. I'll leave it idling overnight (It's 23:30 here now), and see if it freezes.
    Thanks for the help, guys. This is a nice forum.

  • Windows crashing - random BSOD on Windows 7 64-bit

    Hello
    I tried reading this forum and tried IMO everything but computer still gets BSOD. I'm including Dump File. I don't know how to read it. Any advice?
    http://sdrv.ms/1gwJEKq
    What I did:
    memtest86 - passed
    ccleaner
    regcleaner
    antivirus scan
    reinstalled drivers
    chkdsk
    I have mirrored drives on windows. It shows 'resynching'. Could it be failing and causing the problem?

    Mindau
    This one crash was Related to the
    nvvad64v.sys NVIDIA Virtual Audio Driver from NVIDIA Corporation  I would install the newest driver available.
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\013114-22495-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
    Machine Name:
    Kernel base = 0xfffff800`03467000 PsLoadedModuleList = 0xfffff800`036a3e70
    Debug session time: Fri Jan 31 05:39:43.583 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:28.095
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {10, 2, 0, fffff880044f8689}
    *** WARNING: Unable to verify timestamp for nvvad64v.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
    Probably caused by : nvvad64v.sys ( nvvad64v+1689 )
    Followup: MachineOwner
    8: kd> !analyze -v
    * Bugcheck Analysis *
    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: 0000000000000010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880044f8689, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370e0e0
    GetUlongFromAddress: unable to read from fffff8000370e198
    0000000000000010 Nonpaged pool
    CURRENT_IRQL: 2
    FAULTING_IP:
    nvvad64v+1689
    fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    PROCESS_NAME: audiodg.exe
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME: fffff8800eb894c0 -- (.trap 0xfffff8800eb894c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80179a6fd0
    rdx=0000000000003fdc rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880044f8689 rsp=fffff8800eb89650 rbp=0000000000000000
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=fffffa80179a6fd0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nvvad64v+0x1689:
    fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h] ds:00000000`00000010=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff800034d5de9 to fffff800034d6880
    STACK_TEXT:
    fffff880`0eb89378 fffff800`034d5de9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0eb89380 fffff800`034d4a60 : 00000000`00000000 00000000`0000100c fffffa80`1611a260 fffff880`035e61c0 : nt!KiBugCheckDispatch+0x69
    fffff880`0eb894c0 fffff880`044f8689 : 00000000`0031c8d3 fffffa80`179a4000 00000000`00000000 fffff800`03665888 : nt!KiPageFault+0x260
    fffff880`0eb89650 00000000`0031c8d3 : fffffa80`179a4000 00000000`00000000 fffff800`03665888 00000000`00000028 : nvvad64v+0x1689
    fffff880`0eb89658 fffffa80`179a4000 : 00000000`00000000 fffff800`03665888 00000000`00000028 00000000`00524fbc : 0x31c8d3
    fffff880`0eb89660 00000000`00000000 : fffff800`03665888 00000000`00000028 00000000`00524fbc 00000000`00002fbc : 0xfffffa80`179a4000
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nvvad64v+1689
    fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nvvad64v+1689
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nvvad64v
    IMAGE_NAME: nvvad64v.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 529fb649
    FAILURE_BUCKET_ID: X64_0xD1_nvvad64v+1689
    BUCKET_ID: X64_0xD1_nvvad64v+1689
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:x64_0xd1_nvvad64v+1689
    FAILURE_ID_HASH: {58ea0214-7b27-7dc6-5a00-c215a7e166cc}
    Followup: MachineOwner
    Wanikiya and Dyami--Team Zigzag

  • Random bsod windows 7 64bit

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

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

  • Problem: P67A-C43 - Random Hard lockups

    Problem:  Random hard lockups with any power management features on (c-state, C1E, etc) and RAM set to X.M.P mode.  The system is not overclocked at all.
    P67A-C43 V1.A (aka Version: V1.10), i5 2500K, Windows 7 Ultimate 64-bit
    CORSAIR XMS 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) CMX8GX3M2A1600C9
    CORSAIR CMPSU-750TX 750W ATX12V v2.2 SLI
    ASUS HD6950
    WD Caviar Black WD1002FAEX 1TB running in SATA 6.0
    TST corp DVD/CD R-W w/LightScribe combo drive
    Description:  Random hard lockups with any power management features on (c-state, C1E) and RAM set to X.M.P mode.  Also experiencing jittery mouse.  As suggested in another thread, turn off all power management features and manually set RAM to DDR1333 along with changing the voltage.  This seemed to have helped as I have had no lockups in two days and my mouse is significantly better.
    I have read that there is not much difference running in XMP mode and I understand that but I would like to take advantage of the power management features and eventually overclock as well.  Please let me know if you need any more info from cpu-z etc.  Thanks in advance!

    Your mem setting changes probably solved the problem. You need to enable your power saving features again to test them one by one. Leave EuP2013 disabled.

  • P67A-GD55 - Random BSODs with varying codes

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

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

  • Windows server 2012 R2 randomly BSOD's

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

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

  • Random BSOD after installing Windows 8.1 on Lynx K3011

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

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

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

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

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

  • MSI P67A-C43 (B3) USB not working but theres a twist! Help!

     :lol_anim:I Have built a new rig with the MSI P67A-C43 (B3) Motherboard, 16GB DDR3 PC3-10600 1333MHz Memory (4GB x 4), Intel Core i5-2500K 3.3GHz 6M LGA1155 Processor, 550 Watt 80 PLUS Bronze Power Supply,24x DVDRW, 3.5" Internal Card Reader with 2 USB ports,    500GB 7200RPM 3.5" SATA Hard Drive(which i plan on upgrading just didnt want to waste money on the shitty HD they had.....
    So down to the nitty gritty  . My computer is running Windows 7 64 Bit, i have downloaded all of the updates and all of the Chip-set drivers, Bios, etc... i ran a system registry tool to clean up any errors in my registry and i have ALL of my drivers up to date.
    I have my USB mouse and keyboard that connect fine and are recognized by my computer, sometimes they stop working and start back up within seconds but windows does display any type of error or disconnection "this may have been fixed due to the registry cleaner i used i haven't had any hiccups yet" so i have my USB mouse and USB keyboard working fine and dandy now i think. got a new headset and the windows finds the USB Headset and it works Perfectly fine. BUT and this is where my whole frustration comes out. Whenever i connect my I-Pod Touch, I-Pod Nano, My Cell phone to copy files to from my SD Card, or my External My Passport drive Windows says "USB Device was not recognized" notification and in the Device manager it shows the one device with a yellow exclamation point and says "Unknown Device" I have tried to uninstall the USB hubs and reinstalled them perfectly restarted windows, still non of the devices work. i have tried making sure that windows tries not to turn off the device to save power, when i say i have tried almost everything i mean everything that is related with USB Device not Recognized. So i do not know what to do now, i have contacted the Manufacturer and they don't know squat about it or what could be causing it. the only thing i can think of is there is some hardware maybe that is not compatible i do hear some beeps when i start up i will have to come back and update how many beeps" i saw another post that it means the motherboard is trying to tell me something maybe this could be the issue. but i have tried every single usb port and non of them Recognize the device but when i plus in my mouse and keyboard in diff ports they still work so i am a bit confused. my last step is to return the computer to the manufacturer for a replacement or repair w/e i do not want to do this cause this should be working. my friend has almost the exact same MB and equipment and his works fine so i am getting a little frustrated with the issue Someone Pls Help me out. And yes i have tried turning off the computer, unplugging it and pressing the power button, and waiting like 1 Hour etc and still nothing. Drivers are Up-to-Date and Mother board bios and chip-set drivers are Up-to-Date as well. I hope someone knows or has an answer to help me out!

    Yes the Bios is Up-to-Date and they are not plugged into the Blue USB 3.0 ports(x2). oh and forgot to mention already did a clean install again of Windows 7 64bit and still nothing.  Im also wondering if the power supply is enough?? maybe?

  • MSI P67A-C43 (B3) & OCZ Vertex 3 VTX3-25SAT3 Issues

    Specifications:
    Quote
    Mobo/Laptop: MSI P67A-C43 (B3)
    BIOS: 1.B (2011-04-14)
    CPU: Intel Core i5-2500K
    RAM: 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 CML8GX3M2A1600C9B
    Vid: ASUS ENGTX560 TI DCII TOP/2DI/1GD5 GeForce GTX 560 Ti
    PSU: HX750 (CMPSU-750HX)
    HDD: OCZ Vertex 3 VTX3-25SAT3-120G v2.11
    Chipset: Intel P67 (B3) RSD v10.6.0.1002
    OS: Windows 7 Ultimate 64 Bit SP1
    Let's start from the beginning: So I built my PC in July and ever since I've been having on and off BSODs with the Vertex 3 drive. Mostly they'll happen once a week. When I first built the machine my drive came with Firmware 2.06. I installed all the drivers from MSI's website as well as the latest Intel Rapid Storage Drivers. Eventually I flashed the SSD to 2.11 when it was released but still had similar issues. Hotplugging was enabled when I installed Windows 7 for the first time AND when I flashed to 2.11 from 2.06. Some members over on the OCZ boards stated this might have been the cause of the BSOD. Basically the PC froze, BSOD'd, restarted, and then the system couldn't detect the drive. I had to power the system down, remove the power cable, wait 10 seconds, re-connect the cable and power on the PC. After I did this Windows booted normally.
    I received some advice on the OCZ forums to reset CMOS and leave hotplugging disabled. Then re-flash the drive to 2.11 with hotplugging disabled. Some members thought this would make the drive act like an internal drive, not an external drive. However, a week after doing this the same BSOD appeared. I've started from scratch last week by secure erasing the drive and re-installing Windows, but same issues. I noticed MSI released a new BIOS for my board in July. I have the one from April currently.
    Is it worth upgrading my BIOS? The listed fixes don't say anything about SSDs.
    I plan on trying this when I get home from work:
    Quote from: Tony;676791
    Going to keep this brief and to the point, this hack will force the 2 primary sata2 or sata3 ports on the motherboards to be designated Internal only...You can do this hack for all Intel chipsets from around ICH8 onwards in win7 and Vista.
    You also need to make sure hotplugging is disabled in uefi/bios if your boards bios has the option(s) do this first before you do any of these regedits etc
    1 Remove all traces of Intel drivers on your system, that means remove the management engine driver, the RST driver and the INF driver, you do this thru the programs and features option in control panel.  I remove them all before I reboot, the system will automagically set you using the MSAHCI driver.
    2 Now reboot, let win7 detect the ssd and reboot again.
    3 now open a elevated command window (CMD with administrator privileges) and copy/paste the following...then hit enter.
    Code: [Select]
    reg.exe add "HKLM\SYSTEM\CurrentControlSet\Services\msahci\Controller0\Channel0" /f /v TreatAsInternalPort /t REG_DWORD /d 0x00000001 
    Once you hit enter you can then add the following again using copy/paste.
    Code: [Select]
    reg.exe add "HKLM\SYSTEM\CurrentControlSet\Services\msahci\Controller0\Channel1" /f /v TreatAsInternalPort /t REG_DWORD /d 0x00000001 
    Hit enter and close CMD.EXE down, reboot
    This will now force the 2 sata 3 ports to Internal only, this means they will apply LPM if you set it and will support Automatic Partial to slumber.
    I now suggest you experiment with power schemes, for some high performance may work better than balanced...try both
    You also need to make sure hotplugging is disabled in uefi do this first before you do any of these regedits etc
    If you want to go a step further than this you can try the following...ONLY do this after you have done the steps above.
    remove the SSD to start
    1 create a temporary win7 install on a hdd, use the msahci driver and once installed do the hack to force the 2 ports to internal only. Have the hdd connected to port 1 on the motherboard.
    2 once the install is ready and you have installed toolbox to it power down and connect the SSD to port 0
    3 now boot to the HDD, use the manual boot menu option to make sure you are booting to the HDD and make sure hotplugging is OFF in UEFI
    4 once in win7, flash the FW to the drive, when its finished flashing, close toolbox, reboot back to the HDD and back into win7...make sure the SSD is detected in my computer.
    5 now power off, remove the HDD...then boot to UEFI and make sure to set the SSD as first boot device
    6 Power up, boot to the SSD
    Stay using the MSAHCI driver for now, do not install any INF, IME or RST drivers.
    Edit 09/09/11
    Had a few end users quoting disabling TRIM solved BSOD for them...now im not saying it will solve BSOD for all but it may be worth trying. Remember the SandForce controller was originally designed without TRIM in mind, it functions just fine without it so you should see no loss of performance. If you want to help the controller stay fast you could always add some extra over provisioning by reducing the volume on the drive and leaving that space unallocated...totally up to you what you do though....
    I like 25% OP on my drives, this means if I have a 120 with 115GB showing in windows I lose 15GB to OP and use 100GB for the volume....
    A forum member wrote a little script to enable /disable trim...he wrote in support for wiper for Indilinx drives also...just ignore that part and use the TRIM function only...
    http://www.ocztechnologyforum.com/forum/showthread.php?63830-A-small-script-to-enable-disable-Trim
    Here is a link to force TRIM also.. http://www.ocztechnologyforum.com/forum/showthread.php?73888-Here-s-a-tool-to-force-TRIM-your-entire-drive&p=523305&viewfull=1#post523305  you could if you wanted use this once a week to force the drive to TRIM all marked deleted blocks if you turn off native TRIM in win7.
    Again....not saying this cures any BSOD but a few end users have said they disabled TRIM and issues went away...anything I have suggested here is totally reversible and will do no harm to your systems.
    If this doesn't work and I get a BSOD after a week I'll disable TRIM and if that doesn't work I have no idea. OCZ said they're working on a new firmware release so who knows. I just hate feeling like I am a beta tester.
    If anyone has any suggestions let me know.

    OK, had some time to go test your suggestions here
    These are the 1.5V Vengeance RAM Modules.  Tried installing 2 of the RAM on slots 2 and 4 on their own.  System Boots Fine.
    Went into the BIOS and changed the voltage applied to the RAM modules from
    AUTO to 1.575V.   On AUTO it says is applying 1.5V to the 2x 4GB modules.
    Installed the full 4x RAM on all slots... and the system just shuts down.  Power cycling again.
    What do you think here?  Bad Motherboard?  Can't think of anything else to try...  totally stumped! 
    Thanks!

  • MSI Z97 MPOWER MAX AC, getting Random Bsod

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

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

  • MSI P67A-C43 B3 won't POST with Full RAM Installed

    Hello all,
    I recently purchased the MSI P67A-C43 B3 mainboard as a custom build
    and have been having trouble with it.  I have 16GB of ram for this board
    (4x 4GB) and when I have 8GB installed (slots 1 and 3 filled), it POSTS fine. 
    When I fill ALL the slots for 16GB total, the board won't POST and just
    power cycles ON and OFF and ON and OFF, etc...
    I have replaced the memory and the PSU and am about to replace the
    mainboard, but wanted to ask if anyone might have a suggestion for
    troubleshooting before I do that. 
    Here's what I'm running on the system:
    mainboard:  MSI P67A-C43 B3
    proc: Intel Core i7-2600K 3.4Ghz Unlocked
    proc cooler: Corsair Hydro H80 CPU Liquid Cooler
    ram: Corsair High Perform Vengeance 4GB DDR3 1600Mhz2x4  (4 of these)
    HDD: OCZ TECHNOLOGY 120GB VERTEX PLUS SSD and Seagate 1TB LP Serial ATA HD 5900/32MB/SATA-3G
    CD Drive: Sony Optiarc 24X DVDRW SATA
    video: EVGA GeForce GTX 560 Ti FPB 1024MB GDDR5 PCB PCIe
    PSU: Thermaltake 750W Modular Power Supply. 80+ Bronze
    case: Thermaltake Chaser MK-I Full Tower Gaming Case
    OS:  Microsoft Windows 7 Professional 64Bit DVD
    Any ideas here would be greatly appreciated!  Thanks!

    OK, had some time to go test your suggestions here
    These are the 1.5V Vengeance RAM Modules.  Tried installing 2 of the RAM on slots 2 and 4 on their own.  System Boots Fine.
    Went into the BIOS and changed the voltage applied to the RAM modules from
    AUTO to 1.575V.   On AUTO it says is applying 1.5V to the 2x 4GB modules.
    Installed the full 4x RAM on all slots... and the system just shuts down.  Power cycling again.
    What do you think here?  Bad Motherboard?  Can't think of anything else to try...  totally stumped! 
    Thanks!

  • P67A-c43: Boot Screen / Status Codes / 35-40 sec hang

    I have a P67A-C43 motherboard.  Everything's working fine, but when I boot, I get a black screen with a white underscore cursor blinking in the upper left and a code in the lower right of B4.  It will stay that way for about 35 seconds, then the codes will quickly change 99 92 82 A3.  The MSI splash screen will come up and then Window (7) will launch and 15 seconds later, I'm at the log-in screen.  Is there anyway to speed this up?  I admit, booting up in less than a minute is OK, but the fact that 40 seconds of it is waiting for the BIOS to load kills me.

    You did not provide your system spec. >>Posting Guide<<
    Without having that magic crystal ball I can only assume that it consists of the following:
    P67A-C43
    i5-2500K
    2 x 4 GB Corsair DDR3 1333MHz 9-9-9-24 1.50V  Memory
    Ultra V Series 500Watt ATX Power Supply
    64GB Kingston SSD
    1 TB HDD (not installed yet)
    SATA DVD-ROM
    XFX Radeon HD 6850 Black Edition
    Can you confirm this and if this is your system, can you please advise what the amp rating is of the 12V rail on that PSU ?  And do add a signature to your profile containing your system specs. Makes life easier for everyone.
    What happens if you physically disconnect the SSD and only connect the HDD ?

  • Windows 8.1 BSOD RDR_FILE_SYSTEM 0x27

    A customer of ours is experiencing random BSODs, it seems to have something to do with avp.exe or rdbss.sys.
    I analyzed the MEMORY.DMP file with the Windows Debugging Tools, see below, can anyone tell me what is causing the BSODs? I already ran sfc /scannow, but it didn't find any problems.
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff801`6847f000 PsLoadedModuleList = 0xfffff801`687492d0
    Debug session time: Mon Jul 28 15:09:04.104 2014 (UTC + 2:00)
    System Uptime: 13 days 3:53:35.466
    Loading Kernel Symbols
    ....................................................Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    ...Page baa75 not present in the dump file. Type ".hh dbgerr004" for details
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7e76f018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 27, {baad0073, ffffd001a9df6b18, ffffd001a9df6320, fffff801f9474ed0}
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : rdbss.sys ( rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60 )
    Followup: MachineOwner
    1: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    RDR_FILE_SYSTEM (27)
        If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the
        exception record and context record. Do a .cxr on the 3rd parameter and then kb to
        obtain a more informative stack trace.
        The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined
        as follows:
         RDBSS_BUG_CHECK_CACHESUP  = 0xca550000,
         RDBSS_BUG_CHECK_CLEANUP   = 0xc1ee0000,
         RDBSS_BUG_CHECK_CLOSE     = 0xc10e0000,
         RDBSS_BUG_CHECK_NTEXCEPT  = 0xbaad0000,
    Arguments:
    Arg1: 00000000baad0073
    Arg2: ffffd001a9df6b18
    Arg3: ffffd001a9df6320
    Arg4: fffff801f9474ed0
    Debugging Details:
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    EXCEPTION_RECORD:  ffffd001a9df6b18 -- (.exr 0xffffd001a9df6b18)
    ExceptionAddress: fffff801f9474ed0 (rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x0000000000000060)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000130
    Attempt to read from address 0000000000000130
    CONTEXT:  ffffd001a9df6320 -- (.cxr 0xffffd001a9df6320;r)
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
     r8=ffffe00161e52080  r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Last set context:
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
     r8=ffffe00161e52080  r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Resetting default scope
    PROCESS_NAME:  avp.exe
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000130
    READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     0000000000000130
    FOLLOWUP_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi]
    FAULTING_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e          mov     rbx,qword ptr [rsi]
    BUGCHECK_STR:  0x27
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff801f94655c2 to fffff801f9474ed0
    STACK_TEXT: 
    ffffd001`a9df6d50 fffff801`f94655c2 : 00000000`00000000 ffffc000`5b033a90 ffffe001`5e2873f0 fffff801`f9453010 : rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60
    ffffd001`a9df6dc0 fffff801`f94649f0 : ffffe001`5e287300 ffffe001`62344c00 fffff801`f9453010 ffffd001`a9df6e00 : rdbss!RxCollapseOrCreateSrvOpen+0x3f2
    ffffd001`a9df6e50 fffff801`f946407d : ffffe001`5e2873f0 00000000`00000004 ffffe001`5e2873f0 ffffe001`618fa590 : rdbss!RxCreateFromNetRoot+0x1b0
    ffffd001`a9df6f80 fffff801`f942ed9e : 01cfaa65`1b27c42d ffffe001`62344c00 ffffe001`62344d18 00000000`00000000 : rdbss!RxCommonCreate+0x1bd
    ffffd001`a9df7030 fffff801`f945f7df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : rdbss!RxFsdCommonDispatch+0x56e
    ffffd001`a9df71a0 fffff801`fa3bf1b3 : 00000000`00000000 ffffe001`62344c01 ffffe001`62344c00 fffff801`f88bf010 : rdbss!RxFsdDispatch+0xcf
    ffffd001`a9df7210 fffff801`f88c4682 : ffffe001`61e06300 ffffe001`62344c00 ffffc000`4eb0c140 00000000`00000000 : mrxsmb!MRxSmbFsdDispatch+0x83
    ffffd001`a9df7250 fffff801`f88c2c07 : ffffc000`4eb0c140 00000000`00000000 fffff801`f88bf010 ffffe001`6248f630 : mup!MupiCallUncProvider+0xc2
    ffffd001`a9df72c0 fffff801`f8344cf8 : ffffe001`618fa590 00000000`00000022 ffffe001`618fa590 ffffe001`6248f630 : mup!MupCreate+0x5f8
    ffffd001`a9df7360 fffff801`f836d341 : ffffe001`5f571010 ffffe001`62344c00 ffffe001`5e4ccad0 00000000`00000801 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x258
    ffffd001`a9df7400 fffff801`68872593 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`000007ff : fltmgr!FltpCreate+0x342
    ffffd001`a9df74b0 fffff801`688784f8 : ffffc000`4dc14188 ffffc000`4dc14188 ffffc000`4eb0f8d0 ffffe001`5da4a320 : nt!IopParseDevice+0x7b3
    ffffd001`a9df76b0 fffff801`68875e53 : 00000000`00000000 ffffd001`a9df78a8 00000000`00000040 ffffe001`5ce39840 : nt!ObpLookupObjectName+0x6d8
    ffffd001`a9df7830 fffff801`688449a2 : 00000000`00000001 ffffe001`61e3f838 00000000`0bb5e830 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
    ffffd001`a9df7960 fffff801`68844628 : 00000000`0bb5e818 00000000`80100080 00000000`0bb5f0d0 fffff801`6887c1c6 : nt!IopCreateFile+0x372
    ffffd001`a9df7a00 fffff801`685de7b3 : ffffe001`60341de8 ffffe001`61e52080 fffff6fb`7dbed000 fffff6fb`7da00000 : nt!NtCreateFile+0x78
    ffffd001`a9df7a90 00007ffc`dfebb25a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0bb5e7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`dfebb25a
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: rdbss
    IMAGE_NAME:  rdbss.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  52affb72
    STACK_COMMAND:  .cxr 0xffffd001a9df6320 ; kb
    BUCKET_ID_FUNC_OFFSET:  60
    FAILURE_BUCKET_ID:  0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    BUCKET_ID:  0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x27_rdbss!rdbssstatisticsentryarrayfindorcreateprimaryinstance
    FAILURE_ID_HASH:  {153fa92a-562a-8bd4-d56c-4e02c62b008f}
    Followup: MachineOwner

    VinnieL
    Upon double checking it was not the correct DMP file.  I am sorry about the mix up.  Given that it is a full DMP file I was not able to use the tools I use to double check.  Lets try this again and you can confirm this is the correct DMP but
    the headers you got and in the snip below
    This was Related to rdbss.sys Redirected Drive Buffering SubSystem Driver from Microsoft Corporation and this makes more sense.  Given that it is an OS driver your first step should be to run a system file check to repair it.  If SFC is unable
    to repair it you should run DISM the instructions for which are at the end of the wiki. 
    Again I am sorry for the mix up.  With over 100 DMPS a day sometimes an old DMP isnt deleted.
    Please run a system file check (SFC)
    All instructions are in our Wiki article below...
    Should you have any questions please ask us.
    System file check (SFC) Scan and Repair System Files
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff801`6847f000 PsLoadedModuleList = 0xfffff801`687492d0
    Debug session time: Mon Jul 28 09:09:04.104 2014 (UTC - 4:00)
    System Uptime: 13 days 3:53:35.466
    Loading Kernel Symbols
    ....................................................Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    ...Page baa75 not present in the dump file. Type ".hh dbgerr004" for details
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7e76f018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 27, {baad0073, ffffd001a9df6b18, ffffd001a9df6320, fffff801f9474ed0}
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : rdbss.sys ( rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60 )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    RDR_FILE_SYSTEM (27)
    If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the
    exception record and context record. Do a .cxr on the 3rd parameter and then kb to
    obtain a more informative stack trace.
    The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined
    as follows:
    RDBSS_BUG_CHECK_CACHESUP = 0xca550000,
    RDBSS_BUG_CHECK_CLEANUP = 0xc1ee0000,
    RDBSS_BUG_CHECK_CLOSE = 0xc10e0000,
    RDBSS_BUG_CHECK_NTEXCEPT = 0xbaad0000,
    Arguments:
    Arg1: 00000000baad0073
    Arg2: ffffd001a9df6b18
    Arg3: ffffd001a9df6320
    Arg4: fffff801f9474ed0
    Debugging Details:
    Page 6a3b not present in the dump file. Type ".hh dbgerr004" for details
    EXCEPTION_RECORD: ffffd001a9df6b18 -- (.exr 0xffffd001a9df6b18)
    ExceptionAddress: fffff801f9474ed0 (rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x0000000000000060)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000130
    Attempt to read from address 0000000000000130
    CONTEXT: ffffd001a9df6320 -- (.cxr 0xffffd001a9df6320;r)
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
    r8=ffffe00161e52080 r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Last set context:
    rax=fffff801f9453010 rbx=0000000000000000 rcx=fffff801f9453800
    rdx=0000000000000000 rsi=0000000000000130 rdi=0000000000000000
    rip=fffff801f9474ed0 rsp=ffffd001a9df6d50 rbp=ffffc0005e647280
    r8=ffffe00161e52080 r9=ffffd001a9df7630 r10=fffff780000003b0
    r11=fffff78000000008 r12=ffffd001a9df7630 r13=ffffe00161e52080
    r14=ffffc0004e87a010 r15=ffffe0015e9ab860
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60:
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi] ds:002b:00000000`00000130=????????????????
    Resetting default scope
    PROCESS_NAME: avp.exe
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 0000000000000130
    READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    0000000000000130
    FOLLOWUP_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi]
    FAULTING_IP:
    rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    fffff801`f9474ed0 488b1e mov rbx,qword ptr [rsi]
    BUGCHECK_STR: 0x27
    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER: from fffff801f94655c2 to fffff801f9474ed0
    STACK_TEXT:
    ffffd001`a9df6d50 fffff801`f94655c2 : 00000000`00000000 ffffc000`5b033a90 ffffe001`5e2873f0 fffff801`f9453010 : rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x60
    ffffd001`a9df6dc0 fffff801`f94649f0 : ffffe001`5e287300 ffffe001`62344c00 fffff801`f9453010 ffffd001`a9df6e00 : rdbss!RxCollapseOrCreateSrvOpen+0x3f2
    ffffd001`a9df6e50 fffff801`f946407d : ffffe001`5e2873f0 00000000`00000004 ffffe001`5e2873f0 ffffe001`618fa590 : rdbss!RxCreateFromNetRoot+0x1b0
    ffffd001`a9df6f80 fffff801`f942ed9e : 01cfaa65`1b27c42d ffffe001`62344c00 ffffe001`62344d18 00000000`00000000 : rdbss!RxCommonCreate+0x1bd
    ffffd001`a9df7030 fffff801`f945f7df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : rdbss!RxFsdCommonDispatch+0x56e
    ffffd001`a9df71a0 fffff801`fa3bf1b3 : 00000000`00000000 ffffe001`62344c01 ffffe001`62344c00 fffff801`f88bf010 : rdbss!RxFsdDispatch+0xcf
    ffffd001`a9df7210 fffff801`f88c4682 : ffffe001`61e06300 ffffe001`62344c00 ffffc000`4eb0c140 00000000`00000000 : mrxsmb!MRxSmbFsdDispatch+0x83
    ffffd001`a9df7250 fffff801`f88c2c07 : ffffc000`4eb0c140 00000000`00000000 fffff801`f88bf010 ffffe001`6248f630 : mup!MupiCallUncProvider+0xc2
    ffffd001`a9df72c0 fffff801`f8344cf8 : ffffe001`618fa590 00000000`00000022 ffffe001`618fa590 ffffe001`6248f630 : mup!MupCreate+0x5f8
    ffffd001`a9df7360 fffff801`f836d341 : ffffe001`5f571010 ffffe001`62344c00 ffffe001`5e4ccad0 00000000`00000801 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x258
    ffffd001`a9df7400 fffff801`68872593 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`000007ff : fltmgr!FltpCreate+0x342
    ffffd001`a9df74b0 fffff801`688784f8 : ffffc000`4dc14188 ffffc000`4dc14188 ffffc000`4eb0f8d0 ffffe001`5da4a320 : nt!IopParseDevice+0x7b3
    ffffd001`a9df76b0 fffff801`68875e53 : 00000000`00000000 ffffd001`a9df78a8 00000000`00000040 ffffe001`5ce39840 : nt!ObpLookupObjectName+0x6d8
    ffffd001`a9df7830 fffff801`688449a2 : 00000000`00000001 ffffe001`61e3f838 00000000`0bb5e830 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
    ffffd001`a9df7960 fffff801`68844628 : 00000000`0bb5e818 00000000`80100080 00000000`0bb5f0d0 fffff801`6887c1c6 : nt!IopCreateFile+0x372
    ffffd001`a9df7a00 fffff801`685de7b3 : ffffe001`60341de8 ffffe001`61e52080 fffff6fb`7dbed000 fffff6fb`7da00000 : nt!NtCreateFile+0x78
    ffffd001`a9df7a90 00007ffc`dfebb25a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0bb5e7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`dfebb25a
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+60
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: rdbss
    IMAGE_NAME: rdbss.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 52affb72
    STACK_COMMAND: .cxr 0xffffd001a9df6320 ; kb
    BUCKET_ID_FUNC_OFFSET: 60
    FAILURE_BUCKET_ID: 0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    BUCKET_ID: 0x27_rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x27_rdbss!rdbssstatisticsentryarrayfindorcreateprimaryinstance
    FAILURE_ID_HASH: {153fa92a-562a-8bd4-d56c-4e02c62b008f}
    Followup: MachineOwner
    1: kd> lmvm rdbss
    start end module name
    fffff801`f942d000 fffff801`f949d000 rdbss (pdb symbols) c:\symbols\rdbss.pdb\79F4162F81A5409285603135A1E6DB592\rdbss.pdb
    Loaded symbol image file: rdbss.sys
    Image path: \SystemRoot\system32\DRIVERS\rdbss.sys
    Image name: rdbss.sys
    Timestamp: Tue Dec 17 02:21:22 2013 (52AFFB72)
    CheckSum: 0006BFA7
    ImageSize: 00070000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    1: kd> .exr 0xffffd001a9df6b18
    ExceptionAddress: fffff801f9474ed0 (rdbss!RdbssStatisticsEntryArrayFindOrCreatePrimaryInstance+0x0000000000000060)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000130
    Attempt to read from address 0000000000000130
    Wanikiya and Dyami--Team Zigzag

Maybe you are looking for