BSOD, help would be appreciated.

#1
Hey guys, just built my first computer and getting BSOD frequently. Predominantly it has been the 'MEMORY_MANAGMENT' error. But there has been a few different ones.
Any help would be greatly appreciated :)
 


Attachments

usasma

Fantastic Member
Microsoft Community Contributor
#2
Only 95 updates since SP1 - most systems have 130 to 140. Please visit Windows Update and get all available updates.

You have 3 hard drives - what is the make/model/wattage of your Power Supply? How old is it?

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
Gigabyte EasyTune6 and EasySaver are known to cause BSOD's. Please uninstall them.

If overclocking, please stop while we're troubleshooting. Feel free to resume the overclock once the BSOD's have stopped.

Apple Charger (Gigabyte On/Off) has been known to cause BSOD's. Uninstall it to test. If you need it back, feel free to reinstall it after the BSOD's have stopped.

Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Sun Nov  4 07:09:50.293 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110412-22214-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:32:53.136[/B]
BugCheck Code: [B]BugCheck 24, {1904fb, fffff8800394d5f8, fffff8800394ce50, fffff8800182cedb}[/B]
Probably caused by :[B]Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+2b )[/B]
BugCheck Info: [B]NTFS_FILE_SYSTEM (24)[/B]
Arguments: 
Arg1: 00000000001904fb
Arg2: fffff8800394d5f8
Arg3: fffff8800394ce50
Arg4: fffff8800182cedb
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID: [B]X64_0x24_Ntfs!NtfsUninitializeNtfsMcb+2b[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov  4 06:35:47.587 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110412-22183-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 4:46:32.430[/B]
BugCheck Code: [B]BugCheck 1E, {ffffffffc0000005, fffff8000f2cf427, 0, ffffffffffffffff}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KeRemoveQueueEx+177 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000f2cf427, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]dwm.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!KeRemoveQueueEx+177[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov  3 23:03:16.841 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110412-22620-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:21:49.685[/B]
BugCheck Code: [B]BugCheck 1A, {41284, 12a6e001, 6e, fffff70001080000}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000012a6e001
Arg3: 000000000000006e
Arg4: fffff70001080000
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]firefox.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov  3 09:40:49.279 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110412-22682-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:12:03.184[/B]
*** WARNING: Unable to verify timestamp for viahduaa.sys
*** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys
BugCheck Code: [B]BugCheck 1000007E, {ffffffffc0000005, fffff880096104ce, fffff880009be6c8, fffff880009bdf20}[/B]
Probably caused by :[B]viahduaa.sys ( viahduaa+1c14ce )[/B]
BugCheck Info: [B]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880096104ce, The address that the exception occurred at
Arg3: fffff880009be6c8, Exception Record Address
Arg4: fffff880009bdf20, Context Record Address
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID: [B]X64_0x7E_viahduaa+1c14ce[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov  3 01:37:12.868 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110312-22604-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:39:55.711[/B]
BugCheck Code: [B]BugCheck 1A, {41790, fffffa8008db7000, ffff, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8008db7000
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]daemonu.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  2 23:53:44.208 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110312-22230-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:06:21.052[/B]
BugCheck Code: [B]BugCheck 1A, {41790, fffffa8008f60c40, ffff, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8008f60c40
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]AdvancedSystem[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  2 23:46:48.908 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110312-22245-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:47:25.751[/B]
BugCheck Code: [B]BugCheck 1A, {41790, fffffa8008ef6ec0, ffff, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8008ef6ec0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]crashreporter.[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  2 22:26:36.496 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110312-22339-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:06:03.212[/B]
BugCheck Code: [B]BugCheck 24, {c08a5, 0, 0, 0}[/B]
Probably caused by :[B]Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )[/B]
BugCheck Info: [B]NTFS_FILE_SYSTEM (24)[/B]
Arguments: 
Arg1: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME: [B]AdvancedSystem[/B]
FAILURE_BUCKET_ID: [B]X64_0x24_Ntfs!NtfsPagingFileIo+155[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  2 22:18:47.338 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110312-24242-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:15:53.182[/B]
BugCheck Code: [B]BugCheck 1A, {41790, fffffa8008e02780, ffff, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8008e02780
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]explorer.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  2 21:34:00.137 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\110312-22464-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:10:02.980[/B]
BugCheck Code: [B]BugCheck 1A, {41790, fffffa8008e7eec0, ffff, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8008e7eec0
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]rundll32.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3503[/B]
  BIOS Version                  F11
  BIOS Release Date             05/31/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Sun Nov  4 07:09:50.293 2012 (UTC - 5:00)**************************
[COLOR=RED][B]gdrv.sys                    Thu Mar 12 23:22:29 2009 (49B9D175)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
tmtdi.sys                   Tue Jul 20 04:58:07 2010 (4C45651F)
tmevtmgr.sys                Wed Jul 21 03:31:15 2010 (4C46A243)
tmcomm.sys                  Wed Jul 21 03:31:15 2010 (4C46A243)
tmactmon.sys                Wed Jul 21 03:31:24 2010 (4C46A24C)
rikvm_38F51D56.sys          Fri Oct 29 06:52:09 2010 (4CCAA759)
L1C62x64.sys                Wed Aug  3 02:21:09 2011 (4E38E8D5)
mvxxmm.sys                  Mon Aug  8 23:05:06 2011 (4E40A3E2)
mvs91xx.sys                 Mon Aug  8 23:05:23 2011 (4E40A3F3)
[COLOR=RED][B]AppleCharger.sys            Tue Nov  1 22:46:00 2011 (4EB0AEE8)[/B][/COLOR]
iaStor.sys                  Tue Nov 29 22:39:19 2011 (4ED5A567)
a88x9oxs.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
viahduaa.sys                Tue Jan 10 06:33:14 2012 (4F0C21FA)
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
xhcdrv.sys                  Thu Jan 19 23:39:02 2012 (4F18EFE6)
ViaHub3.sys                 Thu Jan 19 23:39:13 2012 (4F18EFF1)
iusb3hub.sys                Fri Jan 27 04:35:25 2012 (4F226FDD)
iusb3xhc.sys                Fri Jan 27 04:35:28 2012 (4F226FE0)
iusb3hcs.sys                Fri Jan 27 04:37:23 2012 (4F227053)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
[COLOR=RED][B]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov  4 06:35:47.587 2012 (UTC - 5:00)**************************
ai3r86pq.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov  3 23:03:16.841 2012 (UTC - 5:00)**************************
tmwfp.sys                   Tue Jul 20 04:57:04 2010 (4C4564E0)
tmlwf.sys                   Tue Jul 20 04:57:44 2010 (4C456508)
a9103zss.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Nov  3 09:40:49.279 2012 (UTC - 5:00)**************************
am5z0x84.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  2 23:46:48.908 2012 (UTC - 5:00)**************************
[COLOR=RED][B]GVTDrv64.sys                Tue Sep  5 03:10:02 2006 (44FD22CA)[/B][/COLOR]
[COLOR=RED][B]etdrv.sys                   Thu Mar 19 22:59:06 2009 (49C3067A)[/B][/COLOR]
[/font]
http://www.carrona.org/drivers/driver.php?id=gdrv.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=tmtdi.sys
http://www.carrona.org/drivers/driver.php?id=tmevtmgr.sys
http://www.carrona.org/drivers/driver.php?id=tmcomm.sys
http://www.carrona.org/drivers/driver.php?id=tmactmon.sys
http://www.carrona.org/drivers/driver.php?id=rikvm_38F51D56.sys
http://www.carrona.org/drivers/driver.php?id=L1C62x64.sys
http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys
http://www.carrona.org/drivers/driver.php?id=mvs91xx.sys
http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys
http://www.carrona.org/drivers/driver.php?id=iaStor.sys
a88x9oxs.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
http://www.carrona.org/drivers/driver.php?id=xhcdrv.sys
http://www.carrona.org/drivers/driver.php?id=ViaHub3.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=sptd.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
ai3r86pq.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=tmwfp.sys
http://www.carrona.org/drivers/driver.php?id=tmlwf.sys
a9103zss.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
am5z0x84.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=GVTDrv64.sys
http://www.carrona.org/drivers/driver.php?id=etdrv.sys
 


#3
Thanks for getting back to me.

I have tried to update as much as I can, via both website and auto update, and I was able to get 3 updates. Maybe I'm not doing it correct though. Still got BSOD after updates.

Re: Power supply: Thermaltake 500W, model: TT-500NL1NH-1, not sure how old it is, came with the case.

A noob question (sorry): What are motherboard controllers?

Uninstalled EasyTune6, and I couldn't find/fairly sure I don't have EasySave installed. So far it has not BSOD, although I have not been able to test it for too long. But I shall keep testing it to see if I get a BSOD, if I do I will move on.

Thanks for the help so far.
 


#4
Re: EasyTune6: Scratch that, got BSOD.
 


usasma

Fantastic Member
Microsoft Community Contributor
#5
Motherboard controllers are chips on your motherboard that control the drives (hard drive, CD/DVD drive, etc)
In this case, any drivers from 2011 or earlier are probably too old for an SSD.

These are the one's that I had in mind when I made that statement:

mvxxmm.sys Mon Aug 8 23:05:06 2011 (4E40A3E2)
mvs91xx.sys Mon Aug 8 23:05:23 2011 (4E40A3F3)
iaStor.sys Tue Nov 29 22:39:19 2011 (4ED5A567)

The first 2 are your Marvell controller drivers - and shouldn't be used as there aren't any
2012 drivers that I know of.

The last one is the Intel storage controller - and there are 2012 drivers for that. You can get them at
Intel Download Center Search for the Intel Rapid Storage Technology drivers (RST).
 


#6
The SSD firmware was already up to date. I downloaded and installed the latest intel storage controller, although I still got BSOD. Daemon Tools was installed after the BSOD started, so it has been left alone so far.

After deleting the mvs91xx.sys diver it has been working fine, no issues for a good 6+ hours, through multiple restarts (restarts tended to make it BSOD quicker), as well as playing games and all the other programs I had been using when it was BSOD.
It seems likely that this has resolved the issue, but I couldn't be sure of that just yet.

Again, thanks for all the help. :)
 


#7
OK, no luck, BSOD's have continued, just a lot less frequently.

Currently I have checked all drivers are up to date, deleted all the drivers indicated above in red, except for the Daemon Tools drivers and removed the suggested programs.
I am now running it off a platter based hard drive, to see of it is stable. So far, so good.

Would likely suggest a problem with the SSD?
I will remove Daemon tools after testing on the platter based HD, if it's a good idea.
 


usasma

Fantastic Member
Microsoft Community Contributor
#8
I'd suggest removing Daemon Tools now as a test.

IMO, Daemon Tools is more likely to be the cause of the BSOD's than the SSD.
Plus, you can easily reinstall Daemon Tools - but it's not so easy to reinstall Windows.
 


#9
Removed Daemon tools and used the suggested tools to make sure the problematic drivers were removed, it worked fine for a couple of days, at the end of which I came back to the computer and the screen was just red with a grey border. But yeah, just a red screen, was very odd.
Then this morning after turning it on it lasted about 10 minuets and then I got BSOD with MEMORY_MANAGMENT again.

Any suggestions on what to do next?
Thanks.
 


#10
Try using Memtest86+ (link in my signature) and running it for about seven or so hours (which is pretty much overnight). Then take a picture of the results and post back.
 


usasma

Fantastic Member
Microsoft Community Contributor
#11
Please zip up and upload the contents of C:\Windows\Minidump so we can see the latest memory dumps.
That may give us additional clues as to what's happening.

Also, try the rest of the free diagnostics here: Hardware Diagnostics
Memory is also tested by the rest of the tests. There's memory on the CPU, on the motherboard, on the video card, and in some other unexpected areas - such as virtual memory being stored on the hard drive.
 


#14
Looking at the memtest results: something wrong (cos it's red).

Also, as usasma mentioned,
Also, try the rest of the free diagnostics here: Hardware Diagnostics
Memory is also tested by the rest of the tests. There's memory on the CPU, on the motherboard, on the video card, and in some other unexpected areas - such as virtual memory being stored on the hard drive.


Try the Hardware Diagnostics first.
In my signature, there's also Prime95 (CPU stress test, named "GIMPS"), FURMARK (GPU Stress test) and HDTUNE (Hard drive Stress Test).

Run Prime95 overnight and post back the results.
Run HDTUNE for 1 or 2 days and post back the results.
Run FURMARK (Burn-in benchmark 1920x1080 15 min and give us your score).

For the GPU Stress Test, you can also use Uningine Heaven DX11 (
http://unigine.com/products/heaven/) to test your GPU.
 


usasma

Fantastic Member
Microsoft Community Contributor
#15
RED = BAD when it comes to MemTest
See step 6b on memory test procedure here: Memory Diagnostics
This'll help you to figure out what's wrong (sticks vs slots).

Continue with the rest of the diagnostics, but it's important to fix the memory issues before doing any software repairs.
 


#16
I reseated the memory after using canned air and test results were better, no problems.
Then I ran all the sticks on there own and there were no problems, although I only ran them for 2 passes each, is that sufficient?
Then I used the fist stick and ran it in all the slots separately and no problems, but again, only for 2 passes.
Then I ran it with them all in again, in the morning when the computer was cold, because it mentioned that in the instructions, no problems again.

I have a couple of questions about the hard drive diag tools, I am currently running the WD one on the computer from the downloaded program. Do I need to do it from a disk?
And about the SSD, mine is OCZ, the suggested site only has tools for Intel, I couldn't seem to find anything on the OCZ website. Is there anything to check mine with? Do I need to?

Cheers.
 


usasma

Fantastic Member
Microsoft Community Contributor
#17
Run the memtest overnight on all sticks - if that passes, then I'd presume that you fixed it.

SSD tools aren't very common - I suggest this one (but haven't used it myself): Crystal Dew World

But, since you've fixed the memory issues, why not just wait to see if it BSOD's again?
 


#18
Yeah, that's the plan, but I thought I might as well get on top of what to do next, in case it doesn't. Plus it gives me something to look into while waiting for BSOD. :)
 


#19
I just put memtest on again to leave overnight, took a few minuets to get a whole bunch of errors.
 


#20
Do you have any other RAM sticks suitable with your current Motherboard (the RAM sticks should be working on other computers fine)?
If so, try testing those RAM sticks on your current motherboard, to test if it's the sticks or the motherboard that's causing the problem.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.