Multiple BSODs - unable to run jcgriff bsod file collection app

hullohihello · Oct 9, 2012

Hi, recently I have been having a few problems with BSODs. The frequency of BSOD's has been increasing, primarily ones relating to memory management and page fault in a nonpaged area. Usually this will happen 1/4 times when booting the computer, as the only time I have ever gotten a BSOD is within minutes of booting the computer.

I tried to run the jcgriff bsod file collection app but had the resulting message. If somebody could tell me how to resolve this, I will run it again and edit my post with the new information.
"
There is a problem with the Environement variables on this system. Unable to determine the location of the Documents or Desktop folders.

Copy and paste the following information to the
forum where you are receiving assistance:
*********************************************************************

Microsoft Windows [Version 6.1.7601]

HomeDrive C:
HomePath \Users\Kevin
Userprofile C:\Users\Kevin
*********************************************************************
"

Also to note, the computer does not shutdown properly and the power button must be manually held after shutdown to drain power from the board. This may or may not be related as the shutdown problem has existed well before BSOD's have become common. Although, help regarding this would also be appreciated.

· OS - Windows 7
· x86 (32-bit)
· What was original installed OS on system? Windows 7
· OEM, from from disk
· Age of system (hardware) - 4 months
· Age of OS installation - have you re-installed the OS? -The day after building it I clean installed windows again due to messing up

· CPU - i5-3570k (not overclocked)
· Video Card - Radeon 7950 MSI Twin Frozr III
· MotherBoard - ASRock z77 Extreme4
· Power Supply - brand & wattage - Corsair TX750 (750watts)

· System Manufacturer - Homebuilt

Thanks in advance! I really appreciate everything you guys are doing here on these forums!

usasma · Oct 9, 2012

Please open an elevated (Run as adminsitrator) Command Prompt and type this:
"systeminfo >%userprofile%\Desktop\systeminfo.txt" (without the quotes)
and then press Enter

Then please open up MSINFO32 (go to Start, type in "msinfo32" (without the quotes) and press Enter)
In the MSINFO32 application, go to File...Save - and save the .nfo file on your Desktop

Then please go to C:\Windows\Minidump and copy the contents of that directory to your Desktop also (no need to copy more than the latest 10 or so)

Finally, zip all that up into a .zip archive and attach it with your next post.
In addition to the minidump files (those ending in .dmp), you'll also have a file named systeminfo.txt and another file that ends in .nfo

hullohihello · Oct 10, 2012

I got an error trying to get the systeminfo.txt with your method but I did eventually find another way to do it so hopefully it is the same thing. I attached everything you asked for.

Thanks again for helping.

usasma · Oct 10, 2012

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

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): http://crystalmark.info/?lang=en
- 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 - http://www.techsupportforum.com/forums/f299/cant-find-the-cause-of-bsod-f4-613075.html#post3537179
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.

Please be sure to update your controller drivers - including the ASMedia controller that dates from March of 2011.

Please uninstall MSI Afterburner. It (along with Riva Tuner and EVGA Precision) are known to cause BSOD's on Win7 systems.

If overclocking, please return the system to stock settings (non-overclocked) while we're troubleshooting. Feel free to resume the overclock once the system is stable again (no BSOD's).

Analysis:
The following is for information purposes only.

Code:

