Daftmunk

New Member
Joined
Nov 25, 2012
Messages
26
Hello there!

I just brought a new computer, and are getting BSOD while playin wow. Haven't experienced this in any other game. Did a Memtest last night with no errors, so my question is: Anyone out there that might have a clue of what is going on with my computer?
I'm linking to my computer setup, dxDiag and latest Minidump below.

Computer setup:
Windows 7 Ultimate 64-bit
geForce GTX 670
Intel Core i5 - 3550 (Ivy Bridge)
Vengeance 8gb Dual Channel DDR3 Memory Kit (CMZ8GX3M2A1866C9B)
ASUS P8H77-V
1TB Seagate 7200RPM
Corsair GS600 PSU (600w)
Fractal Design Arctic (chassi)


Minidump: Link Removed
DxDiag: Link Removed

Thanks in advance,
Marcus
 


Solution
You have 108 updates installed -
normally there are about 130 to 140 updates installed, so check Windows Update for any missing updates.

One device has a problem:
AVG AVI Loader Driver This device is not present, is not working properly, or does not have all its drivers installed.
That device belongs to AVG Technologies, and has drivers for your antivirus software. Please download and install the correct driver for the device.
(Just a suggestion/pointer: just for now, use Microsoft Security Essentials [link: http://windows.microsoft.com/en-US/windows/security-essentials-download] as your antivirus - feel free to reinstall AVG Antivirus once your problem is fixed. Remember to only have one Antivirus installed on your...
I'm late for work - will return this afternoon or tomorrow AM
Please provide this info for a complete analysis: Link Removed
 


You have 108 updates installed -
normally there are about 130 to 140 updates installed, so check Windows Update for any missing updates.

One device has a problem:
AVG AVI Loader Driver This device is not present, is not working properly, or does not have all its drivers installed.
That device belongs to AVG Technologies, and has drivers for your antivirus software. Please download and install the correct driver for the device.
(Just a suggestion/pointer: just for now, use Microsoft Security Essentials [link: http://windows.microsoft.com/en-US/windows/security-essentials-download] as your antivirus - feel free to reinstall AVG Antivirus once your problem is fixed. Remember to only have one Antivirus installed on your computer)

LolLauncher also seems to be causing some problems - try reinstalling League of Legends and try it again.

Also try:
Reinstalling WoW.
Installing the latest version of DirectX (link: How to download and install DirectX)
Installing the latest drivers for your Graphics Card (for this, I'm giving you the BETA driver instead of the WHQL-signed driver)(link: Drivers | GeForce)
 


Solution
Hello!

This seems to have fixed the problem. :) I also found out that my networkcard driver was outdated and chipset.. But 6 hours gaming without any BSOD..

Thanks for the help, I'll come with update in a few days if I get any more BSOD..

Regards,
Daftmunk. :)
 


Hello!
I'm back, now it happend again.
Been playing for a couple of hours and BOOM, BSOD Your face.

Attached my latest here, please help get a solution on this.

Regards,
Daftmunk.
 


Attachments

IMO we're either looking at incompatible RAID/storage drivers or faulty hardware.

The RAID/storage stuff dates from 2007 to 2009. Depending on the source of your installation media, this may/may not be a problem. I've gotta wonder why you have an Silicone Image controller driver on an Asus mobo that doesn't use them. Do you have a RAID card installed on the system?

STEP 1: Update all controller drivers from the controller manufacturer's website. If unable to locate them, then try the Asus website. If there is an add-on RAID card, update the drivers from the manufacturer's website. Update motherboard chipset drivers to the latest version available from the chipset manufacturer's website ( Link Removed )

STEP 2: Run these free hardware diagnostics: Link Removed

STEP 3: Run Driver Verifier according to these instructions: Link Removed

STEP 4: Please update these older drivers (if you haven't already). 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! :

SiWinAcc.sys Thu Jun 14 20:02:02 2007 (4671D6FA)
Silicon Image driver - comes with package for the SIxxxx drivers
Link Removed

SiRemFil.sys Wed Jun 20 15:42:10 2007 (46798312)
Silicon Image driver
Link Removed

vsmraid.sys Fri Jan 30 20:18:57 2009 (4983A701)
VIA RAID driver for X86-32
Link Removed

amdsbs.sys Fri Mar 20 14:36:03 2009 (49C3E213)
AMD AHCI Compatible Controller driver
Link Removed



Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Tue Nov 27 16:50:07.984 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112712-13587-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 2:56:17.217[/B]
BugCheck Code: [B]BugCheck A, {fffffa88a0aeb110, 2, 1, fffff8000308c129}[/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]win32k.sys ( win32k+c6a68 )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
Arguments: 
Arg1: fffffa88a0aeb110, 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: fffff8000308c129, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: [B]spotify.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_win32k+c6a68[/B]
CPUID:        "Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3300[/B]
  BIOS Version                  0701
  BIOS Release Date             05/07/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 09:42:49.446 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-21980-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:55:13.521[/B]
BugCheck Code: [B]BugCheck 1A, {403, fffff680001d60f0, d9200000aba7b86f, fffff6802e1d60f0}[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff680001d60f0
Arg3: d9200000aba7b86f
Arg4: fffff6802e1d60f0
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]Wow.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_403_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2[/B]
CPUID:        "Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3300[/B]
  BIOS Version                  0701
  BIOS Release Date             05/07/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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]**************************Tue Nov 27 16:50:07.984 2012 (UTC - 5:00)**************************
[COLOR=RED][B]SiWinAcc.sys                Thu Jun 14 20:02:02 2007 (4671D6FA)[/B][/COLOR]
[COLOR=RED][B]SiRemFil.sys                Wed Jun 20 15:42:10 2007 (46798312)[/B][/COLOR]
[COLOR=RED][B]vsmraid.sys                 Fri Jan 30 20:18:57 2009 (4983A701)[/B][/COLOR]
[COLOR=RED][B]amdsbs.sys                  Fri Mar 20 14:36:03 2009 (49C3E213)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
xfiltx64.sys                Thu Aug 13 23:09:44 2009 (4A84D578)
amdsata.sys                 Thu Mar 18 20:45:17 2010 (4BA2C91D)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvraid.sys                  Fri Mar 19 16:59:20 2010 (4BA3E5A8)
DC3410.sys                  Mon May  2 05:40:52 2011 (4DBE7C24)
viahduaa.sys                Fri Nov  4 05:52:46 2011 (4EB3B5EE)
L1C62x64.sys                Mon Jan 16 02:10:16 2012 (4F13CD58)
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)
amd_xata.sys                Wed Apr 11 10:40:27 2012 (4F8597DB)
iaStorF.sys                 Wed Jun 20 09:14:44 2012 (4FE1CCC4)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
nvlddmkm.sys                Sun Nov 18 06:10:12 2012 (50A8C214)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 09:42:49.446 2012 (UTC - 5:00)**************************
ALSysIO64.sys               Sat Jul  9 20:27:45 2011 (4E18F201)
L1C62x64.sys                Fri Dec 23 04:13:21 2011 (4EF44631)
cpuz135_x64.sys             Wed May 23 10:53:22 2012 (4FBCF9E2)
avgrkx64.sys                Thu Sep 13 20:41:40 2012 (50527D44)
avgloga.sys                 Thu Sep 20 21:23:51 2012 (505BC1A7)
avgtdia.sys                 Thu Sep 20 21:25:33 2012 (505BC20D)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
avgmfx64.sys                Thu Oct  4 21:08:44 2012 (506E331C)
avgidsha.sys                Sun Oct 14 21:22:54 2012 (507B656E)
avgidsdrivera.sys           Mon Oct 22 06:47:11 2012 (5085242F)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
xfiltx64.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.
Link Removed
Link Removed
Link Removed
DC3410.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.
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
 


IMO we're either looking at incompatible RAID/storage drivers or faulty hardware.

The RAID/storage stuff dates from 2007 to 2009. Depending on the source of your installation media, this may/may not be a problem. I've gotta wonder why you have an Silicone Image controller driver on an Asus mobo that doesn't use them. Do you have a RAID card installed on the system?

May this be caused by that i use an old Windows 7 copy from my last computer?
If so, i might just go and buy a new OEM Windows 8.

But no, i don't have RAID card installed that i know of.
This is everything that is in my computer:

Windows 7 Ultimate 64-bit

geForce GTX 670
Intel Core i5 - 3550 (Ivy Bridge)
Vengeance 8gb Dual Channel DDR3 Memory Kit (CMZ8GX3M2A1866C9B)
ASUS P8H77-V
1TB Seagate 7200RPM
Corsair GS600 PSU (600w)
Fractal Design Arctic (chassi)

If there is a hardware problem, what parts is there that could be faulty from manufacturer?

Regards,
Marcus
 


It is possible that this is from an old copy of Win7 - but the drivers shouldn't have been installed (unless this was a copy from a computer manufacturer - rather than directly from Microsoft).

Perform the steps listed above before buying a new copy of anything.
That will tell us if there's a problem with either the 3rd party drivers or the hardware.
If we can successfully rule them out, then it'll be time to try another copy of Windows.
 


Thx for all of this!

Coming with update about these BSOD's..
I installed a clean copy of my windows again, due to i found out those raiddrivers came from my last installation file from Asus.
So cleansed the disk from all drivers and installed all the latest from Asus site + the latest driver GeneralHiningII linked..

No errors from anything this far atleast.

Fingers crossed

Regards,
Daftmunk
 


Hi!
I'm back again!

It took 24 Hours before the Bluescreens came back.
Here is the latest files!

Link Removed


Regards,
Daftmunk
 


Where did you get your copy of Windows from? What does it say on the face of the disk (if it came with the computer)?
The Silicone Image drivers are still there and they still date from 2007. I researched this a bit more, and updating the drivers will only get the dates up to 2008 - so I'm concerned about why these drivers are even on your system. I also have to wonder about the AMD drivers (you appear to have an Intel chipset) - but several of them are installed with any Windows installation, so I have to blame Microsoft for that.

Can you provide a link to the company who built the system?

Meanwhile, the latest memory dump points again to video issues and memory management issues.
Please run these free hardware diagnostics: Link Removed
Each one of the tests is important as each one tests different components of memory management (even the hard drive, as it's where paged out memory resides).


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

SiWinAcc.sys Thu Jun 14 20:02:02 2007 (4671D6FA)
Silicon Image driver - comes with package for the SIxxxx drivers
Link Removed

SiRemFil.sys Wed Jun 20 15:42:10 2007 (46798312)
Silicon Image driver
Link Removed

vsmraid.sys Fri Jan 30 20:18:57 2009 (4983A701)
VIA RAID driver for X86-32
Link Removed

amdsbs.sys Fri Mar 20 14:36:03 2009 (49C3E213)
AMD AHCI Compatible Controller driver
Link Removed



Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Thu Nov 29 14:34:15.282 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112912-15709-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 3:07:50.516[/B]
BugCheck Code: [B]BugCheck 1A, {403, fffff6800007a2f8, d0900000ace4a86f, fffff6808007a2f8}[/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]dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments: 
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800007a2f8
Arg3: d0900000ace4a86f
Arg4: fffff6808007a2f8
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]Wow-64.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_403_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2[/B]
CPUID:        "Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3300[/B]
  BIOS Version                  0701
  BIOS Release Date             05/07/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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]**************************Thu Nov 29 14:34:15.282 2012 (UTC - 5:00)**************************
[COLOR=RED][B]SiWinAcc.sys                Thu Jun 14 20:02:02 2007 (4671D6FA)[/B][/COLOR]
[COLOR=RED][B]SiRemFil.sys                Wed Jun 20 15:42:10 2007 (46798312)[/B][/COLOR]
[COLOR=RED][B]vsmraid.sys                 Fri Jan 30 20:18:57 2009 (4983A701)[/B][/COLOR]
[COLOR=RED][B]amdsbs.sys                  Fri Mar 20 14:36:03 2009 (49C3E213)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdsata.sys                 Thu Mar 18 20:45:17 2010 (4BA2C91D)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvraid.sys                  Fri Mar 19 16:59:20 2010 (4BA3E5A8)
DC3410.sys                  Mon May  2 05:40:52 2011 (4DBE7C24)
viahduaa.sys                Fri Nov  4 05:52:46 2011 (4EB3B5EE)
L1C62x64.sys                Mon Jan 16 02:10:16 2012 (4F13CD58)
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)
amd_xata.sys                Wed Apr 11 10:40:27 2012 (4F8597DB)
iaStorF.sys                 Wed Jun 20 09:14:44 2012 (4FE1CCC4)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
nvlddmkm.sys                Sun Nov 18 06:10:12 2012 (50A8C214)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
DC3410.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.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 


