Windows 7 random BSODs - new system

BenniMa · Jan 2, 2013

I just bought a system including the following hardware:

ASRock Extreme 4
I5 3570k
16 GB Corsair Ram
Gainward GTX 570

I installed all the drivers on the ASRock Page and two newer ones for the Intel USB 3 and the Intel HD IGPU. Now I get theses random Bluescreens, like once a day.

Possible reasons:

- overclock of my i5 3570K to 4.2 with stock voltage
- using Intel HD and the NVIDIA card (driver conflict?)

I am quiete new to these kind of problems so be kind Thank you very much.

usasma · Jan 3, 2013

Please remove the overclock while we're troubleshooting the issues. Feel free to resume the overclock once the BSOD's have stopped.

At work we run diagnostics on every system that we take in for repair (before we even start working on it). At a minimum, please run the free diagnostics here: Link Removed. For more in-depth diagnostics, please run those listed here: Link Removed

Only 2 updates since SP1 - most systems have 130 to 140. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

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

usasma · Jan 3, 2013

Please remove the overclock while we're troubleshooting the issues. Feel free to resume the overclock once the BSOD's have stopped.

At work we run diagnostics on every system that we take in for repair (before we even start working on it). At a minimum, please run the free diagnostics here: Link Removed. For more in-depth diagnostics, please run those listed here: Link Removed

Only 2 updates since SP1 - most systems have 130 to 140. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

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.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)

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! :

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

ElbyCDIO.sys Thu Dec 16 17:58:13 2010 (4D0A9985)
CDRTools/ElbyCDIO/DVD Region Killer/VirtualCloneDrive (elby CloneDVD™ 2)/AnyDVD
Link Removed

VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
VirtualCloneCD Driver by Elaborate Bytes AG
Link Removed

asmtxhci.sys Fri Mar 4 02:54:59 2011 (4D709AD3)
Asmedia USB 3.0 driver
Link Removed

asmthub3.sys Fri Mar 4 02:55:10 2011 (4D709ADE)
ASMedia USB 3.0 Hub driver
Link Removed

ISCTD64.sys Tue Aug 23 13:32:39 2011 (4E53E437)
Intel Smart Connect Technology Driver
Link Removed

asahci64.sys Wed Sep 21 05:42:57 2011 (4E79B1A1)
Asmedia 106x SATA Host Controller Driver
Link Removed