**************************Wed Oct 10 20:57:36.208 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101012-8704-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:58.989
BugCheck Code: BugCheck 1E, {ffffffffc000001d, fffff960000aa70b, 0, fffff88007f0c900}
Probably caused by :memory_corruption
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 10 20:54:43.998 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101012-7846-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:28.153
BugCheck Code: BugCheck 50, {fffff8804b825160, 0, fffff96000228705, 5}
Probably caused by :memory_corruption
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 10 20:53:41.121 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101012-7160-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:01:07.276
BugCheck Code: BugCheck 50, {fffff680200184c8, 0, fffff80002eb29d7, 2}
Probably caused by :memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct  9 13:20:15.967 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100912-6957-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:00:17.122
BugCheck Code: BugCheck 50, {fffff6fc5005e910, 0, fffff80002eb17b0, 9}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :CI.dll ( CI!I_MinCryptGetCertificateEKUs+69 )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x50_CI!I_MinCryptGetCertificateEKUs+69
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Oct  9 13:18:10.344 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100912-6832-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:00:19.124
BugCheck Code: BugCheck 50, {fffff8a40248abb0, 0, fffff800031c8e5a, 5}
Probably caused by :ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+16a )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0x50_nt!ObpLookupDirectoryEntry+16a
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Oct  1 20:08:55.713 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100112-7784-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:00:19.494
BugCheck Code: BugCheck 50, {fffff901005817a0, 1, fffff960001b3786, 5}
Probably caused by :memory_corruption
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 30 10:51:35.083 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\093012-7597-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:03:03.238
BugCheck Code: BugCheck 50, {fffffa80c4750438, 0, fffff80002e56ccb, 5}
Probably caused by :memory_corruption ( nt!MiDeleteAddressesInWorkingSet+27f )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: X64_0x50_nt!MiDeleteAddressesInWorkingSet+27f
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 29 12:21:59.502 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092912-9016-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:00:45.657
BugCheck Code: BugCheck 50, {fffff8e0003437ea, 0, fffff800031c0e6d, 5}
Probably caused by :ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+17d )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: RtWLan.exe
FAILURE_BUCKET_ID: X64_0x50_nt!ObpLookupDirectoryEntry+17d
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep 28 18:56:38.877 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092812-6910-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:00:38.658
BugCheck Code: BugCheck 50, {fffff9640030ba98, 0, fffff88001032e1e, 5}
Probably caused by :msrpc.sys ( msrpc!I_RpcGetBufferWithObject+2e )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_0x50_msrpc!I_RpcGetBufferWithObject+2e
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 27 13:42:27.300 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092712-9781-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 0:00:54.081
BugCheck Code: BugCheck 3B, {c0000005, fffff96000056dc9, fffff8800b701d10, 0}
Probably caused by :win32k.sys ( win32k!xxxInternalDoPaint+19 )
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME: Skype.exe
FAILURE_BUCKET_ID: X64_0x3B_win32k!xxxInternalDoPaint+19
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Oct 10 20:57:36.208 2012 (UTC - 4:00)**************************

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:

**************************Wed Oct 10 20:57:36.208 2012 (UTC - 4:00)**************************
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)
asmtxhci.sys                Fri Mar  4 02:54:59 2011 (4D709AD3) - ASMedia Controller
asmthub3.sys                Fri Mar  4 02:55:10 2011 (4D709ADE) - ASMedia Controller
speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)
k57nd60a.sys                Tue May 10 00:42:30 2011 (4DC8C236)
rtl8192Ce.sys               Tue Jun 14 23:05:06 2011 (4DF82162)
ISCTD64.sys                 Tue Aug 23 13:32:39 2011 (4E53E437)
asahci64.sys                Wed Sep 21 05:42:57 2011 (4E79B1A1)
WPRO_41_2001.sys            Mon Nov  7 16:04:48 2011 (4EB847F0)
HECIx64.sys                 Wed Nov  9 19:52:25 2011 (4EBB2049)
IntcDAud.sys                Tue Dec  6 06:23:07 2011 (4EDDFB1B)
ikbevent.sys                Tue Jan  3 19:35:09 2012 (4F039EBD)
imsevent.sys                Tue Jan  3 19:35:31 2012 (4F039ED3)
AsrRamDisk.sys              Thu Jan 12 23:52:38 2012 (4F0FB896)
RTKVHD64.sys                Tue Jan 31 05:55:06 2012 (4F27C88A)
iusb3hub.sys                Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys                Mon Feb 27 05:56:53 2012 (4F4B6175)
iusb3hcs.sys                Mon Feb 27 05:58:49 2012 (4F4B61E9)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
igdkmd64.sys                Mon May 21 15:04:11 2012 (4FBA91AB)
iaStor.sys                  Wed May 30 16:40:40 2012 (4FC685C8)
atikmpag.sys                Fri Jul 27 21:14:47 2012 (50133D07)
atikmdag.sys                Fri Jul 27 21:48:09 2012 (501344D9)
rzudd.sys                   Fri Aug 17 03:01:22 2012 (502DEC42)
rzvkeyboard.sys             Fri Aug 17 03:01:26 2012 (502DEC46)
rzdaendpt.sys               Fri Aug 17 03:01:28 2012 (502DEC48)

