locked
VIDEO_MEMORY_MANAGEMENT_INTERNAL and NTFS_FILE_SYSTEM BSODs RRS feed

  • Question

  • Hello!

    I've been getting intermittent BSODs and I was hoping someone could help me identify why. I just recently ran Memtest86+ on each of my RAM modules (separately), both showed no errors on multiple passes. (I would hope so, since I just bought these sticks a few weeks ago).

    Recently, I've gotten VIDEO_MEMORY_MANAGEMENT_INTERNAL and NTFS_FILE_SYSTEM BSODs. Here is my MEMORY.dmp and two most recent minidump files:

    https://dl.dropboxusercontent.com/u/5772230/bsod2/MEMORYDMP_minidumps.zip

    And a screenshot of more of my previous crashes (via WhoCrashed):

    https://dl.dropboxusercontent.com/u/5772230/bsod2/whocrashed.png

    Just a note, but I fixed the SYSTEM_SERVICE_EXCEPTION crash by uninstalling a bad third-party driver (thread found here: http://social.technet.microsoft.com/Forums/windows/en-US/8d8f7cff-596b-4048-ba89-8ad0354b261c/systemserviceexception-bsod-after-waking-up-from-sleep?forum=w7itproperf)

    Let me know what I could do to aid the troubleshooting process. Thanks!

    Fil

    Saturday, August 9, 2014 5:04 PM

Answers

  • BSOD caused by driver : Ntfs.sys and watchdog.sys

    Both of them are fixed by Windows updates.

    Are all updates installed?


    Arnav Sharma | http://arnavsharma.net/ 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.

    • Marked as answer by arnavsharma Wednesday, June 7, 2017 1:28 AM
    Saturday, August 9, 2014 5:12 PM
  • Fmpeyton

    Is this the same machine in your other thread?  I notice the joystick driver is still installed and driver verifier was not enabled.  You need to enable verifier and remove the joystick driver.

    http://social.technet.microsoft.com/Forums/windows/en-US/8d8f7cff-596b-4048-ba89-8ad0354b261c/systemserviceexception-bsod-after-waking-up-from-sleep?forum=w7itproperf#4b816c72-bcc2-4dcc-b281-665623e9973c


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by arnavsharma Wednesday, June 7, 2017 1:28 AM
    Saturday, August 9, 2014 5:34 PM
  • Memory/minidump files: https://dl.dropboxusercontent.com/u/5772230/bsod4/8-12-14.zip

    Any ideas why?


    Fmpeyton

    Threads merged same topic.  This is the third thread you have started on the same topic.  Please dont start additional ones on the same topic.


    Wanikiya and Dyami--Team Zigzag


    • Edited by ZigZag3143x Tuesday, August 12, 2014 5:33 PM
    • Marked as answer by arnavsharma Wednesday, June 7, 2017 1:28 AM
    Tuesday, August 12, 2014 5:32 PM

All replies

  • BSOD caused by driver : Ntfs.sys and watchdog.sys

    Both of them are fixed by Windows updates.

    Are all updates installed?


    Arnav Sharma | http://arnavsharma.net/ 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.

    • Marked as answer by arnavsharma Wednesday, June 7, 2017 1:28 AM
    Saturday, August 9, 2014 5:12 PM
  • Fmpeyton

    Is this the same machine in your other thread?  I notice the joystick driver is still installed and driver verifier was not enabled.  You need to enable verifier and remove the joystick driver.

    http://social.technet.microsoft.com/Forums/windows/en-US/8d8f7cff-596b-4048-ba89-8ad0354b261c/systemserviceexception-bsod-after-waking-up-from-sleep?forum=w7itproperf#4b816c72-bcc2-4dcc-b281-665623e9973c


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by arnavsharma Wednesday, June 7, 2017 1:28 AM
    Saturday, August 9, 2014 5:34 PM
  • Hi ZigZag3143x! Yeah same machine. I thought I removed the driver. Strange...

    After removing the driver, do I need to keep driver verifier enabled forever? I thought it was more of a troubleshooting program.

    Thanks for your help!

    Saturday, August 9, 2014 6:37 PM
  • arnavsharma - Yes, the machine is up to date on all windows updates.
    Saturday, August 9, 2014 6:37 PM
  • FP

    It is a trouble shooting program but you are still having trouble.  Probably a better idea now to start duplicate thread on the same topic and machine.

    Not sure if you ran Memtest, or if you ran a system file check but you should

    *

    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.


    Wanikiya and Dyami--Team Zigzag

    Saturday, August 9, 2014 7:35 PM
  • ZigZag3143x - I removed the program entirely. Since it was just a piece of a larger program, it kept reinstalling itself.

    I started a new thread because I thought this was a new issue and not related to the joystick re-instantiating itself. I'll see if removing the parent program fixes the issue.

    Sunday, August 10, 2014 5:38 AM
  • ZigZag3143x - I've removed the parent program, but I am still getting a BSOD after waking my computer. Here's my latest MEMORY.DMP: https://dl.dropboxusercontent.com/u/5772230/bsod3/MEMORY.zip

    I did Memtest86+ and here are my results:

    Module 1 (after a few passes of memtest86+): https://dl.dropboxusercontent.com/u/5772230/bsod3/module1.jpg

    Module 2 (after a few passes of memtest86+): https://dl.dropboxusercontent.com/u/5772230/bsod3/module2.jpg

    And here are some screenshots of my BIOS settings:

    Memory Settings: https://dl.dropboxusercontent.com/u/5772230/bsod3/bios_memory.jpg

    Voltage Settings: https://dl.dropboxusercontent.com/u/5772230/bsod3/bios_voltage.jpg

    One note to add: I had to change the memory settings in my BIOS because my mobo reads my 1866 memory at 1600. I followed the G-Skill guide here: http://www.gskill.us/forum/showthread.php?t=11742

    I will try running SFC and then enabling Driver Verifier.

    Thanks!

    Fil

    Sunday, August 10, 2014 8:54 PM
  • I ran sfc /verifyonly and got: https://dl.dropboxusercontent.com/u/5772230/bsod3/sfc_verifyonly.png

    Here is the CBS.log: https://dl.dropboxusercontent.com/u/5772230/bsod3/CBS_afterverifyonly.log

    I then ran sfc /scannow and I got: https://dl.dropboxusercontent.com/u/5772230/bsod3/sfc_scannow-2x.png

    CBS.log after running /scannow twice: https://dl.dropboxusercontent.com/u/5772230/bsod3/CBS_after-scannow-2x.log

    Sunday, August 10, 2014 9:14 PM
  • I just tried running sfc /scannow 5x in a row and I still get "Windows Resource Protection found corrupt files but was unable to fix some of them."

    Going to try and run a repair install.

    Sunday, August 10, 2014 9:32 PM
  • Ran a Repair Install (http://www.sevenforums.com/tutorials/3413-repair-install.html) and then tried sfc /verifyonly and I am getting no errors: https://dl.dropboxusercontent.com/u/5772230/bsod3/sfc_passed.png

    We'll see if I get any more bluescreens now. I'll keep this thread posted.

    Monday, August 11, 2014 1:13 AM
  • Repair install was successful, but I got a few BSODs. I'm lacking some windows updates, so I am making my way through those before I say the BSODs are back.

    Also, I have a new thread to make sure my memory settings are correct: http://www.tomshardware.com/answers/id-2255464/correct-settings-skill-14900cl9d-8gbxl-gigabyte-990fxa-ud3-mobo.html

    My RAM was recognized at 1600 when they are rated at 1866, so I had to make some adjustments.

    Monday, August 11, 2014 6:25 PM
  • The BSODs are back. More specifically NTFS_FILE_SYSTEM:

    https://dl.dropboxusercontent.com/u/5772230/bsod4/8-12-14.zip

    Any ideas?

    Tuesday, August 12, 2014 4:50 PM
  • Memory/minidump files: https://dl.dropboxusercontent.com/u/5772230/bsod4/8-12-14.zip

    Any ideas why?


    • Edited by fmpeyton Tuesday, August 12, 2014 4:58 PM
    • Merged by ZigZag3143x Tuesday, August 12, 2014 5:31 PM Duplicate thread
    Tuesday, August 12, 2014 4:58 PM
  • Memory/minidump files: https://dl.dropboxusercontent.com/u/5772230/bsod4/8-12-14.zip

    Any ideas why?


    Fmpeyton

    Threads merged same topic.  This is the third thread you have started on the same topic.  Please dont start additional ones on the same topic.


    Wanikiya and Dyami--Team Zigzag


    • Edited by ZigZag3143x Tuesday, August 12, 2014 5:33 PM
    • Marked as answer by arnavsharma Wednesday, June 7, 2017 1:28 AM
    Tuesday, August 12, 2014 5:32 PM
  • ZigZag3143x - Sorry about that.  I had thought since they were all separate BSODs that they would warrant separate threads.

    Let me know what you think about my currect dump files. Thank you!!

    Tuesday, August 12, 2014 5:43 PM
  • Memory/minidump files: https://dl.dropboxusercontent.com/u/5772230/bsod4/8-12-14.zip

    Any ideas why?


    FP

    This rar file is empty.  Please try it again


    Wanikiya and Dyami--Team Zigzag

    Tuesday, August 12, 2014 6:09 PM
  • ZigZag3143x - Strange... It is downloading for me. Might've not finished uploading from earlier. Can you try again?

    https://dl.dropboxusercontent.com/u/5772230/bsod4/8-12-14.zip

    Tuesday, August 12, 2014 6:49 PM
  • FP

    Works fine now.  Have you run verifier since you dod the re-install?  Are you overclocking the CPU?  where did you get the win 7 image from?

    If this issue has persisted across a clean install (it was a clean install right?) it has to be either hardware, malware or a corrupt OS image.

    lets run some hardware stress tests.  Furmark for the graphics and Prime 95 for CPU.  You have run memtest for how many passes?

    Try this free video stress test:  http://www.ozone3d.net/benchmarks/fur/
    FurMark Setup:

    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first)
    - Click "Quit" to exit

    Try this free stress test:  http://www.mersenne.org/freesoft/

    Prime95 Setup;
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
    The Test selection box and the stress.txt file describes what components that the program stresses.

    For malware lets run a malwarebytes scan

    Please download the free version of Malwarebytes.
    Update it immediately.
    Do a full system scan
    Let us know the results at the end.

    http://www.malwarebytes.org/products


    Wanikiya and Dyami--Team Zigzag

    Tuesday, August 12, 2014 7:09 PM
  • ZigZag3143x - 

    1) I will run the verifier now.
    2) I am not overclocking my CPU
    3) I bought my Win7 (OEM) image from Newegg.
    4) I have run hardware stress tests before:
    - http://www.3dmark.com/3dm/3568181
    - http://www.3dmark.com/pcm7/843826
    5) I ran memtest86+ for ~3 passes each module:
    - https://dl.dropboxusercontent.com/u/5772230/bsod3/module1.jpg
    - https://dl.dropboxusercontent.com/u/5772230/bsod3/module2.jpg
    6) I will try running Prime95 when I have more time (unless 3dmark was enough)
    7) A scan of Malwarebytes returned:
    - https://dl.dropboxusercontent.com/u/5772230/bsod4/malwarebytes-scan.png
    - https://dl.dropboxusercontent.com/u/5772230/bsod4/malwarebytes-scan.txt
    Thursday, August 14, 2014 3:22 AM
  • 4-You may get more specific results if you stress the hardware using prime 95 and furmark, rather than 3D mark

    5-Memtest needs at east 8 passes

    6-Malwarbytes looks fine.

    Fingers crossed on verifier.  You can also change the drivers being verified to "all" to force the issue but make sure you have a restore point before you do just in case.


    Wanikiya and Dyami--Team Zigzag

    Thursday, August 14, 2014 3:27 AM
  • 4-You may get more specific results if you stress the hardware using prime 95 and furmark, rather than 3D mark

    5-Memtest needs at east 8 passes

    6-Malwarbytes looks fine.

    Fingers crossed on verifier.  You can also change the drivers being verified to "all" to force the issue but make sure you have a restore point before you do just in case.


    Wanikiya and Dyami--Team Zigzag

    Just ran verifier and had the computer go to sleep and woke it up (this is when I see the BSODs). I was able to get blue screens a little while after the machine woke up (with Verifier on). Here are the latest three dumps: https://dl.dropboxusercontent.com/u/5772230/bsod4/8-14-14.zip
    Friday, August 15, 2014 1:11 AM
  • ZigZag3143x - Any ideas on what's going wrong here?
    Tuesday, August 19, 2014 6:16 AM
  • FP

    Still related to video driver.  SInce you have the most current have you tried rolling it back 6 months or more?

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\081414-23805-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`03650890
    Debug session time: Thu Aug 14 21:02:21.511 2014 (UTC - 4:00)
    System Uptime: 0 days 9:15:40.588
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C1, {fffff98018dcef00, fffff98018dce2d6, a54108, 32}
    
    *** 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+dab31 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98018dcef00, address trying to free
    Arg2: fffff98018dce2d6, address where one bit is corrupted
    Arg3: 0000000000a54108, (reserved)
    Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC1_32
    
    SPECIAL_POOL_CORRUPTION_TYPE:  32
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80003511cb3 to fffff80003482bc0
    
    STACK_TEXT:  
    fffff880`0847c8e8 fffff800`03511cb3 : 00000000`000000c1 fffff980`18dcef00 fffff980`18dce2d6 00000000`00a54108 : nt!KeBugCheckEx
    fffff880`0847c8f0 fffff800`0358a903 : 00000000`00000000 00000000`00000001 00000000`ffffffff fffffa80`0ac80298 : nt!MiCheckSpecialPoolSlop+0x83
    fffff880`0847c930 fffff800`035b593b : fffff800`0340d000 00000000`4d52564e 00000000`00040d10 fffff980`18dcef00 : nt!MmFreeSpecialPool+0x1d3
    fffff880`0847ca70 fffff880`111a0b31 : 00000000`00000000 fffff880`0847cc50 00000000`c1d00211 fffffa80`0ac80298 : nt!ExDeferredFreePool+0xf33
    fffff880`0847cb20 00000000`00000000 : fffff880`0847cc50 00000000`c1d00211 fffffa80`0ac80298 fffff980`18dcef00 : nvlddmkm+0xdab31
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+dab31
    fffff880`111a0b31 ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nvlddmkm+dab31
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a
    
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nvlddmkm+dab31
    
    BUCKET_ID:  X64_0xC1_32_VRF_nvlddmkm+dab31
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xc1_32_vrf_nvlddmkm+dab31
    
    FAILURE_ID_HASH:  {ba39757c-bcbf-aec6-841a-8215dd197da4}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Tuesday, August 19, 2014 11:56 AM
  • FP

    Still related to video driver.  SInce you have the most current have you tried rolling it back 6 months or more?

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\081414-23805-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`03650890
    Debug session time: Thu Aug 14 21:02:21.511 2014 (UTC - 4:00)
    System Uptime: 0 days 9:15:40.588
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C1, {fffff98018dcef00, fffff98018dce2d6, a54108, 32}
    
    *** 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+dab31 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98018dcef00, address trying to free
    Arg2: fffff98018dce2d6, address where one bit is corrupted
    Arg3: 0000000000a54108, (reserved)
    Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC1_32
    
    SPECIAL_POOL_CORRUPTION_TYPE:  32
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80003511cb3 to fffff80003482bc0
    
    STACK_TEXT:  
    fffff880`0847c8e8 fffff800`03511cb3 : 00000000`000000c1 fffff980`18dcef00 fffff980`18dce2d6 00000000`00a54108 : nt!KeBugCheckEx
    fffff880`0847c8f0 fffff800`0358a903 : 00000000`00000000 00000000`00000001 00000000`ffffffff fffffa80`0ac80298 : nt!MiCheckSpecialPoolSlop+0x83
    fffff880`0847c930 fffff800`035b593b : fffff800`0340d000 00000000`4d52564e 00000000`00040d10 fffff980`18dcef00 : nt!MmFreeSpecialPool+0x1d3
    fffff880`0847ca70 fffff880`111a0b31 : 00000000`00000000 fffff880`0847cc50 00000000`c1d00211 fffffa80`0ac80298 : nt!ExDeferredFreePool+0xf33
    fffff880`0847cb20 00000000`00000000 : fffff880`0847cc50 00000000`c1d00211 fffffa80`0ac80298 fffff980`18dcef00 : nvlddmkm+0xdab31
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+dab31
    fffff880`111a0b31 ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nvlddmkm+dab31
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a
    
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nvlddmkm+dab31
    
    BUCKET_ID:  X64_0xC1_32_VRF_nvlddmkm+dab31
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xc1_32_vrf_nvlddmkm+dab31
    
    FAILURE_ID_HASH:  {ba39757c-bcbf-aec6-841a-8215dd197da4}
    
    Followup: MachineOwner
    ---------
    


    Wanikiya and Dyami--Team Zigzag

    Hi ZigZag,

    This computer (OS install) is no older than 2 months old. I'm going to roll back to a previous Restore Point, because my Firewall isn't turning on now.

    Friday, August 22, 2014 5:56 AM
  • Fmpeyton

    Good luck and let us know if you need help


    Wanikiya and Dyami--Team Zigzag

    Friday, August 22, 2014 12:25 PM
  • NVIDIA has a new driver out, might be of some help for the crashes

    likely a fresh install of windows is the only way to clean up this mess


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Friday, August 22, 2014 1:14 PM
  • Fmpeyton

    Good luck and let us know if you need help


    Wanikiya and Dyami--Team Zigzag

    Still no dice. After going back to an old restore point, I was still getting the BSODs.

    Since I'd tried practically everything, I tried a clean install. But I got another BSOD. The BSOD always comes back after waking the computer from sleep. Could you check out my memory dump and see if it was due to the video card again? https://dl.dropboxusercontent.com/u/5772230/bsod4/8-22-14.zip

    After this crash, I rolled back the nvidia driver, so we'll see if that helps. I might just need a new video card.

    Saturday, August 23, 2014 4:57 AM
  • FP

    Both the memory.dmp and the minidump are related to memory corruption (pool corruption) not the video driver.  Since this is happening after a clen install I would run memtest to test the memory for at least 8 passes (even if you have run it before) and I would enable driver verifier.

    Did you install anything NOT on the install dvd (image) besides the video driver like Malware, or anything else?

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run these tests to verify your memory and find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    Since it is more likely to be a driver please run verifier first.
    1-Driver verifier (for complete directions see our wiki here)

    If verifier does not find the issue we can move on to this.
    2-Memtest. (You can read more about running memtest here)

    If you cannot boot after enabling verifier reboot into safe mode
    In Vista & win 7 (F8)

    Co-Authored by  JMH3143
    .


    Wanikiya and Dyami--Team Zigzag

    Saturday, August 23, 2014 12:00 PM
  • I really hope its not the memory. I did the three passes on each module before and it showed clean. When I get some time I'll set them to run for 8 passes each.

    Here's my latest dump after running verifier: https://dl.dropboxusercontent.com/u/5772230/bsod4/8-23-14.zip

    Sunday, August 24, 2014 2:23 AM
  • FP

    Three passes does not stress the memory enough so the results are useless.  Memory corruption.  You can reduce your upload time by changing the settings in your system control panel to kernel dmp instructions are in the wiki


    Wanikiya and Dyami--Team Zigzag

    Sunday, August 24, 2014 2:46 AM
  • I really hope its not the memory. I did the three passes on each module before and it showed clean. When I get some time I'll set them to run for 8 passes each.

    Here's my latest dump after running verifier: https://dl.dropboxusercontent.com/u/5772230/bsod4/8-23-14.zip

    It looks like you are going to have to swap parts to figure out what is at fault

    this is why I like amd, fewer sockets and nonsense, my cpu works on several models of motherboard


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, August 24, 2014 1:53 PM
  • I ran Memtest86+ on each module to see if there was anything wrong with my modules. My first stick ran 8 passes without error:

    https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140901_182529.jpg

    I ran Memtest86+ on my other module too and it passed 8 passed too:

    https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140902_080050.jpg

    One thing I noticed on the second module is the speed/timings are not what they should be. If you look at the above screenshot, you'll notice the speed is DDR3-784 and timings are 4-5-5-15 @ 64-bit. On the first module, the speed/timings are correct.

    Seeing this, I tried moving the second module into another memory slot, but the speed/timings still read the same. The strange part was on my BIOS, the speed/timings of the second module read correctly:

    https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140902_081659.jpg

    Also, after testing the 8 passes on the second module, I started another Memtest86+ on the second module, which resulted in many errors (~46 errors) within a span of a minute. This seems to happen randomly with this module.
    Tuesday, September 2, 2014 7:26 PM
  • FP

    Looking like RAM or mobo slot.  I would use only the known good stick and try each mobo slot.


    Wanikiya and Dyami--Team Zigzag

    Tuesday, September 2, 2014 7:35 PM
  • I ran Memtest86+ on each module to see if there was anything wrong with my modules. My first stick ran 8 passes without error:

    https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140901_182529.jpg

    I ran Memtest86+ on my other module too and it passed 8 passed too:

    https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140902_080050.jpg

    One thing I noticed on the second module is the speed/timings are not what they should be. If you look at the above screenshot, you'll notice the speed is DDR3-784 and timings are 4-5-5-15 @ 64-bit. On the first module, the speed/timings are correct.

    Seeing this, I tried moving the second module into another memory slot, but the speed/timings still read the same. The strange part was on my BIOS, the speed/timings of the second module read correctly:

    https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140902_081659.jpg

    Also, after testing the 8 passes on the second module, I started another Memtest86+ on the second module, which resulted in many errors (~46 errors) within a span of a minute. This seems to happen randomly with this module.

    If you are using RAM with dissimilar timings then it may lead to problems, DDR2 and DDR3 are designed to work in pairs per channel.

    Slots are also sensitive to damage as well. Its possible that you may need to get a new motherboard.


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Tuesday, September 2, 2014 10:06 PM
  • ZigZag-

    I did some swapping of modules and slots. Here's what I've found:

    When I would test my memory on slots 0-1, Memtest86+ would read my memory's speeds/timings correctly: 1866 9-10-9-28. But when I tested the same modules in slots 2-3, I would get half of that: DDR3-784 4-5-5-15.

    Slots 0-1: https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140901_182529.jpg

    Slots 2-3: https://dl.dropboxusercontent.com/u/5772230/bad_module/IMG_20140902_080050.jpg

    I'm not sure why that's happening, but I do see that CPU-Z is reading my modules correctly, no matter what position they are in.

    I have since upped the voltage for my DRAM and CPU VCORE in my BIOS, to see if that helps.

    I did see another similar case as mine: http://www.tomshardware.com/forum/id-1926857/memory-slots-speeds.html (He has the same mobo and CPU as me)

    I've also written my issues to Gigabyte (mobo) and G Skill (RAM).

    I'm running out of ideas here. It seems to be the memory, but I can't figure out exactly what. My last thing I'm going to try is placing both modules in positions 0 and 1, since I'm getting full speed reads from them. Maybe that will help?

    Wednesday, September 3, 2014 6:30 AM
  • Also, I just tried my modules in slots 0-1 and upon waking from sleep, it seemed fine for about 10 minutes (just like before every other BSOD), then it crashed: https://dl.dropboxusercontent.com/u/5772230/bad_module/9-3-14.zip

    I have no idea what to do at this point. There's no clues pointing to any clear solution here.

    Wednesday, September 3, 2014 3:28 PM
  • FP

    Unsure exactly where you are.  This has been going on for almost a month.  Did you memtest each mobo slot with known good ram?  results?  did you individually test each stick in a known good mobo slot.  Results?

    The newest crash was not verified and I suspect irrelevant.


    Wanikiya and Dyami--Team Zigzag

    Wednesday, September 3, 2014 10:11 PM