If all of this doesn't fix things, please run Driver Verifier according to these instructions: Link Removed

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Wed Jan  2 21:29:53.776 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010313-24086-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 3:18:33.978[/B]
Probably caused by :[B]System ( INVALID_CONTEXT )[/B]
BugCheck [B]D1, {3, 2, 8, 3}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000003, address which referenced memory
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  RAISED_IRQL_FAULT
FAILURE_BUCKET_ID: [B]X64_RAISED_IRQL_FAULT_System_CODE_AV_BAD_IP_INVALID_CONTEXT[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  BIOS Version                  P2.70
  BIOS Release Date             11/28/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jan  2 18:10:44.666 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010313-23524-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 5:36:29.494[/B]
Probably caused by :[B]Unknown_Image ( nt!KiDeferredReadyThread+1f9 )[/B]
BugCheck [B]A, {30, 2, 1, fffff800032e3919}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032e3919, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  BIOS Version                  P2.70
  BIOS Release Date             11/28/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 30 10:50:34.625 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\123012-23556-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime:[B]0 days 1:04:57.002[/B]
Probably caused by :[B]System ( INVALID_CONTEXT )[/B]
BugCheck [B]D1, {3, 2, 8, 3}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000003, address which referenced memory
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  RAISED_IRQL_FAULT
FAILURE_BUCKET_ID: [B]X64_RAISED_IRQL_FAULT_System_CODE_AV_BAD_IP_INVALID_CONTEXT[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  BIOS Version                  P2.70
  BIOS Release Date             11/28/2012
  Manufacturer                  To Be Filled By O.E.M.
  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]**************************Wed Jan  2 21:29:53.776 2013 (UTC - 5: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)
ElbyCDIO.sys        Thu Dec 16 17:58:13 2010 (4D0A9985)
VClone.sys          Sat Jan 15 11:21:04 2011 (4D31C970)
asmtxhci.sys        Fri Mar  4 02:54:59 2011 (4D709AD3)
asmthub3.sys        Fri Mar  4 02:55:10 2011 (4D709ADE)
k57nd60a.sys        Tue May 10 00:42:30 2011 (4DC8C236)
ISCTD64.sys         Tue Aug 23 13:32:39 2011 (4E53E437)
asahci64.sys        Wed Sep 21 05:42:57 2011 (4E79B1A1)
RTKVHD64.sys        Tue Jan 31 05:55:06 2012 (4F27C88A)
IntcDAud.sys        Tue Jun 19 10:40:51 2012 (4FE08F73)
HECIx64.sys         Mon Jul  2 18:14:58 2012 (4FF21D62)
nvhda64v.sys        Tue Jul  3 11:25:04 2012 (4FF30ED0)
aswrdr2.sys         Mon Oct  8 04:23:43 2012 (50728D8F)
iusb3hub.sys        Tue Oct 16 11:49:22 2012 (507D8202)
iusb3xhc.sys        Tue Oct 16 11:49:26 2012 (507D8206)
iusb3hcs.sys        Tue Oct 16 11:51:20 2012 (507D8278)
igdkmd64.sys        Wed Oct 17 15:12:29 2012 (507F031D)
aswFsBlk.SYS        Tue Oct 30 18:43:04 2012 (509057F8)
aswMonFlt.sys       Tue Oct 30 18:43:09 2012 (509057FD)
aswTdi.SYS          Tue Oct 30 18:43:16 2012 (50905804)
aswSP.SYS           Tue Oct 30 18:44:06 2012 (50905836)
aswSnx.SYS          Tue Oct 30 18:44:08 2012 (50905838)
iaStorA.sys         Mon Nov 19 15:09:40 2012 (50AA9204)
dump_iaStorA.sys    Mon Nov 19 15:09:40 2012 (50AA9204)
iaStorF.sys         Mon Nov 19 15:09:43 2012 (50AA9207)
nvlddmkm.sys        Fri Nov 30 22:24:02 2012 (50B97852)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 30 10:50:34.625 2012 (UTC - 5:00)**************************
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)
[/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
Link Removed
Link Removed
Link Removed
Link Removed

BenniMa · Jan 3, 2013

Thx for your fast response.

you are right I totally forgot to enable windows update again. Now windows is up tp date again.

What I did so far:

1. memtest86+ -> no errors

2. Updated these drivers:

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

VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
VirtualCloneCD Driver by Elaborate Bytes AG
Link Removed

asmtxhci.sys Fri Mar 4 02:54:59 2011 (4D709AD3)
Asmedia USB 3.0 driver
Link Removed

asmthub3.sys Fri Mar 4 02:55:10 2011 (4D709ADE)
ASMedia USB 3.0 Hub driver
Link Removed

ISCTD64.sys Tue Aug 23 13:32:39 2011 (4E53E437)
Intel Smart Connect Technology Driver
Link Removed

asahci64.sys Wed Sep 21 05:42:57 2011 (4E79B1A1)
Asmedia 106x SATA Host Controller Driver
Link Removed
(even I this device does not appear in my device manager - it is not active though I think)

Not shure about this one:

ElbyCDIO.sys Thu Dec 16 17:58:13 2010 (4D0A9985)
CDRTools/ElbyCDIO/DVD Region Killer/VirtualCloneDrive (elby CloneDVD™ 2)/AnyDVD
Link Removed

Do you want me to install cdrtools to get that driver? Is it part of virtualclonedrive?

Furthermore I will stay with the ssd drive, even they have some problems...
Now I will look for newer chipset drivers.

No crashes after these steps so far. Will run some benchmarks and games to stress the system.

BenniMa · Jan 3, 2013

thx for your quick response

I totally forgot to enable windows update again. Now my system is up to date again.

what I have done so far:

1. Updated win7

2. memtest86+ -> no errors

3. updated these drivers:

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

VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
VirtualCloneCD Driver by Elaborate Bytes AG
Link Removed

asmtxhci.sys Fri Mar 4 02:54:59 2011 (4D709AD3)
Asmedia USB 3.0 driver
Link Removed

asmthub3.sys Fri Mar 4 02:55:10 2011 (4D709ADE)
ASMedia USB 3.0 Hub driver
Link Removed

ISCTD64.sys Tue Aug 23 13:32:39 2011 (4E53E437)
Intel Smart Connect Technology Driver
Link Removed

asahci64.sys Wed Sep 21 05:42:57 2011 (4E79B1A1)
Asmedia 106x SATA Host Controller Driver
Link RemovedBut I did not install this one yet:

ElbyCDIO.sys Thu Dec 16 17:58:13 2010 (4D0A9985)
CDRTools/ElbyCDIO/DVD Region Killer/VirtualCloneDrive (elby CloneDVD™ 2)/AnyDVD
Link Removed

why do I have to install this? You want me to install CDRtools to get a certain driver?

Also I would like to stay with my SSD, even some of them have problems. Will stress the system now.
Now bluescreens so far.

usasma · Jan 3, 2013

The ElbyCDIO.sys driver is highlighted for updating simply because it dates from 2010. The script that I use highlights all drivers from 2011 and earlier because that's before Win8 came out (it was released on 26 Oct 2012). That causes me to wonder if it's compatible with Win8 - or if it's just been behaving for you until a certain Windows came along and forced it to show it's incompatibility.

But it's your system - so it's your choice what you do or don't do.
Good luck to you.

BenniMa · Jan 7, 2013

I just wanted to come back here to thank you. You did a great job - no bsod anymore. thread can be closed

usasma · Jan 8, 2013

Thank you!

Windows 7 random BSODs - new system

BenniMa

New Member

Attachments

usasma

usasma

Fantastic Member

BenniMa

New Member

BenniMa

New Member

usasma

Fantastic Member

BenniMa

New Member

usasma

Fantastic Member

Similar threads