Last edited:
Hey,
this windows 7 I'm using is from my old Asus computer.. So I guess, that could be the problem?
This system I'm running for now I brought loose parts and put together myself. (got help from a computer freak friend)

These test you are talking about, I have no clue of how to use them.

So, it seems then there is some drivers included in the installation that is causing this problem?

If so, I should be able to fix it (Hopefully) If I brought a new windows OEM product and installed?

Regards,
Daftmunk
 


Diagnostics like GeneralHiningII suggests are the starting point. It's less likely that there is a problem from the installation disk.
If those pass, then do the full list of free diagnostics here: Link Removed

Asus Win7 disks are usually locked to prevent it from being used on another computer.
How did you get around that?

Have you tried a regular Win7 SP1 disk (like one from Digital River)? I'm uncertain on how to go about this as I've only read about it in other forums. I seem to recall it being in Microsoft Answers - so try searching there.
 


Last edited:
Hello,

I ran memtest over the night. It passed with 0 errors..
I ran harddrive this morning, passed without errors..

I've ran multiple stresstests now.. None of my components goes over 65 degress it seems through hwmonitor and coretemp..

Now I have no idea what to with this..
Since it seems no hardware issue, or software issue..
Or maybe I just should try get the RAM memories back and get some new ones..

Anyone of you guys have a suggestion on how to do now?