hullohihello · Oct 10, 2012

Thanks for the help. I tried everything you suggested including updating my ssd controller, installing all windows updates, and removing afterburner. The ASMedia Drivers are updated, as the march 2011 driver is the latest update available on the motherboard website unless I am mistaken about which driver we are referring to. When I used the corrona driver lookup, the update link is different than that of my motherboard driver downloads so I did not download those.

I don't know how to my motherboard controller drivers so I did not do that.

If problems continue to happen, I will post again.

hullohihello · Oct 12, 2012

Blue screens are continuing to occur. Attached are the dump files.

How likely is it for a BSOD to occur from faulty hardware? I'm starting to wonder if it is a hardware issue.

usasma · Oct 13, 2012

The most likely cause of BSOD's is problems with 3rd party drivers
Next most likely is hardware
Then comes Windows problems

On average it takes at least 2 pages of posts to fix the majority of BSOD's, in some cases it can take many more. Please be patient - this is the best site on the web for BSOD analysis and it was founded just for that purpose.

We work on the 3rd party stuff first - in order to rule it out.
What controller is your SSD connected to? Please ensure that it's connected to an Intel controller - as that's the most recent storage controller on your system.

The BSOD's that you are getting are generally associated with driver issues (but the line between drivers and hardware is a bit blurred when talking about BSOD's). Try running Driver Verifier to see if we can force it to name the offending driver. Please use this procedure: http://www.carrona.org/verifier.html

If that doesn't stop the BSOD's, I'd suggest that you try installing Win7 on a platter based hard drive - that will rule out the most likely cause of these problems (the SSD not being compatible with your hardware). Don't bother to activate the install as you'll switch back to the SSD if it proves that it's not the SSD (and you can always activate the platter based hard drive installation later on - if needed).

I've learned to never discount the owner's gut feelings (that's how most BSOD's are solved). So, as you have time, please run these free hardware diagnostics: http://www.carrona.org/hwdiag.html

Analysis:
The following is for information purposes only.

Code:

**************************Fri Oct 12 17:23:15.545 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101212-7051-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:50.326
BugCheck Code: BugCheck 3B, {c0000005, fffff960000cdaae, fffff88008efde60, 0}
Probably caused by :memory_corruption
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME: explorer.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 12 15:27:24.022 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101212-7519-02.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:18.803
BugCheck Code: BugCheck 50, {fffff8a408613eca, 0, fffff8000312bb97, 5}
Probably caused by :win32k.sys ( win32k!UserGetAtomName+31 )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: Skype.exe
FAILURE_BUCKET_ID: X64_0x50_win32k!UserGetAtomName+31
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 12 15:22:34.231 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101212-7519-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:18.012
BugCheck Code: BugCheck 50, {fffff140031cabcc, 0, fffff80002ec99f4, 7}
Probably caused by :memory_corruption ( nt!MiRemoveNode+204 )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x50_nt!MiRemoveNode+204
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 12 15:21:38.343 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101212-8283-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:27.498
BugCheck Code: BugCheck 50, {fffff8a406de3382, 0, fffff80002eb6e25, 5}
Probably caused by :ntkrnlmp.exe ( nt!SepMandatoryIntegrityCheck+75 )
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: wmpnetwk.exe
FAILURE_BUCKET_ID: X64_0x50_nt!SepMandatoryIntegrityCheck+75
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct 11 17:04:54.412 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\101112-8174-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:00:31.193
BugCheck Code: BugCheck 50, {ffffffff8b49285c, 1, fffff960000b678c, 5}
Probably caused by :memory_corruption
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.00
  BIOS Release Date             07/13/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 12 17:23:15.545 2012 (UTC - 4:00)**************************

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:

