Windows 7 Random BSOD's, now i'm sick of it.

Jim Berggren · Nov 30, 2012

Hi,

I would like some help with my bluescreens. I've had them for 4-5 months now but as you will see at the dates they are not daily.

I don't know what else to write so just ask if you need more info.

Thanks

usasma · Dec 2, 2012

Sorry for the delay in responding, I've been real busy lately and don't have much time to spend online!

Only 80 updates since SP1 - most systems have 130 to 140. Please visit Windows Update and get ALL available updates.

Your SSD is awfully full - and is below the recommended 15% for Windows to operate with - but I'm unsure of how the free space stuff is treated with SSD', so I'd keep an eye on it just to be safe.

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...

usasma · Dec 2, 2012

Sorry for the delay in responding, I've been real busy lately and don't have much time to spend online!

Only 80 updates since SP1 - most systems have 130 to 140. Please visit Windows Update and get ALL available updates.

Your SSD is awfully full - and is below the recommended 15% for Windows to operate with - but I'm unsure of how the free space stuff is treated with SSD', so I'd keep an eye on it just to be safe.

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.

No error reports in the WER section of MSINFO32. Have you tweaked system settings dramatically? If so, could you briefly describe some of what you've done?

Please un-install MSI Afterburner. It (along with Riva Tuner and EVGA Precision) are know to cause BSOD's on some Win7 systems. Also, if overclocking, please stop while we are troubleshooting. Feel free to resume the overclock once the problem has been fixed.

Numerous errors when running your memory dumps. Should this be a pirated copy of Windows, please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F)
MagicISO SCSI Host Controller driver
Link Removed

MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)
Link Removed

emupia2k.sys Wed Jul 7 09:38:03 2010 (4C34833B)
Creative E-mu Plug-in Architecture Driver
Link Removed

ctsfm2k.sys Wed Jul 7 09:38:10 2010 (4C348342)
Creative SoundFont Management Device Driver
Link Removed

ctoss2k.sys Wed Jul 7 09:38:24 2010 (4C348350)
Creative OS Services Driver
Link Removed

ha20x22k.sys Wed Jul 7 09:41:25 2010 (4C348405)
Creative Technology Audigy
Link Removed

ctaud2k.sys Wed Jul 7 09:42:14 2010 (4C348436)
Creative Audio Driver (WDM)
Link Removed

ctprxy2k.sys Wed Jul 7 09:42:17 2010 (4C348439)
Creative Audio Driver (WDM)
Link Removed

CTEXFIFX.SYS Wed Jul 7 09:44:03 2010 (4C3484A3)
Creative sound card driver
Link Removed

CT20XUT.SYS Wed Jul 7 09:44:15 2010 (4C3484AF)
Creative sound card driver
Link Removed

CTHWIUT.SYS Wed Jul 7 09:44:19 2010 (4C3484B3)
Creative sound card driver
Link Removed