Regards,
Daftmunk
 


We are by no means done with this - but please answer these questions:
Asus Win7 disks are usually locked to prevent it from being used on another computer.
How did you get around that?

Have you tried a regular Win7 SP1 disk (like one from Digital River)? I'm uncertain on how to go about this as I've only read about it in other forums. I seem to recall it being in Microsoft Answers - so try searching there.

BTW - the license for the Asus copy of Windows is only good on the Asus hardware that you purchased. Legally it's required that you get another license in order to install it on different hardware - maybe a copy of Win8 would be a good idea at this point?
 


Hey,
Oh sorry, forgot to answer..

I was able to install it with just booting the install disk. So maybe mine wasn't blocked like that?

And No, haven't tried 1 from Digital River..

But allthough, I went shopping for a new operative system.. And got a BIOS update available with Windows 8 so now it seems to be working just fine. And hopefully this is what my computer needed to work properly.

Sincerly regards,
Daftmunk
 


Glad to hear it! Thanks for letting us know!
 


Hello again!

It took 24 hours before it came back with more BSOD's..
But I guess we can clearly make it about hardware issue now, and not software.

Same setup as before just using a windows 8 64-bit now..

Can you guys help me figure out what part of my computer I need to change?


Kind regards,
Daftmunk
 


Attachments

Back
Top