**************************Fri Oct 12 17:23:15.545 2012 (UTC - 4:00)**************************
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)
asmtxhci.sys                Fri Mar  4 02:54:59 2011 (4D709AD3)
asmthub3.sys                Fri Mar  4 02:55:10 2011 (4D709ADE)
speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)
k57nd60a.sys                Tue May 10 00:42:30 2011 (4DC8C236)
rtl8192Ce.sys               Tue Jun 14 23:05:06 2011 (4DF82162)
ISCTD64.sys                 Tue Aug 23 13:32:39 2011 (4E53E437)
asahci64.sys                Wed Sep 21 05:42:57 2011 (4E79B1A1)
WPRO_41_2001.sys            Mon Nov  7 16:04:48 2011 (4EB847F0)
HECIx64.sys                 Wed Nov  9 19:52:25 2011 (4EBB2049)
IntcDAud.sys                Tue Dec  6 06:23:07 2011 (4EDDFB1B)
ikbevent.sys                Tue Jan  3 19:35:09 2012 (4F039EBD)
imsevent.sys                Tue Jan  3 19:35:31 2012 (4F039ED3)
AsrRamDisk.sys              Thu Jan 12 23:52:38 2012 (4F0FB896)
RTKVHD64.sys                Tue Jan 31 05:55:06 2012 (4F27C88A)
iusb3hub.sys                Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys                Mon Feb 27 05:56:53 2012 (4F4B6175)
iusb3hcs.sys                Mon Feb 27 05:58:49 2012 (4F4B61E9)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
igdkmd64.sys                Mon May 21 15:04:11 2012 (4FBA91AB)
iaStor.sys                  Wed May 30 16:40:40 2012 (4FC685C8)
atikmpag.sys                Fri Jul 27 21:14:47 2012 (50133D07)
atikmdag.sys                Fri Jul 27 21:48:09 2012 (501344D9)
rzudd.sys                   Fri Aug 17 03:01:22 2012 (502DEC42)
rzvkeyboard.sys             Fri Aug 17 03:01:26 2012 (502DEC46)
rzdaendpt.sys               Fri Aug 17 03:01:28 2012 (502DEC48)

hullohihello · Oct 13, 2012

I just want to say thanks again and apologize if I'm coming across as impatient.

First, how do I determine what controller my SSD is connected to? It's currently connected to a SATA3 port on the back of my motherboard but I doubt that is what you are referring to.