In short, if the above steps don't fix it (and if nothing new appears in subsequent memory dumps), then our next steps will be to look at hardware problems. Please ensure that your anti-virus and video drivers are the latest version available. Then start with these free hardware diagnostics: Link Removed Please run the MemTest86+ test for at least 7 passes (I ask this because of the long period of time between BSOD's) and the Prime 95 test for a minimum of 24 hours (you can use the computer while running Prime95 - it's just going to be very, very slow).

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Wed Nov 28 09:52:07.713 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112812-12058-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:01:58.977[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]109, {a3a039d89ea7a7e6, b3b7465ef124773c, fffff80003470790, 1}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: a3a039d89ea7a7e6, Reserved
Arg2: b3b7465ef124773c, Reserved
Arg3: fffff80003470790, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Nov 22 10:45:16.990 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112212-22214-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:00:50.254[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+437f6 )[/B]
BugCheck [B]50, {fffff7ffc3470665, 8, fffff7ffc3470665, 2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff7ffc3470665, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff7ffc3470665, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]MSIAfterburner[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_BAD_IP_nt!_??_::FNODOBFM::_string_+437f6[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 24 09:38:19.608 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102412-11731-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:00:42.873[/B]
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]D1, {ffffffffcffe6bc8, 2, 1, fffff880016548ab}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffcffe6bc8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880016548ab, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 24 09:36:54.532 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102412-21403-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:00:57.797[/B]
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]D1, {88, 2, 0, fffff8800164da05}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000088, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800164da05, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]chrome.exe[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct 23 09:26:25.741 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\102312-8689-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:04:01.615[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]109, {a3a039d89ea976cd, b3b7465ef1264623, fffff80003470374, 1}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: a3a039d89ea976cd, Reserved
Arg2: b3b7465ef1264623, Reserved
Arg3: fffff80003470374, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct  4 10:45:30.346 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100412-9235-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:04:04.220[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]109, {a3a039d89eab178b, b3b7465ef127e6e1, fffff8000347087e, 1}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: a3a039d89eab178b, Reserved
Arg2: b3b7465ef127e6e1, Reserved
Arg3: fffff8000347087e, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct  4 10:35:41.486 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100412-10374-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:00:46.360[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff8800164da73, fffff880031a16e8, fffff880031a0f40}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800164da73, The address that the exception occurred at
Arg3: fffff880031a16e8, Exception Record Address
Arg4: fffff880031a0f40, Context Record Address
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct  4 10:34:04.358 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100412-10467-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:01:04.232[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]D1, {fffff880498618b8, 2, 0, fffff880018618af}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff880498618b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880018618af, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 24 09:17:03.136 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092412-9453-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:01:15.401[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]D1, {28, 2, 0, fffff8800164da73}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800164da73, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 24 09:12:56.839 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092412-9422-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:00:30.713[/B]
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck [B]D1, {ffffffffd0239bc8, 2, 1, fffff880016548ab}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffd0239bc8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880016548ab, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT[/B]
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3292[/B]
  BIOS Version                  V1.12
  BIOS Release Date             06/08/2011
  Manufacturer                  MSI
  Product Name                  MS-7681
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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]**************************Wed Nov 28 09:52:07.713 2012 (UTC - 5:00)**************************
[B]mcdbus.sys                  Tue Feb 24 05:34:07 2009 (49A3CD1F)[/B]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
emupia2k.sys                Wed Jul  7 09:38:03 2010 (4C34833B)
ctsfm2k.sys                 Wed Jul  7 09:38:10 2010 (4C348342)
ctoss2k.sys                 Wed Jul  7 09:38:24 2010 (4C348350)
ha20x22k.sys                Wed Jul  7 09:41:25 2010 (4C348405)
ctaud2k.sys                 Wed Jul  7 09:42:14 2010 (4C348436)
ctprxy2k.sys                Wed Jul  7 09:42:17 2010 (4C348439)
CTEXFIFX.SYS                Wed Jul  7 09:44:03 2010 (4C3484A3)
CT20XUT.SYS                 Wed Jul  7 09:44:15 2010 (4C3484AF)
CTHWIUT.SYS                 Wed Jul  7 09:44:19 2010 (4C3484B3)
Rt64win7.sys                Wed Dec 29 06:44:36 2010 (4D1B1F24)
RTKVHD64.sys                Tue Jan  4 06:48:55 2011 (4D230927)
[B]RTCore64.sys                Tue Sep  6 08:24:50 2011 (4E661112)[/B]
nusb3hub.sys                Mon Oct 24 20:57:37 2011 (4EA60981)
nusb3xhc.sys                Mon Oct 24 20:57:38 2011 (4EA60982)
cpuz135_x64.sys             Fri Mar  9 03:56:55 2012 (4F59C5D7)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
nvhda64v.sys                Mon May 21 09:10:39 2012 (4FBA3ECF)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Nov 22 10:45:16.990 2012 (UTC - 5:00)**************************
nvlddmkm.sys                Thu Jun 28 18:58:00 2012 (4FECE178)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 24 09:38:19.608 2012 (UTC - 5:00)**************************
nusb3hub.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)
nusb3xhc.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
nvlddmkm.sys                Wed Aug 22 07:11:30 2012 (5034BE62)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

Jim Berggren · Dec 2, 2012

Hi, thanks for the help.

I forgot to tell something about my problem.
When i get the Bsod's it's just after start up and i try to open a web page.

I will try to replace my ssd with a new one and get a fresh install of a legit copy of Windows 8.

Windows 7 Random BSOD's, now i'm sick of it.

Jim Berggren

New Member

Attachments

usasma

usasma

Fantastic Member

Jim Berggren

New Member

Similar threads