I will run driver verifier as well as all of the other hardware diagnostics you have mentioned. I have ran furmark, memtest, and prime95 before but will definitely at least try to run a hard drive diagnostic as well as running memtest for longer (I only ran 2 passes last time so I'll try running it overnight today).

In regards to installing Windows onto a platter based drive, would I be able to install in onto the platter based drive and then be able to boot off of that drive while still being able to access the programs on the SSD? I will try to do that, although I am not positive when I will have time to do that. I do want to note that for the first few days of having the system, it was run purely off of the SSD as I was short a SATA cable and never experienced any problems during that time.

While working on all of the things you have mentioned, I would like to point out that my computer does not shut down properly and instead boots again after a few seconds(mentioned in first post). Additionally, the computer fails to POST occasionally (like ~1/5 boots). I don't know for sure if this is related to the BSOD but just something to consider.

usasma · Oct 13, 2012

First, how do I determine what controller my SSD is connected to? It's currently connected to a SATA3 port on the back of my motherboard but I doubt that is what you are referring to.

Actually, that is what I'm referring to. A look in your mobo manual should tell you what controller is assigned to that port.

Do you have any eSATA devices connected? If so, disconnect them as they interfere with the SATA3 ports

From page 46 of your mobo manual:
ASMedia ASM1061 chipset supports Serial ATA3 (SATA3) hard disks for SATA3_A0
and SATA3_A1 connectors

Intel Z77 chipset that supports Serial ATA3 (SATA3) hard
disks and RAID (RAID 0, RAID 1, RAID 5, RAID 10, Intel Rapid Storage and Intel
Smart Response Technology) functions for SATA3_0 and SATA3_1 connectors.

Look at page 13 to determine which slot is which.
Then, if not using the Intel connector - please change it over so it's connected to the Intel storage controller connectors.
The Intel storage drivers date from 2012, while the ASMedia date from 2011.

Link where I got the manual from : http://www.asrock.com/mb/Intel/Z77 Extreme4/?cat=Manual
************************
Installing to a platter based hard drive is just a test. You'd only run it long enough to see if it BSOD's or not.
Unfortunately, there's no way to run the programs off the SSD on the platter based hard drive without installing them.

You mentioned that you had only the SSD when you first installed - does this mean that you have another Hard Drive?
If that's the case, please run the hard drive diagnostics on that other hard drive also (run the diagnostics on ALL hard drives). That combined with the POST issues is suggestive of a hardware problem.

hullohihello · Oct 20, 2012

Sorry about replying so late, I've been busy all week on my college apps (and will be for another week). I do have two hard drives, a WD Caviar Black 1TB and a Corsair Force GT 120gb. I will double check as to which connector they are connected to and reconnect to the Intel controller if they are not already.

I have ran some hard drive diagnostics and so far everything as came up clean. I have some spare time this afternoon so I'll run memtest for a few passes and see how those results go. I have not started running driver verifier as I haven't really used this computer all that much. I can probably start running that next weekend once college things are done.

Attached are some additional dump files if they would be of any use.

hullohihello · Oct 20, 2012

Update. The hard drives are indeed connected to the Intel controller on the motherboard. Also, memtest ran fine for 3 passes (2.5 hours) so I stopped testing memory as I previously ran 2 passes also without errors, indicating memory is likely not to be at fault.

jcgriff2 · Oct 20, 2012

Hi -

The bugchecks on the last 2 dumps = 0x50 = invalid memory referenced

Are you running memtest86+ one stick at a time and alternating the slots?

Did these 2 BSODs occur with a SATA HDD or SSD? I ask because SSD problems can mimic RAM in dump files.

If no SSD, it appears that either RAM itself is failing or other unknown hardware failure is causing RAM to fail (not properly hold kernel code).

HDD could be an issue here as "invalid memory" could of course refer to virtual memory (hard drive).

Regards. . .

jcgriff2

BSOD SUMMARY

Code:


Debug session time: Sat Oct 20 13:16:17.100 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\102012-10327-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:00:26.256
BugCheck 50, {ffffffff00000404, 1, fffff80002ee0980, 5}
Probably caused by : win32k.sys ( win32k!SleepInputIdle+79 )
Bugcheck code 00000050
Arguments: 

Arg1: ffffffff00000404, memory referenced.

Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.

Arg3: fffff80002ee0980, If non-zero, the instruction address which referenced the bad memory

	address.

Arg4: 0000000000000005, (reserved)


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  iTunesHelper.e
FAILURE_BUCKET_ID:  X64_0x50_win32k!SleepInputIdle+79
MaxSpeed:     3400
CurrentSpeed: 3400
BiosVersion = P2.00
BiosReleaseDate = 07/13/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Oct 20 13:15:07.534 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\102012-9656-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:02:48.315
BugCheck 50, {fffffa80c3e775e8, 0, fffff80002e9db3b, 5}
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+27f )
Bugcheck code 00000050
Arguments: 

Arg1: fffffa80c3e775e8, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff80002e9db3b, If non-zero, the instruction address which referenced the bad memory

	address.

Arg4: 0000000000000005, (reserved)


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+27f
MaxSpeed:     3400
CurrentSpeed: 3400
BiosVersion = P2.00
BiosReleaseDate = 07/13/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

        
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           [url]https://mvp.support.microsoft.com/profile/Griffith[/url]   

           jcgriff2 - Sysnative Forums
             
           [url]www.jcgriff2.com[/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

hullohihello · Oct 20, 2012

I ran memtest with both sticks in. Do I need to run in with only one stick at a time or is running both at the same time ensuring that both work fine individually?

The system is currently running with a SSD and a HDD which are both SATA, with the OS and all programs on the SSD and documents on the HDD.

jcgriff2 · Oct 20, 2012

Yes, memtest needs to run 1 stick at a time; alternate the slots.

If RAM passes, I would consider ruling the SSD out next by installing Windows onto the SATA HDD ONLY (remove the SSD) -- then see if BSODs persist.

Regards. . .

jcgriff2

`

Search

Search

Multiple BSODs - unable to run jcgriff bsod file collection app

hullohihello

Member

Attachments

usasma

Retired Admin

hullohihello

Member

Attachments

usasma

Retired Admin

hullohihello

Member

hullohihello

Member

Attachments

usasma

Retired Admin

hullohihello

Member

usasma

Retired Admin

hullohihello

Member

Attachments

hullohihello

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

hullohihello

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Multiple BSODs - unable to run jcgriff bsod file collection app

Member

Attachments

Retired Admin

Member

Attachments

Retired Admin

Member

Member

Attachments

Retired Admin

Member

Retired Admin

Member

Attachments

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)