Dear SF Users
First of all I hope that this is in the right place and that you can help me.
I recently(4 days ago) build a new PC, consisting of the following pars:
CPU: AMD Processors for Desktops: AMD Phenom™, AMD Athlon™ FX, AMD Athlon™ X2 Dual-Core, AMD Athlon™, and AMD Sempron™ Processor
MOBO: GA-770TA-UD3 (rev. 1.0) - GIGABYTE
MOBO COOLER: Hyper 212 Plus - Cooler Master
GPU: Product section
PSU: Real Power M520 - Cooler Master
RAM: GeIL GV34GB1333C9DC prijzen | Core | Tweakers.net Pricewatch
Case: CM 690 II Advanced - Cooler Master
OS: Windows 7 Home Premium 64Bit OEM
The first problem encountered was that my mobo had bios version F2 which did not support my CPU. So when I found out after 6 hours I updated the BIOS to F3, and it worked.
I installed windows 7 and the drivers on cd from my mobo and GPU. And updated them all.
Havning encountered a few crashes here and there(bsods) during various installations and during the prosess of copying files I was supprised, but not worried.
When I started to play(Starcraft 2, which was set on Ultra) It worked fine, the first time. After that I kept encountering BSODs. So after reading a lot and using WinDBG I tried to deinstall my ATI drivers.
Which seemed to work. But then again I started to encounter "other" BSODs, during more random stuff, listing to music, trying to open a file, playing AC2.
So I decided to ask, beg you guys for help.
I attached the requested files and a zip with the error messages and dmp files after several (different) crashes.
Thanks!!!!
Titus
First of all I hope that this is in the right place and that you can help me.
I recently(4 days ago) build a new PC, consisting of the following pars:
CPU: AMD Processors for Desktops: AMD Phenom™, AMD Athlon™ FX, AMD Athlon™ X2 Dual-Core, AMD Athlon™, and AMD Sempron™ Processor
MOBO: GA-770TA-UD3 (rev. 1.0) - GIGABYTE
MOBO COOLER: Hyper 212 Plus - Cooler Master
GPU: Product section
PSU: Real Power M520 - Cooler Master
RAM: GeIL GV34GB1333C9DC prijzen | Core | Tweakers.net Pricewatch
Case: CM 690 II Advanced - Cooler Master
OS: Windows 7 Home Premium 64Bit OEM
The first problem encountered was that my mobo had bios version F2 which did not support my CPU. So when I found out after 6 hours I updated the BIOS to F3, and it worked.
I installed windows 7 and the drivers on cd from my mobo and GPU. And updated them all.
Havning encountered a few crashes here and there(bsods) during various installations and during the prosess of copying files I was supprised, but not worried.
When I started to play(Starcraft 2, which was set on Ultra) It worked fine, the first time. After that I kept encountering BSODs. So after reading a lot and using WinDBG I tried to deinstall my ATI drivers.
Which seemed to work. But then again I started to encounter "other" BSODs, during more random stuff, listing to music, trying to open a file, playing AC2.
So I decided to ask, beg you guys for help.
I attached the requested files and a zip with the error messages and dmp files after several (different) crashes.
Thanks!!!!
Titus
Sorry, but I dont speak/read German... 
I suspect ZoneAlarm is the cause. Please remove it with this tool: http://download.zonealarm.com/bin/fr..._clean.exeAlso remove AVG: http://download.avg.com/filedir/util...removerx64.exe
Install MSE instead of AVG: http://www.microsoft.com/security_essentials
Reset the Windows firewall, instead of ZoneAlarm. Open an elevated command prompt and enter netsh firewall reset.
No dumps are being created for some reason, not sure why. You may try setting your page file to "System Managed".
Install MSE instead of AVG: http://www.microsoft.com/security_essentials
Reset the Windows firewall, instead of ZoneAlarm. Open an elevated command prompt and enter netsh firewall reset.
No dumps are being created for some reason, not sure why. You may try setting your page file to "System Managed".
@tews Are the dumps in the installed language then?(it's gonna be dutch, not german 
)
@Jonathan_king
Is removing them with those tools necessary? Or is uninstalling them enough?
And I wondered, is the build in Firewall good enough? And the Same foor MSE?
Because I always thought(xp user before w7) that the window firewalls were crap. And that you always should have a antivirus from a different company then your firewall?
But THANKS for the suggestiongs, I'll await your reply about the removing thing before I go ahead and try it.
Or would a clean Install work better?
Thanks
Titus
)@Jonathan_king
Is removing them with those tools necessary? Or is uninstalling them enough?
And I wondered, is the build in Firewall good enough? And the Same foor MSE?
Because I always thought(xp user before w7) that the window firewalls were crap. And that you always should have a antivirus from a different company then your firewall?
But THANKS for the suggestiongs, I'll await your reply about the removing thing before I go ahead and try it.
Or would a clean Install work better?
Thanks
Titus
Remove them with the tools provided, to clean up all traces.
The built-in Firewall is enough, as is MSE. The Windows 7 and Vista firewalls are better than the XP one.
Although I don't find it necessary to have a different company's firewall and anti-virus, I can't really recommend other products.
If you want a paid anti-virus program, I recommend ESET 2010. I think MSE is sufficient though.
Your system is in Dutch, so that makes it a bit difficult to read if you only speak English. Fortunately, there are enough universal keywords in the report to make reading Dutch unnecessary.
The built-in Firewall is enough, as is MSE. The Windows 7 and Vista firewalls are better than the XP one.
Although I don't find it necessary to have a different company's firewall and anti-virus, I can't really recommend other products.
If you want a paid anti-virus program, I recommend ESET 2010. I think MSE is sufficient though.
Your system is in Dutch, so that makes it a bit difficult to read if you only speak English. Fortunately, there are enough universal keywords in the report to make reading Dutch unnecessary.
I did everything you said, and I'm going to try and play AC2 after I reinstalled my ATI drivers to see if I get another BSOD.
Also I wondered, there is still a AVG9 map in c programdata. Should I delete that?
Also I wondered, there is still a AVG9 map in c programdata. Should I delete that?
Go ahead and run this tool: http://download.avg.com/filedir/util...removerx64.exe
That should clean it up.
That should clean it up.
Ok so I Just got back from testing after everything was clean(ZA & AVG removed, MSE installed and ATI CCC Installed)
And it went quite well, until, yes you can guess it, a BSOD.
Here are the new files, I hope you can help me with them again.
Also, I wondered: Is there a way to change the language of the files to English, so you(and more people) could read them more easily
Thanks
Titus
EDIT!!!
I added a zip file with the SF diagnostics files, because I came across the utility.
And it went quite well, until, yes you can guess it
, a BSOD.Here are the new files, I hope you can help me with them again.
Also, I wondered: Is there a way to change the language of the files to English, so you(and more people) could read them more easily
Thanks
Titus
EDIT!!!
I added a zip file with the SF diagnostics files, because I came across the utility.
Please enable driver verifier: Driver Verifier - Enable and Disable
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Documents and Settings\JK\Desktop\Files for SF\Windows7_BSOD_jcgriff2\082410-21356-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a1e50 Debug session time: Tue Aug 24 11:01:11.654 2010 (GMT-5) System Uptime: 0 days 1:45:08.012 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800031ed415, fffff88009d76140, 0} Probably caused by : memory_corruption ( nt!MiUnmapViewOfSection+3f5 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800031ed415, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88009d76140, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt!MiUnmapViewOfSection+3f5 fffff800`031ed415 488b5138 mov rdx,qword ptr [rcx+38h] CONTEXT: fffff88009d76140 -- (.cxr 0xfffff88009d76140) rax=fffffa8003d07160 rbx=fffffa8003e77750 rcx=bffff8a00aecd000 rdx=fffffa8003bc5d75 rsi=fffffa8005548b30 rdi=fffffa8006e03580 rip=fffff800031ed415 rsp=fffff88009d76b10 rbp=000000006c3c0000 r8=fffffa8003bc5d70 r9=00000000004c1000 r10=fffff800031ed57c r11=000000000031827c r12=00000000004c1000 r13=0000000000000000 r14=000000006c880fff r15=000000006c3c0000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!MiUnmapViewOfSection+0x3f5: fffff800`031ed415 488b5138 mov rdx,qword ptr [rcx+38h] ds:002b:bffff8a0`0aecd038=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: SearchIndexer. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800031ed5db to fffff800031ed415 STACK_TEXT: fffff880`09d76b10 fffff800`031ed5db : fffff880`00000000 00000000`6c3c0000 fffffa80`00000001 fffffa80`03d07160 : nt!MiUnmapViewOfSection+0x3f5 fffff880`09d76bd0 fffff800`02ed3993 : 00000000`00000008 00000000`002e8bf0 fffffa80`05548b30 00000000`77843670 : nt!NtUnmapViewOfSection+0x5f fffff880`09d76c20 00000000`7775fffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0478f548 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7775fffa FOLLOWUP_IP: nt!MiUnmapViewOfSection+3f5 fffff800`031ed415 488b5138 mov rdx,qword ptr [rcx+38h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiUnmapViewOfSection+3f5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff88009d76140 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MiUnmapViewOfSection+3f5 BUCKET_ID: X64_0x3B_nt!MiUnmapViewOfSection+3f5 Followup: MachineOwner --------- 1: kd> lmntsm start end module name fffff880`04f9e000 fffff880`04fdc000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00e92000 fffff880`00ee9000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`06cc7000 fffff880`06cdf000 adfs adfs.SYS Thu Jun 26 16:52:37 2008 (48640195) fffff880`02d1e000 fffff880`02da8000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`0416b000 fffff880`04181000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`013e9000 fffff880`013fe000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00e86000 fffff880`00e91000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`08e71000 fffff880`08e7c000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00e53000 fffff880`00e5c000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e5c000 fffff880`00e86000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`04808000 fffff880`04f37000 atikmdag atikmdag.sys Tue Jul 06 21:37:28 2010 (4C33DA58) fffff880`040da000 fffff880`04120000 atikmpag atikmpag.sys Tue Jul 06 21:15:42 2010 (4C33D53E) fffff880`01966000 fffff880`0196e000 AtiPcie AtiPcie.sys Tue May 05 11:00:22 2009 (4A005486) fffff960`00850000 fffff960`008b1000 ATMFD ATMFD.DLL Thu May 27 00:11:31 2010 (4BFDF0F3) fffff880`01809000 fffff880`01810000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`02de6000 fffff880`02df7000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`06952000 fffff880`06970000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`006f0000 fffff960`00717000 cdd cdd.dll unavailable (00000000) fffff880`019a4000 fffff880`019ce000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00d38000 fffff880`00df8000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01936000 fffff880`01966000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00cda000 fffff880`00d38000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01000000 fffff880`01073000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`0415b000 fffff880`0416b000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`06890000 fffff880`0689e000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`018b5000 fffff880`018d3000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`02cc6000 fffff880`02cd5000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01920000 fffff880`01936000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`05ddb000 fffff880`05dfd000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`068aa000 fffff880`068b3000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`0689e000 fffff880`068aa000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`068b3000 fffff880`068c6000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`06854000 fffff880`06860000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`0426a000 fffff880`0435e000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`0435e000 fffff880`043a4000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`0111f000 fffff880`01133000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`010d3000 fffff880`0111f000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`018e6000 fffff880`01920000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff880`08ff7000 fffff880`09000000 gdrv gdrv.sys Thu Mar 12 23:22:29 2009 (49B9D175) fffff800`02e1b000 fffff800`02e64000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`043a4000 fffff880`043c8000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`08e8a000 fffff880`08ea3000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`06887000 fffff880`0688f080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`08e7c000 fffff880`08e8a000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`05c06000 fffff880`05cce000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`015e9000 fffff880`015f2000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`0413d000 fffff880`0415b000 i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00fd9000 fffff880`00ff9000 jraid jraid.sys Thu Oct 29 04:14:20 2009 (4AE94EDC) fffff880`04fe8000 fffff880`04ff7000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff800`00ba3000 fffff800`00bad000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`0404a000 fffff880`0408d000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`015ac000 fffff880`015d7000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`05c00000 fffff880`05c05200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`06925000 fffff880`0693a000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`068e1000 fffff880`06904000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00cb9000 fffff880`00cc6000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`068d3000 fffff880`068e1000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`0403b000 fffff880`0404a000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`08ea3000 fffff880`08eb0000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e39000 fffff880`00e53000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`019ce000 fffff880`019fb000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`08fe7000 fffff880`08ff7000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`06970000 fffff880`06988000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`06988000 fffff880`069b5000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`06c56000 fffff880`06ca4000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`06ca4000 fffff880`06cc7000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`0186e000 fffff880`01879000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00ef2000 fffff880`00efc000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`0113f000 fffff880`0119d000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`02cbb000 fffff880`02cc6000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`015d7000 fffff880`015e9000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`00e2f000 fffff880`00e39000 mv91cons mv91cons.sys Tue Sep 22 17:36:37 2009 (4AB94365) fffff880`0145a000 fffff880`0154c000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`041a5000 fffff880`041b1000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`041b1000 fffff880`041e0000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`05d56000 fffff880`05d6b000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02dd7000 fffff880`02de6000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02cd9000 fffff880`02d1e000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`0154c000 fffff880`015ac000 NETIO NETIO.SYS Thu Apr 08 22:43:59 2010 (4BBE946F) fffff880`01879000 fffff880`0188a000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`02caf000 fffff880`02cbb000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02e64000 fffff800`03440000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01246000 fffff880`013e9000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`01800000 fffff880`01809000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`0409f000 fffff880`040b7000 nusb3hub nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B) fffff880`043c8000 fffff880`043f8000 nusb3xhc nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C) fffff880`02db1000 fffff880`02dd7000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`04120000 fffff880`0413d000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00f3c000 fffff880`00f51000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00efc000 fffff880`00f2f000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00fc2000 fffff880`00fc9000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00fc9000 fffff880`00fd9000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`0121a000 fffff880`0122b000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`06cdf000 fffff880`06d85000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`05d9e000 fffff880`05ddb000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00cc6000 fffff880`00cda000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`01133000 fffff880`0113eae0 PxHlpa64 PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D) fffff880`04181000 fffff880`041a5000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`041e0000 fffff880`041fb000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`04000000 fffff880`04021000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`04021000 fffff880`0403b000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`02c5e000 fffff880`02caf000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`01853000 fffff880`0185c000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`0185c000 fffff880`01865000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01865000 fffff880`0186e000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`0119d000 fffff880`011d7000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`0693a000 fffff880`06952000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04200000 fffff880`04257000 Rt64win7 Rt64win7.sys Mon Mar 22 05:57:14 2010 (4BA73EFA) fffff880`05d6b000 fffff880`05d9d700 RtHDMIVX RtHDMIVX.sys Wed Dec 02 01:33:25 2009 (4B160A35) fffff880`06600000 fffff880`06853700 RTKVHD64 RTKVHD64.sys Wed Jul 28 06:01:36 2010 (4C500000) fffff880`02c4c000 fffff880`02c5e000 SCDEmu SCDEmu.SYS Sun Jan 20 02:56:57 2008 (4792FEC9) fffff880`00e00000 fffff880`00e2f000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0) fffff880`06d85000 fffff880`06d90000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`04fdc000 fffff880`04fe8000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`02c00000 fffff880`02c1d000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`0144a000 fffff880`01452000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`08f51000 fffff880`08fe7000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`08ee9000 fffff880`08f51000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`06d90000 fffff880`06dbd000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`04262000 fffff880`04263480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`06dbd000 fffff880`06dcf000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`018a8000 fffff880`018b5000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`0188a000 fffff880`018a8000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`02c38000 fffff880`02c4c000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`005d0000 fffff960`005da000 TSDDD TSDDD.dll Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`011d7000 fffff880`011fd000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`0408d000 fffff880`0409f000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`043f8000 fffff880`043f9f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`04f8d000 fffff880`04f9e000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`05cfc000 fffff880`05d56000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`04257000 fffff880`04262000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04f37000 fffff880`04f8d000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00f2f000 fffff880`00f3c000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01810000 fffff880`0181e000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`0181e000 fffff880`01843000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00f51000 fffff880`00f66000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00f66000 fffff880`00fc2000 volmgrx volmgrx.sys unavailable (00000000) fffff880`01073000 fffff880`010bf000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`02c1d000 fffff880`02c38000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`01843000 fffff880`01853000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00c00000 fffff880`00ca4000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00ca4000 fffff880`00cb3000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02da8000 fffff880`02db1000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000b0000 fffff960`003bf000 win32k win32k.sys Sat Jun 19 00:31:59 2010 (4C1C483F) fffff880`02df7000 fffff880`02e00000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00ee9000 fffff880`00ef2000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`06904000 fffff880`06925000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`08e00000 fffff880`08e71000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0686e000 fffff880`06887000 HIDCLASS.SYS Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`06860000 fffff880`0686e000 hidusb.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`068c6000 fffff880`068d3000 mouhid.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`08e00000 fffff880`08e71000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0196e000 fffff880`0197c000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0197c000 fffff880`01988000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01988000 fffff880`01991000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01991000 fffff880`019a4000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 So if my pc boots with the driver verifier enabled, it's ok? What to do next?
I'm checking not loaded drivers now aswell
And Why shouldn't I check the Microsoft Drivers?
Titus
I'm checking not loaded drivers now aswell
And Why shouldn't I check the Microsoft Drivers?
Titus
Microsoft drivers are assumed to be stable, so there is no point in stressing them. It will just slow down your computer.
The way Verifier works, it stresses all drivers checked, in hopes of causing them to BSOD. When it happens, we can look at the dump and hopefully find the cause.
Just use your computer normally while Verifier is running, but don't start anything that you can't afford to lose in a BSOD.
The way Verifier works, it stresses all drivers checked, in hopes of causing them to BSOD. When it happens, we can look at the dump and hopefully find the cause.
Just use your computer normally while Verifier is running, but don't start anything that you can't afford to lose in a BSOD.
"After a reboot, driver verifier should be enabled."
Ok, so what I did last time was what the topic said, and rebooting went fine(is that the clear sign, or am I supposed to use my computer during the time the verifier is on?
What I also did was during the driver selection, I clicked on "show not loaded drivers" and selected them all except the windows and the 2 named.
Then I couldn't reboot. During signing out it gave a BSOD(c1).
My guess is that I wasn't supposed to check the not loaded drivers, so what I'll do NOW is reboot again with only the loaded drivers selected. brb
EDIT:
back after a reboot. No problems so far. What I'll do NOW is play a game with driver verification on until my system crashes.
Or is there something else I should test?
Thanks
Ok, so what I did last time was what the topic said, and rebooting went fine(is that the clear sign, or am I supposed to use my computer during the time the verifier is on?
What I also did was during the driver selection, I clicked on "show not loaded drivers" and selected them all except the windows and the 2 named.
Then I couldn't reboot. During signing out it gave a BSOD(c1).
My guess is that I wasn't supposed to check the not loaded drivers, so what I'll do NOW is reboot again with only the loaded drivers selected. brb
EDIT:
back after a reboot. No problems so far. What I'll do NOW is play a game with driver verification on until my system crashes.
Or is there something else I should test?
Thanks
Just use your system just as you normally would. Play whatever games you normally play, go to the sites you normally do, and pretend Verifier is not running.
So the next BSOD is the Data Jackpot :P ?
If it's a driver issue you're having, then hopefully yes.
If the dump still doesn't point to a specific cause, we can then assume it is either a hardware problem, or low-level driver.
If the dump still doesn't point to a specific cause, we can then assume it is either a hardware problem, or low-level driver.
Ok, I got my BSOD. Not really at a nice time though:
I was getting ready for bed and wanted to shut my computer down. So I Clicked Shutdown.
And it was shutting down and BOOF, BSOD.
So I can't seem to shutdown xD Because the system will reboot after the BSOD xD
Here are the Files:
Thanks for looking into this again
I was getting ready for bed and wanted to shut my computer down. So I Clicked Shutdown.
And it was shutting down and BOOF, BSOD.
So I can't seem to shutdown xD Because the system will reboot after the BSOD xD
Here are the Files:
Thanks for looking into this again
I've experienced the same BSOD's as you and struggled for a couple months until I found the problem. I suspect the culprit in your case, as it was in mine, is the Gigabyte GA-770TA-UD3 M/B itself!
After 3 weeks of random BSOD's with a new system last Spring, I ended up RMA'ing the RAM, which didn't help. Finally received Gigabyte RMA authorization and returned the board. Week and half later, got it back with no explanantion. After calling, I was told they couldn't find anything wrong with it. Spoke with the manager and convinced them to allow a board replacement. When the new one arrived, it worked fine for a day and half but guess what, starting spitting out BSOD's and random restarts.
Long story short, I just ended up replacing the M/B with a MSI 790X-G45 and have run two weeks of torture tests without a single hiccup... it's been perfect!
Check out the Newegg customer satisfaction reviews and you'll see many reports of the same issue. Some have "fixed" their boards by raising the Northbridge voltage by 0.1 volts (directly from Gigabyte technician), while others have raised their PCIx and Vcor by .15 -.25 volts. But in my particular case, it didn't help.
Always liked their products but will never buy another one of these boards. If you got the resources, run, don't walk and replace the board. You'll hopefully save yourself a lot of headaches down the road.
After 3 weeks of random BSOD's with a new system last Spring, I ended up RMA'ing the RAM, which didn't help. Finally received Gigabyte RMA authorization and returned the board. Week and half later, got it back with no explanantion. After calling, I was told they couldn't find anything wrong with it. Spoke with the manager and convinced them to allow a board replacement. When the new one arrived, it worked fine for a day and half but guess what, starting spitting out BSOD's and random restarts.
Long story short, I just ended up replacing the M/B with a MSI 790X-G45 and have run two weeks of torture tests without a single hiccup... it's been perfect!
Check out the Newegg customer satisfaction reviews and you'll see many reports of the same issue. Some have "fixed" their boards by raising the Northbridge voltage by 0.1 volts (directly from Gigabyte technician), while others have raised their PCIx and Vcor by .15 -.25 volts. But in my particular case, it didn't help.
Always liked their products but will never buy another one of these boards. If you got the resources, run, don't walk and replace the board. You'll hopefully save yourself a lot of headaches down the road.
@BWpotter, that sounds very scary! I don't want my mobo to be, well broken
@jonathan_king
I Decided to stress my system a little by running a benchmark(performance test by passmark.com). And it gave me another 3B crash.
Here are the files
@jonathan_king
I Decided to stress my system a little by running a benchmark(performance test by passmark.com). And it gave me another 3B crash.
Here are the files
Looks like Gigabyte's Dynamic Energy Saver Advanced program is the cause here, not the first time by any means.
Please remove it, and see what happens.
Please remove it, and see what happens.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\Downloads\Documents\Windows7_BSOD_jcgriff2\082510-21528-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`03047e50 Debug session time: Tue Aug 24 18:23:45.054 2010 (UTC - 4:00) System Uptime: 0 days 3:24:45.083 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C1, {fffff9802f1c8ff0, fffff9802f1c8ffc, 2d000c, 24} Unable to load image \??\C:\Windows\gdrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for gdrv.sys *** ERROR: Module load completed but symbols could not be loaded for gdrv.sys Probably caused by : gdrv.sys ( gdrv+30c7 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: fffff9802f1c8ff0, address trying to free Arg2: fffff9802f1c8ffc, address where bits are corrupted Arg3: 00000000002d000c, (reserved) Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten Debugging Details: ------------------ BUGCHECK_STR: 0xC1_24 SPECIAL_POOL_CORRUPTION_TYPE: 24 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: essvr.exe CURRENT_IRQL: 1 IRP_ADDRESS: fffff9802c380f3b LAST_CONTROL_TRANSFER: from fffff80002f81843 to fffff80002e7a740 STACK_TEXT: fffff880`06d0d4f8 fffff800`02f81843 : 00000000`000000c1 fffff980`2f1c8ff0 fffff980`2f1c8ffc 00000000`002d000c : nt!KeBugCheckEx fffff880`06d0d500 fffff800`02fad356 : fffff800`02e0a000 00000000`20206f49 ffffffff`ffef7148 fffffa80`04e24200 : nt!MmFreeSpecialPool+0x383 fffff880`06d0d630 fffff800`02e99d9e : 00000000`00000000 fffff980`2c380fb0 fffff980`2c380ee0 fffff980`2c380fb0 : nt!ExDeferredFreePool+0xf13 fffff880`06d0d6e0 fffff800`02e7d0dd : fffff980`2c380fb3 fffff800`00000001 00000000`00000001 fffff880`00000005 : nt!IopCompleteRequest+0x5ce fffff880`06d0d7b0 fffff800`0331a19f : fffff980`2c380ee0 fffffa80`07556400 fffff980`2c380f00 00000000`00000000 : nt!IopfCompleteRequest+0x75d fffff880`06d0d890 fffff880`07d710c7 : fffff880`07d71a50 00000000`00000008 00000000`00000000 fffff980`2c380fb0 : nt!IovCompleteRequest+0x19f fffff880`06d0d960 fffff880`07d71a50 : 00000000`00000008 00000000`00000000 fffff980`2c380fb0 00000000`00000001 : gdrv+0x30c7 fffff880`06d0d968 00000000`00000008 : 00000000`00000000 fffff980`2c380fb0 00000000`00000001 00000000`00000000 : gdrv+0x3a50 fffff880`06d0d970 00000000`00000000 : fffff980`2c380fb0 00000000`00000001 00000000`00000000 00000000`00000001 : 0x8 STACK_COMMAND: kb FOLLOWUP_IP: gdrv+30c7 fffff880`07d710c7 ?? ??? SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: gdrv+30c7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: gdrv IMAGE_NAME: gdrv.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49b9d175 FAILURE_BUCKET_ID: X64_0xC1_24_VRF_gdrv+30c7 BUCKET_ID: X64_0xC1_24_VRF_gdrv+30c7 Followup: MachineOwner --------- Just deinstalled it, didn't need it anyway.
The question is, I have to Reboot now. My guess is I'll get the crash on shutdown again(the C1 one)
I'll let you know in a sec
The question is, I have to Reboot now. My guess is I'll get the crash on shutdown again(the C1 one)
I'll let you know in a sec
I'm not surprised at all, if that program is the cause, due to the nature of the BSODs. I should have noticed that program earlier, and had you uninstall it. 
BSOD on reboot(C1: Special pool detected memory corruption). Just after signing out, during "shutting down"
Files:
I'm going to run the performance test from passmark again to check if the 3B is gone.
EDIT: 3b is gone. C1 remains
I've got a feeling we are almost there. The one problem that remains is the shut down BSOD
Which occurred after I went messing with the driver verifier(by checking the drivers that were not loaded aswell).
Any ideas on this C1? THANKS!
Files:
I'm going to run the performance test from passmark again to check if the 3B is gone.
EDIT: 3b is gone. C1 remains
I've got a feeling we are almost there. The one problem that remains is the shut down BSOD
Which occurred after I went messing with the driver verifier(by checking the drivers that were not loaded aswell).
Any ideas on this C1? THANKS!
Got a new batch of BSOD's for you
What about a system recovery to before I started using Driver verifier?
Before that I never had the 1C...
Well I'm getting crazy! What could it be, what test could I run? THANKS
Titus
What about a system recovery to before I started using Driver verifier?
Before that I never had the 1C...
Well I'm getting crazy! What could it be, what test could I run? THANKS
Titus
Download the latest drivers for your video card ... ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) ... http://www.ati.com/
Code:
.... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {411, fffff6fcc005cc30, 1d400000a2e378c2, bffff6fcc005cc31} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+35e705 ) Followup: MachineOwner --------- This one:?
Display Driver Only (?) 50.9MB 10.7 7/26/2010
I am using CCC atm to get full screen with my hdmi cable :O Well, i'll see. Next 1A BSOD, it's byebye ati CCC
Thanks
Display Driver Only (?) 50.9MB 10.7 7/26/2010
I am using CCC atm to get full screen with my hdmi cable :O Well, i'll see. Next 1A BSOD, it's byebye ati CCC
Thanks
another BSOD. Is it still CCC?
Thanks
Thanks
New kind of BSOD: "A"
Files:
Files:
Bsod while idle(was even afk)
I see three crashes, 2 of which occurred while using the internet.
Update your Realtek drivers: Realtek
Enable driver verifier: Driver Verifier - Enable and Disable
...Summary of the Dumps:
Update your Realtek drivers: Realtek
Enable driver verifier: Driver Verifier - Enable and Disable
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Aug 26 19:56:58.512 2010 (UTC - 4:00) System Uptime: 0 days 0:59:01.870 BugCheck 1A, {411, fffff68000064998, f6d00000c989b824, bffff68000064999} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6051 ) BUGCHECK_STR: 0x1a_411 PROCESS_NAME: MsMpEng.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Aug 26 15:43:53.430 2010 (UTC - 4:00) System Uptime: 0 days 4:01:28.428 BugCheck A, {28, 2, 0, fffff80002ed0518} Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 ) BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Aug 26 11:41:50.028 2010 (UTC - 4:00) System Uptime: 0 days 1:09:15.386 BugCheck 3B, {c0000005, fffff960000f840e, fffff8800863dcf0, 0} Probably caused by : win32k.sys ( win32k!HmgShareLock+72 ) BUGCHECK_STR: 0x3B PROCESS_NAME: uTorrent.exe �������������������������������������������������������������������������������������� Yeah, I didn't know if you had a 100 or 1000 card.
If you're sure you have a 100 card, install this driver: Realtek
I think you have a 1000 though: Realtek
You can install both if you like, perhaps only 1 will actually install.
If you're sure you have a 100 card, install this driver: Realtek
I think you have a 1000 though: Realtek
You can install both if you like, perhaps only 1 will actually install.
Another BSOD playing starcraft 2 with skype. That just doesn't seem to work. Single player does, but multi...
I have Ati CCC removed and my realtech lan drivers updated...
Any Idea's? It's software, not hardware?
EDIT: Another other bsod, during browsing/chatting
files are named "BSOD 3D"
I have Ati CCC removed and my realtech lan drivers updated...
Any Idea's? It's software, not hardware?
EDIT: Another other bsod, during browsing/chatting
files are named "BSOD 3D"
Now it's getting crazy 
: While watching a video podcast on the internet I got a 1A BSOD:
Files:
Please Also look at my previous post
: While watching a video podcast on the internet I got a 1A BSOD:Files:
Please Also look at my previous post
Your .dmp file still shows the same video driver as the cause of your crashes... Did you ever update them??
Code:
.... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {411, fffff6fcc005cc30, 1d400000a2e378c2, bffff6fcc005cc31} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+35e705 ) Followup: MachineOwner --------- Yeah I did, I uninstalled ATI CCC and installed the driver from the site you provided.
Perhaps an older driver could work?
That's the 1A BSOD
I also got 3D 3B,
Wait, I got another BSOD file coming, 7B
Perhaps an older driver could work?
That's the 1A BSOD
I also got 3D 3B,
Wait, I got another BSOD file coming, 7B
�� Quote: Originally Posted by iTitus 
Yeah I did, I uninstalled ATI CCC and installed the driver from the site you provided.
Perhaps an older driver could work?
That's the 1A BSOD
I also got 3D 3B,
Wait, I got another BSOD file coming, 7B
Perhaps an older driver could work?
That's the 1A BSOD
I also got 3D 3B,
Wait, I got another BSOD file coming, 7B
Did you use the un-install tool from ati?
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Ken is spot on, as usual, make certain that the old ones are completely removed before reinstalling ...
Thanks for the assist Ken...
Thanks for the assist Ken...
I sweeped it with Guru3D and installed the new.
Now I have 2 non bsod problems:
My max resolution is 1400x1050 iso 1920x1080
and there is a black border arround my screen.
I think this is because I installed the driver only and not CCC(which was the instruction right?)
And I still have these others BSODS besides 1A, the 3B, 3D, and 7F:
Now I have 2 non bsod problems:
My max resolution is 1400x1050 iso 1920x1080
and there is a black border arround my screen.
I think this is because I installed the driver only and not CCC(which was the instruction right?)
And I still have these others BSODS besides 1A, the 3B, 3D, and 7F:
The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. ... Before we can go any further, make sure that you have followed Kens' instructions for replacing your video driver...
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff80002eb8948} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {411, fffff6fc50017650, 834000007e95f882, bffff6fc50017651} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6051 ) Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff88002ffd110, 0, 0, fffff880049b037d} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+ea37d ) Followup: MachineOwner --------- What about the skype crash?
And about what ken said:
I Did, but as stated I have the following new problems:
My max resolution is 1400x1050 iso 1920x1080
and there is a black border arround my screen.
I Installed the 2nd download from this page:
http://sites.amd.com/us/game/downloa...n-win7-64.aspx
Was Ati CCC really a problem? Or just the driver, which was updated like yesterday?
Because with CCC I didn't have these troubles
I'll try and play some games to see if I still get errors now with thes strange resolutions
Thanks for still taking time to help me!
And about what ken said:
I Did, but as stated I have the following new problems:
My max resolution is 1400x1050 iso 1920x1080
and there is a black border arround my screen.
I Installed the 2nd download from this page:
http://sites.amd.com/us/game/downloa...n-win7-64.aspx
Was Ati CCC really a problem? Or just the driver, which was updated like yesterday?
Because with CCC I didn't have these troubles
I'll try and play some games to see if I still get errors now with thes strange resolutions
Thanks for still taking time to help me!
Ever since I cleared the drivers with the GURU3d tool, I can't install new ones
It "installs" fine, but there are some errors, but there arn't and then nothing is installed ...
It "installs" fine, but there are some errors, but there arn't and then nothing is installed ...
Ok I'm thinking about a clean install.
Just windows 7 64bit again.
Then some drivers and programs. But I'd like to "ask" for permission with each driver/software, so I won't blindly install, lets say avg+zoneAlarm, or Easysaver from gigabyte.
So the current list of drivers/programs is:
-CCC 10.8?
-the latest MSE?
-The latest Realteck LAN drivers, found here in the topic)
Then which of my mobo drivers?
GA-770TA-UD3 (rev. 1.0) - GIGABYTE
Then:
-The latest Opera?
-Starcraft II and Skype? To test if the BSOD's still remain?
If there are BSODs, testing with a minimal amount of drivers/software would help, I guess.
If there are no BSOD's I'll start installing the software I like to use(google talk, adobe, flashplugin, windows live, Ccleaner, java runtime, PowerIso, Mediamonkey, Klite codex, Gomplayer, uTorrent, MS Office 2003, and the things I forgot)
My questions to you are:
-Is a clean install a good idea here(given the fact that i've got the time and nothing to lose)
-Is the list of drivers/software complete/correct?
Thanks!
Titus
Just windows 7 64bit again.
Then some drivers and programs. But I'd like to "ask" for permission with each driver/software, so I won't blindly install, lets say avg+zoneAlarm, or Easysaver from gigabyte.
So the current list of drivers/programs is:
-CCC 10.8?
-the latest MSE?
-The latest Realteck LAN drivers, found here in the topic)
Then which of my mobo drivers?
GA-770TA-UD3 (rev. 1.0) - GIGABYTE
Then:
-The latest Opera?
-Starcraft II and Skype? To test if the BSOD's still remain?
If there are BSODs, testing with a minimal amount of drivers/software would help, I guess.
If there are no BSOD's I'll start installing the software I like to use(google talk, adobe, flashplugin, windows live, Ccleaner, java runtime, PowerIso, Mediamonkey, Klite codex, Gomplayer, uTorrent, MS Office 2003, and the things I forgot)
My questions to you are:
-Is a clean install a good idea here(given the fact that i've got the time and nothing to lose)
-Is the list of drivers/software complete/correct?
Thanks!
Titus
Let windows install the basic drivers... test for stability .. install the other programs one by one ... test for stability ... once you have a stable install, create a system image of your drive... Backup Complete Computer - Create an Image Backup.. Then install a game and see how it goes..
But uhm, so
install windows
create image
test stability(how?)
install the drivers/programs I mentioned first
test stability(how?)
create image
install game to test stability
So how to test stability if you only got windows?
install windows
create image
test stability(how?)
install the drivers/programs I mentioned first
test stability(how?)
create image
install game to test stability
So how to test stability if you only got windows?
Reinstalled windows
MSE
Opera
Ati CCC 10.8
No BSOD so far. Going to install Starcraft II and play
MSE
Opera
Ati CCC 10.8
No BSOD so far. Going to install Starcraft II and play
�� Quote: Originally Posted by iTitus I sweeped it with Guru3D and installed the new.
Now I have 2 non bsod problems:
My max resolution is 1400x1050 iso 1920x1080
and there is a black border arround my screen.
I think this is because I installed the driver only and not CCC(which was the instruction right?)
And I still have these others BSODS besides 1A, the 3B, 3D, and 7F:
Now I have 2 non bsod problems:
My max resolution is 1400x1050 iso 1920x1080
and there is a black border arround my screen.
I think this is because I installed the driver only and not CCC(which was the instruction right?)
And I still have these others BSODS besides 1A, the 3B, 3D, and 7F:
Yet again, these point to your video driver and memory. It could be your video driver corrupting memory of the other way around.
remove the video driver completely again
run memory test
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
run a system file check
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
If this doesnt identify and or repair the problem we will need to run driver verifier
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\082810-20467-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03091e50 Debug session time: Sat Aug 28 06:53:24.438 2010 (GMT-4) System Uptime: 0 days 0:06:55.827 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff88002ffd110, 0, 0, fffff880049b037d} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+ea37d ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff88002ffd110 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff880049b037d Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0x3D PROCESS_NAME: System CURRENT_IRQL: b EXCEPTION_RECORD: fffff88002ffd8a8 -- (.exr 0xfffff88002ffd8a8) ExceptionAddress: fffff880049b037d (atikmdag+0x00000000000ea37d) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002ffd950 -- (.trap 0xfffff88002ffd950) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000190 rbx=0000000000000000 rcx=bffff88006370000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880049b037d rsp=fffff88002ffdae0 rbp=fffff88002ffdc70 r8=0000000000000000 r9=0000000000000000 r10=fffff9800164af90 r11=00000000002f9d00 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc atikmdag+0xea37d: fffff880`049b037d f30f6f04c1 movdqu xmm0,xmmword ptr [rcx+rax*8] ds:1ea0:bffff880`06370c80=???????????????????????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ec3ca9 to fffff80002ec4740 STACK_TEXT: fffff880`02ffc858 fffff800`02ec3ca9 : 00000000`0000003d fffff880`02ffd110 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff880`02ffc860 fffff800`02ebffe9 : fffff800`031ac000 fffff880`040ed000 fffff880`02ffd110 fffff800`02ef1668 : nt!KiBugCheckDispatch+0x69 fffff880`02ffc9a0 fffff800`02eea40d : fffff880`04076150 fffff880`0405a610 fffff880`04037000 fffff880`02ffd8a8 : nt!KiInterruptHandler+0x29 fffff880`02ffc9d0 fffff800`02ef1a90 : fffff800`0301391c fffff880`02ffca48 fffff880`02ffd8a8 fffff800`02e54000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02ffca00 fffff800`02efe9ef : fffff880`02ffd8a8 fffff880`02ffd110 fffff880`00000000 fffffa80`0692e000 : nt!RtlDispatchException+0x410 fffff880`02ffd0e0 fffff800`02ec3d82 : fffff880`02ffd8a8 fffffa80`0692ec50 fffff880`02ffd950 00000000`00000001 : nt!KiDispatchException+0x16f fffff880`02ffd770 fffff800`02ec268a : fffffa80`06d8e1a0 fffff880`042e92c5 fffffa80`06d8e1a0 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`02ffd950 fffff880`049b037d : fffffa80`06d77b30 fffff800`02e0f71f fffffa80`0557f870 fffff880`049b012c : nt!KiGeneralProtectionFault+0x10a fffff880`02ffdae0 fffffa80`06d77b30 : fffff800`02e0f71f fffffa80`0557f870 fffff880`049b012c fffffa80`06401ea0 : atikmdag+0xea37d fffff880`02ffdae8 fffff800`02e0f71f : fffffa80`0557f870 fffff880`049b012c fffffa80`06401ea0 fffffa80`04fb3d70 : 0xfffffa80`06d77b30 fffff880`02ffdaf0 fffff880`049a3aa0 : fffffa80`00000000 fffffa80`0692e000 fffff880`02ffdc70 00000000`00000001 : hal!HalBuildScatterGatherList+0x2f3 fffff880`02ffdb60 fffffa80`00000000 : fffffa80`0692e000 fffff880`02ffdc70 00000000`00000001 fffffa80`05329b60 : atikmdag+0xddaa0 fffff880`02ffdb68 fffffa80`0692e000 : fffff880`02ffdc70 00000000`00000001 fffffa80`05329b60 fffff880`0491b187 : 0xfffffa80`00000000 fffff880`02ffdb70 fffff880`02ffdc70 : 00000000`00000001 fffffa80`05329b60 fffff880`0491b187 fffff880`02fd5180 : 0xfffffa80`0692e000 fffff880`02ffdb78 00000000`00000001 : fffffa80`05329b60 fffff880`0491b187 fffff880`02fd5180 fffffa80`0646b9c0 : 0xfffff880`02ffdc70 fffff880`02ffdb80 fffffa80`05329b60 : fffff880`0491b187 fffff880`02fd5180 fffffa80`0646b9c0 00000000`0000681f : 0x1 fffff880`02ffdb88 fffff880`0491b187 : fffff880`02fd5180 fffffa80`0646b9c0 00000000`0000681f 00000000`00000000 : 0xfffffa80`05329b60 fffff880`02ffdb90 fffff880`02fd5180 : fffffa80`0646b9c0 00000000`0000681f 00000000`00000000 fffff880`02fd5180 : atikmdag+0x55187 fffff880`02ffdb98 fffffa80`0646b9c0 : 00000000`0000681f 00000000`00000000 fffff880`02fd5180 fffff880`0403c265 : 0xfffff880`02fd5180 fffff880`02ffdba0 00000000`0000681f : 00000000`00000000 fffff880`02fd5180 fffff880`0403c265 fffff880`0110f000 : 0xfffffa80`0646b9c0 fffff880`02ffdba8 00000000`00000000 : fffff880`02fd5180 fffff880`0403c265 fffff880`0110f000 fffffa80`06d8e1a0 : 0x681f STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+ea37d fffff880`049b037d f30f6f04c1 movdqu xmm0,xmmword ptr [rcx+rax*8] SYMBOL_STACK_INDEX: 8 SYMBOL_NAME: atikmdag+ea37d FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c33da58 FAILURE_BUCKET_ID: X64_0x3D_VRF_atikmdag+ea37d BUCKET_ID: X64_0x3D_VRF_atikmdag+ea37d Followup: MachineOwner --------- Code:
PxHlpa64.sys fffff880`01093000 fffff880`0109eae0 0x0000bae0 0x475dd06d 12/10/2007 19:49:01 adfs.SYS fffff880`04671000 fffff880`04689000 0x00018000 0x48640195 6/26/2008 16:52:37 AtiPcie.sys fffff880`019ae000 fffff880`019b6000 0x00008000 0x4a005486 5/5/2009 11:00:22 spldr.sys fffff880`018d1000 fffff880`018d9000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 amdxata.sys fffff880`00c5c000 fffff880`00c67000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
I did a clean install without BSOD's so far. Can I install DirectX 11?
Ok guys, my first BSOD in my clean install. Playing offline starcraft II. Yesterday night it seemed fine. The BSOD's always seem to start in the morning...
Installed:
windows 7(and updates including windows live)
MSE
Ati CCC 10.8
latest realtech lan drivers
opera
Ccleaner
SIW
Winrar(after bsod, to zip it)
Gotto be in there... Here are the files
Thanks!
Installed:
windows 7(and updates including windows live)
MSE
Ati CCC 10.8
latest realtech lan drivers
opera
Ccleaner
SIW
Winrar(after bsod, to zip it)
Gotto be in there... Here are the files
Thanks!
Honestly, I have to suspect hardware.
Test RAM: RAM - Test with Memtest86+
Test CPU: http://www.sevenforums.com/tutorials...t-prime95.html
Be sure to report the temps Speedfan reports.
Test hard drive: HD Diagnostic
Test GFX card: Video Card - Stress Test with Furmark
Report the results of the tests, and we'll see where we're at.
Test RAM: RAM - Test with Memtest86+
Test CPU: http://www.sevenforums.com/tutorials...t-prime95.html
Be sure to report the temps Speedfan reports.
Test hard drive: HD Diagnostic
Test GFX card: Video Card - Stress Test with Furmark
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\_jcgriff2_\dbug\__Kernel__\082910-19063-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Mini Kernel Dump does not have process information Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0285c000 PsLoadedModuleList = 0xfffff800`02a99e50 Debug session time: Sun Aug 29 05:21:18.106 2010 (UTC - 4:00) System Uptime: 0 days 0:24:58.464 Loading Kernel Symbols ............................................ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff80002906948} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 2: kd> !analyze -v;lmtsmn;.bugcheck;.logclose;q ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002906948 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 EXCEPTION_RECORD: fffff8800378b588 -- (.exr 0xfffff8800378b588) .exr 0xfffff8800378b588 ExceptionAddress: fffff800028f99bf (nt!RtlDispatchException+0x000000000000033f) ExceptionCode: 10000001 ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 TRAP_FRAME: fffff8800378b630 -- (.trap 0xfffff8800378b630) .trap 0xfffff8800378b630 NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000050 rbx=0000000000000000 rcx=fffff800028f99a3 rdx=bffff88003790d70 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800028f99bf rsp=fffff8800378b7c0 rbp=000000000000029b r8=0000000000000006 r9=0000000000000837 r10=fffff88003790c20 r11=fffff8800378b808 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po nc nt!RtlDispatchException+0x33f: fffff800`028f99bf 488b02 mov rax,qword ptr [rdx] ds:3340:bffff880`03790d70=???????????????? .trap Resetting default scope LAST_CONTROL_TRANSFER: from fffff800028cbca9 to fffff800028cc740 STACK_TEXT: fffff880`02d69d68 fffff800`028cbca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`02d69d70 fffff800`028ca172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`02d69eb0 fffff800`02906948 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 fffff880`0378adc0 fffff800`028cbd82 : fffff880`0378b588 00000000`00000001 fffff880`0378b630 fffff800`0285c000 : nt!KiDispatchException+0xc8 fffff880`0378b450 fffff800`028ca68a : 00000000`0007000b 00000000`00001988 00000000`0007001c 00000000`00001808 : nt!KiExceptionDispatch+0xc2 fffff880`0378b630 fffff800`028f99bf : fffff800`028cb99b fffff880`0378b808 fffff880`0378c668 fffff800`0285c000 : nt!KiGeneralProtectionFault+0x10a fffff880`0378b7c0 fffff800`029069ef : fffff880`0378c668 fffff880`0378bed0 fffff880`00000000 fffff800`00000004 : nt!RtlDispatchException+0x33f fffff880`0378bea0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`028ca172 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner --------- start end module name fffff880`00e00000 fffff880`00e57000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`00eeb000 fffff880`00ef6000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`00fc8000 fffff880`00fd1000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00fd1000 fffff880`00ffb000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`011ca000 fffff880`011fa000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d05000 fffff880`00d63000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`010d1000 fffff880`01144000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`013e1000 fffff880`013f7000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`0105f000 fffff880`01073000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`01013000 fffff880`0105f000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`013d7000 fffff880`013e1000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`00dbf000 fffff880`00df9000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`015ad000 fffff880`015f7000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02813000 fffff800`0285c000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`01412000 fffff880`0141b000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff800`00ba7000 fffff800`00bb1000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`013ac000 fffff880`013c6000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01582000 fffff880`015ad000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`00ce4000 fffff880`00cf1000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`00fae000 fffff880`00fc8000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00e60000 fffff880`00e6a000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01073000 fffff880`010d1000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`01400000 fffff880`01412000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01430000 fffff880`01522000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`01522000 fffff880`01582000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff800`0285c000 fffff800`02e38000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01209000 fffff880`013ac000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`00eaa000 fffff880`00ebf000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e6a000 fffff880`00e9d000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00ed4000 fffff880`00edb000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00edb000 fffff880`00eeb000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013c6000 fffff880`013d7000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`00cf1000 fffff880`00d05000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`01190000 fffff880`011ca000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`015f7000 fffff880`015ff000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) 4f5a020a`66653fa1 4f5a020a`a41dd105 Unknown_Module_4f5a020a_66653fa1 Unknown_Module_4f5a020a`66653fa1 unavailable (00000000) fffff880`00e9d000 fffff880`00eaa000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`00ebf000 fffff880`00ed4000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d63000 fffff880`00dbf000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01144000 fffff880`01190000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`00efb000 fffff880`00f9f000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f9f000 fffff880`00fae000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00e57000 fffff880`00e60000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) Bugcheck code 0000007F Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`02906948 �������������������������������������������������������������������������������������� Ok, I'm going to test my hardware. I really hope I can find something.
In the mean time, I got another BSOD for you, a 7E this time:
Files
In the mean time, I got another BSOD for you, a 7E this time:
Files
The dump points to your video card. If you have another one you can try, please do so.
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88004fa6cee, fffff880021bd6a8, fffff880021bcf10} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 ) �������������������������������������������������������������������������������������� I'm stress testing my GPU now, almost 10 minutes: No strange things yet, temp is steady at 68 degrees Celcius. How long should I let it run?
I Don't have another GPU lying arround. Could it be the fact that my directx is still 9.0c atm?
I Don't have another GPU lying arround. Could it be the fact that my directx is still 9.0c atm?
More likely the card is older, so more likely to have problems.
Do you have on-board graphics you can use, and remove your other video card?
Do you have on-board graphics you can use, and remove your other video card?
No onboard graphics. The card is a Club 3D Ati Radeon HD 5770. Not that old.
Ran the test 20 minutes. Steady 69 degrees. With highest burn settings etc.
About the HDD testing, my samsung hdd isn't noted at the supported hdd's for that test: Samsung Spinpoint F3 HD103SJ, 1TB
SAMSUNG Hard Disk Drive - support - utilities
Run that test anyway or another test?
I'm updating to directx 11 and testing it with SC II again first.
Ran the test 20 minutes. Steady 69 degrees. With highest burn settings etc.
About the HDD testing, my samsung hdd isn't noted at the supported hdd's for that test: Samsung Spinpoint F3 HD103SJ, 1TB
SAMSUNG Hard Disk Drive - support - utilities
Run that test anyway or another test?
I'm updating to directx 11 and testing it with SC II again first.
3B Bsod while uninstalling CCC and trying to install drivers only
I'm going to run these memtests etc
Files:
I'm going to run these memtests etc
Files:
8 hours later, 9 passes later, 0 errors later. I guess the memory is fine.
I'll run prime95 overnight. Is it safe to let it run while you're not there?
Also I wondered which HDD Test to run, given the fact that my hdd isn't noted in the samsung support list for their utility?
I'll run prime95 overnight. Is it safe to let it run while you're not there?
Also I wondered which HDD Test to run, given the fact that my hdd isn't noted in the samsung support list for their utility?
started prime95. temps are either 35 or 44, not sure which one is cpu.
letting it run little more then 12 hours from now.
what to test after that?(memtest86 9 passes with 2x2gb ram installed in the correct slots: 0 errors)
letting it run little more then 12 hours from now.
what to test after that?(memtest86 9 passes with 2x2gb ram installed in the correct slots: 0 errors)
I have to recommend purchasing a new video card, or having the PC shop test/replace the card.
...Summary of the Dumps:
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Aug 29 06:06:41.180 2010 (UTC - 4:00) System Uptime: 0 days 0:44:47.844 BugCheck 1000007E, {ffffffffc0000005, fffff88004fa6cee, fffff880021bd6a8, fffff880021bcf10} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 ) PROCESS_NAME: System BUGCHECK_STR: 0x7E �������������������������������������������������������������������������������������� Ran Prime95 overnight, almost 15 hours. no errors I could detect.
Max temp 38 or 45, dunno which sensor is cpu.
I got another BSOD: 1E
You say it's my gpu? I'll RMA it. Should I get "the same" or a totally other one?
Any idea's on which one would be ok?
Thanks
Max temp 38 or 45, dunno which sensor is cpu.
I got another BSOD: 1E
You say it's my gpu? I'll RMA it. Should I get "the same" or a totally other one?
Any idea's on which one would be ok?
Thanks
That last one points to a totally different issue, and it looks like it may have something to do with RainMeter (WinRing0x64.sys). I'd ignore it for now, and worry about the video card issue first. The last dump appears totally unrelated.
I just ran Unigine heaven benchmark with almost max settings(only not full tesselation) and no BSOD whatever, max temp 60 degrees. I don't know, but I can torture my GPU pretty hard...
So how to test whether it seriously is my GPU? Install one of the first drivers or what?
So how to test whether it seriously is my GPU? Install one of the first drivers or what?
I googled a bit and found out that there are MANY users with a HD5770+win7 64bit with randoms bsods... No one has a solution yet -_-
�� Quote: Originally Posted by iTitus I googled a bit and found out that there are MANY users with a HD5770+win7 64bit with randoms bsods... No one has a solution yet -_-
While they may appear random they in fact are not. There is a cause and usually a cure. If it is caused by hardware you may have to replace pieces to find which.
Ken J
I Disabled Cool and Quiet because I read somewhere that it would cause random bsods aswell. No result.
Running SC2 gives solid crashes(something that was not 100% sure before the clean install...)
Also I encountered another random crash while I was watching something on the internet.
What tests are there left other then exchanging parts(can test my GPU in another pc on friday and test another gpu in this pc on monday)?
Memtest 9 passes was clear(2x2 gb in slots 1 and 2, with dual channel. Didn't test other configurations, is that something I might test?)
15 hours of prime95 held fine
furmark and heaven benchmark ran fine with max temp of 69c and 60c
Thanks for the hardware test help and the BSOD analysis
Didn't check hdd though, because I didn't know how.
Running SC2 gives solid crashes(something that was not 100% sure before the clean install...)
Also I encountered another random crash while I was watching something on the internet.
What tests are there left other then exchanging parts(can test my GPU in another pc on friday and test another gpu in this pc on monday)?
Memtest 9 passes was clear(2x2 gb in slots 1 and 2, with dual channel. Didn't test other configurations, is that something I might test?)
15 hours of prime95 held fine
furmark and heaven benchmark ran fine with max temp of 69c and 60c
Thanks for the hardware test help and the BSOD analysis
Didn't check hdd though, because I didn't know how.
I still suspect it's your motherboard. A well documented issue appears to be the design were the M/B isn't supplying enough power to the video card through the Northbridge circuit. While individual components, memory, cpu, etc check out fine via hardware tests, inadequate power to the Video card during regular operation causes random freezes, BSODS, and restarts.
Try raising the Northbridge voltage 0.1V to 1.2V (this was suggested by a Gigabyte tech). Also, you may want to try a combination of higher voltages for the memory (1.6V), and PCIx and Vcor voltages by as much as 0.25V.
Try raising the Northbridge voltage 0.1V to 1.2V (this was suggested by a Gigabyte tech). Also, you may want to try a combination of higher voltages for the memory (1.6V), and PCIx and Vcor voltages by as much as 0.25V.
Hi BWPotter,
I'll be testing another gpu tomorrow, both a nvidia(6700XL) and an ati one(unknown, because it's from a friend).
If those tests still BSOD, it's clear it's the mobo I guess. If those pass, it's almost sure it's the GPU. Although if these cards decide that the inadequate power is enough, i'll still not be able to find the cause.
Could you help me with a little tutorial/link on how to raise those voltages?
I Added a screen from SIW with my voltages. But I think it's not on there...
And do you have a link from the topic/email where the gigabyte guys suggested it?
Thanks
I'll be testing another gpu tomorrow, both a nvidia(6700XL) and an ati one(unknown, because it's from a friend).
If those tests still BSOD, it's clear it's the mobo I guess. If those pass, it's almost sure it's the GPU. Although if these cards decide that the inadequate power is enough, i'll still not be able to find the cause.
Could you help me with a little tutorial/link on how to raise those voltages?
I Added a screen from SIW with my voltages. But I think it's not on there...
And do you have a link from the topic/email where the gigabyte guys suggested it?
Thanks
Took 1 memory stick out and tried to play starcraft 2. It seemed to work, so I put it in again:
some crash, outside starcraft 2.
Gonna try it in starcraft 2 one more time. If it crashes I'll memtest overnight, this time with 1 stick, and all slots
files:
some crash, outside starcraft 2.
Gonna try it in starcraft 2 one more time. If it crashes I'll memtest overnight, this time with 1 stick, and all slots
files:
oh sweet, a RAM issue, i've seen so ,SO many people having trouble with 2x2GB ram. 4x1 - OK , 2x2 - BAD, 4x2 - OK. What about dram:fsb ratio? without bottlenecks, there is a lesser chance of bsodding.
Try installing these older ATI drivers: https://a248.e.akamai.net/f/674/9206...win7_64_dd.exe
Be sure to remove your current ones with Driver Sweeper first.
...Summary of the Dumps:
Be sure to remove your current ones with Driver Sweeper first.
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 31 19:03:43.172 2010 (UTC - 4:00) System Uptime: 0 days 0:02:08.530 BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) BUGCHECK_STR: 0x1E_0 PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 31 18:06:59.724 2010 (UTC - 4:00) System Uptime: 0 days 2:45:40.722 BugCheck 3B, {c0000005, fffff8800411e22a, fffff88007551480, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+be ) BUGCHECK_STR: 0x3B PROCESS_NAME: dwm.exe �������������������������������������������������������������������������������������� Well, with 2 sticks of ram I did encounter a crash, but not during starcraft :O
I REALLY don�t know what to do or how to test. I got my old GPU here, Nvidia 6700XL I think i�ll pop it in and see what happens...
I REALLY don�t know what to do or how to test. I got my old GPU here, Nvidia 6700XL I think i�ll pop it in and see what happens...
�� Quote: Originally Posted by iTitus Well, with 2 sticks of ram I did encounter a crash, but not during starcraft :O
I REALLY don�t know what to do or how to test. I got my old GPU here, Nvidia 6700XL I think i�ll pop it in and see what happens...
I REALLY don�t know what to do or how to test. I got my old GPU here, Nvidia 6700XL I think i�ll pop it in and see what happens...
I Worked with my old GPU till it crashed, uploading data now, after that I'll swap GPU's and work/game till next(?) crash.
Try installing these Marvell storage drivers: http://download.gigabyte.eu/FileList...arvell_mru.exe
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\_jcgriff2_\dbug\__Kernel__\090110-31512-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50 Debug session time: Wed Sep 1 12:21:17.869 2010 (UTC - 4:00) System Uptime: 0 days 2:39:27.227 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : raspppoe.sys ( raspppoe!MpIndicatePacketOnCall+12b ) Followup: MachineOwner --------- 0: kd> !analyze -v;lmtsmn;.bugcheck;.logclose;q ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +6666383164353266 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff80000ba2b38 -- (.exr 0xfffff80000ba2b38) .exr 0xfffff80000ba2b38 ExceptionAddress: fffff80002a84905 (nt!ExpInterlockedPopEntrySListFault16) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff80000ba2be0 -- (.trap 0xfffff80000ba2be0) .trap 0xfffff80000ba2be0 NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000a057f000d rbx=0000000000000000 rcx=fffffa80039bde30 rdx=bffffa80053a85a1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a84905 rsp=fffff80000ba2d70 rbp=0000000000000008 r8=bffffa80053a85a0 r9=0000000000000000 r10=fffffa80039bde30 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!ExpInterlockedPopEntrySListFault16: fffff800`02a84905 498b08 mov rcx,qword ptr [r8] ds:0001:bffffa80`053a85a0=???????????????? .trap Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a7946e to fffff80002a81710 STACK_TEXT: fffff800`00ba1c28 fffff800`02a7946e : fffffa80`04c05000 fffffa80`064f19b0 fffff800`00ba23a0 fffff800`02aae668 : nt!KeBugCheck fffff800`00ba1c30 fffff800`02aa740d : fffff800`02c8fb7c fffff800`02bc9e84 fffff800`02a11000 fffff800`00ba2b38 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`00ba1c60 fffff800`02aaea90 : fffff800`02bd0a40 fffff800`00ba1cd8 fffff800`00ba2b38 fffff800`02a11000 : nt!RtlpExecuteHandlerForException+0xd fffff800`00ba1c90 fffff800`02abb9ef : fffff800`00ba2b38 fffff800`00ba23a0 fffff800`00000000 fffffa80`00000003 : nt!RtlDispatchException+0x410 fffff800`00ba2370 fffff800`02a80d82 : fffff800`00ba2b38 00000000`00000000 fffff800`00ba2be0 fffffa80`046f1adc : nt!KiDispatchException+0x16f fffff800`00ba2a00 fffff800`02a7f68a : fffffa80`04afd0c0 fffffa80`0648d930 fffffa80`04afd0c0 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff800`00ba2be0 fffff800`02a84905 : 00000000`00000000 fffff800`02a913fb fffffa80`044aeca8 fffffa80`0553e1a0 : nt!KiGeneralProtectionFault+0x10a fffff800`00ba2d70 fffff800`02a913fb : fffffa80`044aeca8 fffffa80`0553e1a0 fffff800`00ba2e98 fffffa80`044aebc0 : nt!ExpInterlockedPopEntrySListFault16 fffff800`00ba2d80 fffff880`014f354b : fffffa80`06601640 fffff880`04268110 fffff800`00ba2e00 fffffa80`046f1adc : nt!IoAllocateMdl+0x7b fffff800`00ba2dd0 fffff880`0426d737 : fffff880`042692c0 fffffa80`04c435a0 00000000`0000005e 00000000`00000002 : ndis!NdisCopyBuffer+0x4b fffff800`00ba2e20 fffff880`0426ea0b : fffffa80`04154010 01cb49f1`b4c00983 fffffa80`c0000001 fffffa80`03f2e0b0 : raspppoe!MpIndicatePacketOnCall+0x12b fffff800`00ba2e80 fffff880`04264ff1 : fffff880`042693a0 fffff880`042693a0 00000000`00000000 fffff880`042693a0 : raspppoe!MpIndicateReceivedPackets+0xab fffff800`00ba2ec0 fffff800`02a8cbfc : fffff800`02bfbe80 fffff800`00095b9f fffff880`042693a0 00000000`0000009f : raspppoe!TimerEvent+0x13d fffff800`00ba2f00 fffff800`02a87865 : 00000000`00000000 fffffa80`03bf1060 00000000`00000000 fffff880`04264eb4 : nt!KiRetireDpcList+0x1bc fffff800`00ba2fb0 fffff800`02a8767c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 fffff880`0772eaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: raspppoe!MpIndicatePacketOnCall+12b fffff880`0426d737 eb15 jmp raspppoe!MpIndicatePacketOnCall+0x142 (fffff880`0426d74e) SYMBOL_STACK_INDEX: a SYMBOL_NAME: raspppoe!MpIndicatePacketOnCall+12b FOLLOWUP_NAME: MachineOwner MODULE_NAME: raspppoe IMAGE_NAME: raspppoe.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcce9 FAILURE_BUCKET_ID: X64_0x1E_0_raspppoe!MpIndicatePacketOnCall+12b BUCKET_ID: X64_0x1E_0_raspppoe!MpIndicatePacketOnCall+12b Followup: MachineOwner --------- start end module name fffff880`04333000 fffff880`04371000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00ed6000 fffff880`00f2d000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02c96000 fffff880`02d20000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`043d7000 fffff880`043ed000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`0121b000 fffff880`01230000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00fe4000 fffff880`00fef000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`088a6000 fffff880`088b1000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00fdb000 fffff880`00fe4000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00c00000 fffff880`00c2a000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`0486e000 fffff880`04fdc000 atikmdag atikmdag.sys Tue Aug 03 21:39:08 2010 (4C58C4BC) fffff880`04073000 fffff880`040ba000 atikmpag atikmpag.sys Tue Aug 03 21:15:45 2010 (4C58BF41) fffff880`01997000 fffff880`0199e000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`02def000 fffff880`02e00000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`0474b000 fffff880`04769000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00690000 fffff960`006b7000 cdd cdd.dll unavailable (00000000) fffff880`01937000 fffff880`01961000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00cc5000 fffff880`00d85000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`018d1000 fffff880`01901000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00c67000 fffff880`00cc5000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01000000 fffff880`01073000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`043c7000 fffff880`043d7000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`05da2000 fffff880`05db0000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`02c77000 fffff880`02c95000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`02c68000 fffff880`02c77000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`018bb000 fffff880`018d1000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`05d7a000 fffff880`05d9c000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`05dbc000 fffff880`05dc5000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05db0000 fffff880`05dbc000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05dc5000 fffff880`05dd8000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`05c18000 fffff880`05c24000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`040ba000 fffff880`041ae000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`04800000 fffff880`04846000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01139000 fffff880`0114d000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`010ed000 fffff880`01139000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`01211000 fffff880`0121b000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01881000 fffff880`018bb000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`0148b000 fffff880`014d5000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02fed000 fffff800`03036000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`04846000 fffff880`0486a000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`05ce1000 fffff880`05d3d000 HdAudio HdAudio.sys Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`05de6000 fffff880`05dff000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`05c00000 fffff880`05c08080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`05dd8000 fffff880`05de6000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`04683000 fffff880`0474b000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`015ed000 fffff880`015f6000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`0439a000 fffff880`043b8000 i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`043b8000 fffff880`043c7000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff800`00bb9000 fffff800`00bc3000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`041ae000 fffff880`041f1000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`013e3000 fffff880`013fd000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01460000 fffff880`0148b000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`05d9c000 fffff880`05da1200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`05c55000 fffff880`05c6a000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`05c32000 fffff880`05c55000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c46000 fffff880`00c53000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`05c24000 fffff880`05c32000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`042b5000 fffff880`042c4000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`05c0b000 fffff880`05c18000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00fc1000 fffff880`00fdb000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`01961000 fffff880`0198e000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`04623000 fffff880`04633000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`04769000 fffff880`04781000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`04781000 fffff880`047ae000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`047ae000 fffff880`047fc000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`04600000 fffff880`04623000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`01800000 fffff880`0180b000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00f36000 fffff880`00f40000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`0114d000 fffff880`011ab000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`02c5d000 fffff880`02c68000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`015db000 fffff880`015ed000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`014e9000 fffff880`015db000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04224000 fffff880`04230000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`04230000 fffff880`0425f000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`05ccc000 fffff880`05ce1000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02d94000 fffff880`02da3000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02d20000 fffff880`02d65000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`0180b000 fffff880`0181c000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`02c51000 fffff880`02c5d000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02a11000 fffff800`02fed000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01240000 fffff880`013e3000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`0198e000 fffff880`01997000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`02d6e000 fffff880`02d94000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`0437d000 fffff880`0439a000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00f80000 fffff880`00f95000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00f40000 fffff880`00f73000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00faa000 fffff880`00fb1000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00fb1000 fffff880`00fc1000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`01200000 fffff880`01211000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`06e07000 fffff880`06ead000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`05d3d000 fffff880`05d7a000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c53000 fffff880`00c67000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`04200000 fffff880`04224000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0425f000 fffff880`0427a000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`0427a000 fffff880`0429b000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`0429b000 fffff880`042b5000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`02c00000 fffff880`02c51000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`019e1000 fffff880`019ea000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`019ea000 fffff880`019f3000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`019f3000 fffff880`019fc000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`011ab000 fffff880`011e5000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`04fe7000 fffff880`04fff000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04000000 fffff880`04056000 Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95) fffff880`06ead000 fffff880`06eb8000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`04371000 fffff880`0437d000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`02da3000 fffff880`02dc0000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`014dd000 fffff880`014e4000 speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798) fffff880`014d5000 fffff880`014dd000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`06f5f000 fffff880`06ff5000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`06ef7000 fffff880`06f5f000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`06eb8000 fffff880`06ee5000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`042c4000 fffff880`042c5480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01601000 fffff880`017fe000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`06ee5000 fffff880`06ef7000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`0183a000 fffff880`01847000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`0181c000 fffff880`0183a000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`02ddb000 fffff880`02def000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`004b0000 fffff960`004ba000 TSDDD TSDDD.dll unavailable (00000000) fffff880`01847000 fffff880`0186d000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`043ed000 fffff880`043ff000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`05c09000 fffff880`05c0af00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`04322000 fffff880`04333000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`05c72000 fffff880`05ccc000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`04fdc000 fffff880`04fe7000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`042cc000 fffff880`04322000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00f73000 fffff880`00f80000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`0199e000 fffff880`019ac000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`019ac000 fffff880`019d1000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00f95000 fffff880`00faa000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d85000 fffff880`00de1000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01073000 fffff880`010bf000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`02dc0000 fffff880`02ddb000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`019d1000 fffff880`019e1000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00e23000 fffff880`00ec7000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00ec7000 fffff880`00ed6000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02d65000 fffff880`02d6e000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00080000 fffff960`0038f000 win32k win32k.sys unavailable (00000000) fffff880`0186d000 fffff880`01876000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00f2d000 fffff880`00f36000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`01901000 fffff880`01922000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`08835000 fffff880`088a6000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00071000 fffff880`01901000 fffff880`0190f000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000E000 fffff880`0190f000 fffff880`0191b000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000C000 fffff880`0191b000 fffff880`01924000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00009000 fffff880`01924000 fffff880`01937000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00013000 Bugcheck code 0000001E Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 Installed marvell drivers, switched GPU, installed nvidia drivers, going to play starcraft 2 to test
Data Jackpot: ?
Got a BSOD with my old nvidia gpu playing starcraft 2.
Files:
Got a BSOD with my old nvidia gpu playing starcraft 2.
Files:
I'm still true to ram issue.
Going to test today:
Delete and sweep nvidia drivers
insert and install the 5770 ati card.
take 1 memory stick out
play SC2 till it crashes
(optional)post dump
remove memory stick, and insert the other one
play SC2 till it crashes
(optional) post dump
If I found a faulty ram stick(the 2 sticks passed 9 passes memtest together) rma it.
But Could it be the problem someone described, with 2 modules(1=fine and 4=fine).
Would that be a mem issue or a mobo issue?
Would a new mobo, new ram, or extra ram help then?
Delete and sweep nvidia drivers
insert and install the 5770 ati card.
take 1 memory stick out
play SC2 till it crashes
(optional)post dump
remove memory stick, and insert the other one
play SC2 till it crashes
(optional) post dump
If I found a faulty ram stick(the 2 sticks passed 9 passes memtest together) rma it.
But Could it be the problem someone described, with 2 modules(1=fine and 4=fine).
Would that be a mem issue or a mobo issue?
Would a new mobo, new ram, or extra ram help then?
If it's a RAM issue, a memory test should (but not guaranteed) identify it.
See this Memtest tutorial: RAM - Test with Memtest86+
Also, test with Prime95 too, except select Blend. Here is the Prime95 tut: http://www.sevenforums.com/tutorials...t-prime95.html
See this Memtest tutorial: RAM - Test with Memtest86+
Also, test with Prime95 too, except select Blend. Here is the Prime95 tut: http://www.sevenforums.com/tutorials...t-prime95.html
I Did the memtest with 9 passes, with the 2 ram sticks sitting in slots 1 and 2
Should I test them seperatly?
Should I test them seperatly?
No, if either of them has errors, a test on both should show it.
Try the Prime95 test.
Try the Prime95 test.
Uhm something strange:
With my old GPU my bios boots in full screen
with my new GPU my bios boots in almost full screen(little border arround the screen)
? Going to test sc2 with 1 memstick
With my old GPU my bios boots in full screen
with my new GPU my bios boots in almost full screen(little border arround the screen)
? Going to test sc2 with 1 memstick
Great, or not Results:
With just one ram stick, I played starcraft 2 for 2 hours no problemo.
So it seems to be a ram issue I guess? I could test the other ram stick aswell. But @Zipsi how could I solve this? Buy 2 extra ram sticks?
Or is it a motherbord issue, by not supplying enough voltage or something?
With just one ram stick, I played starcraft 2 for 2 hours no problemo.
So it seems to be a ram issue I guess? I could test the other ram stick aswell. But @Zipsi how could I solve this? Buy 2 extra ram sticks?
Or is it a motherbord issue, by not supplying enough voltage or something?
Try playing with only the other stick in. If you get BSODs, we can figure it's a bad stick, in which case you should purchase or RMA a new kit.
try gaming an hour with 1 stick only, if nothing happens.. do the same with other stick.. if thats okay too then I guess they don't communicate well. You could try putting them in asynchronous mode in bios, then they wont try to "compete" against eachother and cause bsods.
Since I no longer have the Gigabyte 770, I can't give you exact step-by-step instructions on how to raise the voltages in the BIOS. However, you should be able to ID the parameters by going into CPU/Memory section, probably in the Advance category, and deselecting the auto controls for these items.
The Northbridge voltage, if memory serves me correctly is auto-set at 1.1V; Raise it manually to 1.2V (a Gigabyte technician suggested this to me over the phone). The PCIx, RAM, and CPU core voltages would all be adjusted manually in a similar fashion. Try raising your RAM to 1.6V (stock is 1.5V) and increase the PCIx and Vcor voltages in small increments (0.02-0.05V) in-till the system becomes stable.
Also, if you're clocking your RAM to 1600, I would recommend relaxing it to 1333 at 9-9-9-24 timings for testing purposes until to achieve system stability.
�� Quote: Originally Posted by iTitus
The Northbridge voltage, if memory serves me correctly is auto-set at 1.1V; Raise it manually to 1.2V (a Gigabyte technician suggested this to me over the phone). The PCIx, RAM, and CPU core voltages would all be adjusted manually in a similar fashion. Try raising your RAM to 1.6V (stock is 1.5V) and increase the PCIx and Vcor voltages in small increments (0.02-0.05V) in-till the system becomes stable.
Also, if you're clocking your RAM to 1600, I would recommend relaxing it to 1333 at 9-9-9-24 timings for testing purposes until to achieve system stability.
�� Quote: Originally Posted by iTitus Hi BWPotter,
I'll be testing another gpu tomorrow, both a nvidia(6700XL) and an ati one(unknown, because it's from a friend).
If those tests still BSOD, it's clear it's the mobo I guess. If those pass, it's almost sure it's the GPU. Although if these cards decide that the inadequate power is enough, i'll still not be able to find the cause.
Could you help me with a little tutorial/link on how to raise those voltages?
I Added a screen from SIW with my voltages. But I think it's not on there...
And do you have a link from the topic/email where the gigabyte guys suggested it?
Thanks
I'll be testing another gpu tomorrow, both a nvidia(6700XL) and an ati one(unknown, because it's from a friend).
If those tests still BSOD, it's clear it's the mobo I guess. If those pass, it's almost sure it's the GPU. Although if these cards decide that the inadequate power is enough, i'll still not be able to find the cause.
Could you help me with a little tutorial/link on how to raise those voltages?
I Added a screen from SIW with my voltages. But I think it's not on there...
And do you have a link from the topic/email where the gigabyte guys suggested it?
Thanks
Now I really don't know what to do xD:
I Played Starcraft with the other ram stick. Really fine, a little slow(just like with the other stick), but no crashes or what ever.
So I was satisfied and decided to quit starcraft and let you guys know. Only Starcraft wouldn't shutdown, so I CTRL ALT DEL'ed it and ended the process, at that moment My PC BSODed.
What do you guys think? I think it could either be a mobo issue, something with voltages, or a ram issue, something with either channels or the fact that 2 ram sticks doesn't work.
What can I do to test either? Put the mem into different channels, not enableling dual channel? Buy an extra set RAM and test with 4? RMA something, either mobo or ram, raise voltages or something, or buy a new mobo?
Thanks!
EDIT@!!!
Just had a crash, after posting this, during browsing etc, Perhaps this is a bad memory stick...
I'm leaving for home for the weekend, should I turn memtest on for the weekend, or should I bring the ram home and send it RMA to the company I got it from? In that case, they will have to find the problem too, otherwise they'll just return it and demand �20,-
EDIT2:
Another crash, I mailed both GEIL and the company who sold the RAM to me to see what their idea is
Files are updated:
I Played Starcraft with the other ram stick. Really fine, a little slow(just like with the other stick), but no crashes or what ever.
So I was satisfied and decided to quit starcraft and let you guys know. Only Starcraft wouldn't shutdown, so I CTRL ALT DEL'ed it and ended the process, at that moment My PC BSODed.
What do you guys think? I think it could either be a mobo issue, something with voltages, or a ram issue, something with either channels or the fact that 2 ram sticks doesn't work.
What can I do to test either? Put the mem into different channels, not enableling dual channel? Buy an extra set RAM and test with 4? RMA something, either mobo or ram, raise voltages or something, or buy a new mobo?
Thanks!
EDIT@!!!
Just had a crash, after posting this, during browsing etc, Perhaps this is a bad memory stick...
I'm leaving for home for the weekend, should I turn memtest on for the weekend, or should I bring the ram home and send it RMA to the company I got it from? In that case, they will have to find the problem too, otherwise they'll just return it and demand �20,-
EDIT2:
Another crash, I mailed both GEIL and the company who sold the RAM to me to see what their idea is
Files are updated:
Returning the RAM or motherboard may be necessary, there are a couple of things to check and try first.
I don't recommend running memtest86+ or Prime95 for that long.
What were the CPU temperatures during the tests?
D/L and run Core Temp during any testing and/or gaming until this issue is resolved.
Let's try adjusting the north bridge voltage (NB).
First down load and run CPUZ, post a snip of the memory and SPD tabs.
For snipping tool, start button> in the search box enter 'Snipping tool'>enter
How to Post a Screenshot in Seven Forums
Down load your motherboard manual: GA-770TA-UD3 Manual
Read the '2-3 MB Intelligent Tweaker(M.I.T.)' page 38, and 'System Voltage Optimized' page 42, sections.
When ready, post back with exactly what you have done and any questions you might have.
I don't recommend running memtest86+ or Prime95 for that long.
What were the CPU temperatures during the tests?
D/L and run Core Temp during any testing and/or gaming until this issue is resolved.
Let's try adjusting the north bridge voltage (NB).
First down load and run CPUZ, post a snip of the memory and SPD tabs.
For snipping tool, start button> in the search box enter 'Snipping tool'>enter
How to Post a Screenshot in Seven Forums
Down load your motherboard manual: GA-770TA-UD3 Manual
Read the '2-3 MB Intelligent Tweaker(M.I.T.)' page 38, and 'System Voltage Optimized' page 42, sections.
When ready, post back with exactly what you have done and any questions you might have.
Thanks for the fast reply, I fear that I don;t understand the snipping thing, but here are the memory and spd tabs:
Quick reply.
The windows 7 snipping tool will take a snapshot of the desktop area you select, right click and select the area to copy, save to convenient location.
To open the snipping tool, click the start button, in the search box type 'snipping tool' it will come up on the list, press enter, it will open.
Let me have a look at this and do some checking.
If you have your motherboard manual, read the sections mentioned in the above post.
Edit:
What BIOS version are you running?
You can check the CPUZ mainboard tab.
The windows 7 snipping tool will take a snapshot of the desktop area you select, right click and select the area to copy, save to convenient location.
To open the snipping tool, click the start button, in the search box type 'snipping tool' it will come up on the list, press enter, it will open.
Let me have a look at this and do some checking.
If you have your motherboard manual, read the sections mentioned in the above post.
Edit:
What BIOS version are you running?
You can check the CPUZ mainboard tab.
I Read the manual, and I can't find the snipping tool xD
Seriously it doesn't come up..
I'll be going home for the weekend, so take your time. I'll be back at Sunday.
Thanks!
btw, you think raising some voltages will help? And won't void any warranties?
Seriously it doesn't come up..
I'll be going home for the weekend, so take your time. I'll be back at Sunday.
Thanks!
btw, you think raising some voltages will help? And won't void any warranties?
Actually Dave, these are the values from with just one, the "correct" RAM stick.
I'll reboot with the 2 sticks in it and post the voltages then, before I leave for home
I'll reboot with the 2 sticks in it and post the voltages then, before I leave for home
What is your BIOS version, check the CPUZ mainboard tab?
There is a good chance that it will help, sounds like unstable RAM. Since it passed memtest86+, the likely problem is inadequate NB voltage, or possibly DRAM voltage. Usually a small bump on the NB will help.
Try looking for the Snipping tool, start button > All Programs > Accessories folder > Snipping Tool
It lets you select what you want to post, which will make it easier to read.
Edit:
The info on the RAM is fine. Just need the current settings, and JEDEC settings.
Your RAM is running at JEDEC#5, 1366, 666MHz.
Should be fine at that setting.
Can you also check the NB and DRAM voltage in BIOS.
This info will give me enough to go on, I can check for issues and have some info when you get back.
There is a good chance that it will help, sounds like unstable RAM. Since it passed memtest86+, the likely problem is inadequate NB voltage, or possibly DRAM voltage. Usually a small bump on the NB will help.
Try looking for the Snipping tool, start button > All Programs > Accessories folder > Snipping Tool
It lets you select what you want to post, which will make it easier to read.
Edit:
The info on the RAM is fine. Just need the current settings, and JEDEC settings.
Your RAM is running at JEDEC#5, 1366, 666MHz.
Should be fine at that setting.
Can you also check the NB and DRAM voltage in BIOS.
This info will give me enough to go on, I can check for issues and have some info when you get back.
I found it, under the dutch name :P
I did all windows of CPU-Z, this time with 2 RAM sticks.
Bios is F3(had to flash it from F2 to F3 to get my CPU to be supported and work)
What about dual channel en (un)ganged mode? And what about all bios power saving settings etc(like cool and quiet and C1E or something like that?)
EDIT: Rebooting now for NB and DRAM voltages
Files:
I did all windows of CPU-Z, this time with 2 RAM sticks.
Bios is F3(had to flash it from F2 to F3 to get my CPU to be supported and work)
What about dual channel en (un)ganged mode? And what about all bios power saving settings etc(like cool and quiet and C1E or something like that?)
EDIT: Rebooting now for NB and DRAM voltages
Files:
Just let me know the NB and DRAM voltages, I'll check for issues and will let you know if any of these need to be changed.
It should Run in Dual channel, the NB bump should help the stability.
Check with me or someone here before you change any voltages, RAM is the easiest component to burn up.
Sometimes the power saving functions can affect the system, but it's not likely in your case.
It should Run in Dual channel, the NB bump should help the stability.
Check with me or someone here before you change any voltages, RAM is the easiest component to burn up.
Sometimes the power saving functions can affect the system, but it's not likely in your case.
Ok here are the voltages and 2 questions, and then i'm really off for my train :P
I set System Voltage Control to manual, in order to see the voltages.
DRAM: 1,5V
DDR VTT: 0,75
NB:1,1V
NB PCIE: 1,8V
Normal CPU Core: 1,45V
1st
When the problems would be solved, I had a clean install of windows in mind. With some programs I didn't install now to cut down driver issues etc. And without some other programs I installed for removing drivers etc.
Would you recommend the clean install before we start working on the Voltages, or is it totally seperated from the install?
2nd
I'm also having trouble connecting to the internet with my LAN cable. I make connection through a PPPOE connection. But Sometimes I can't logon or what ever(as the only one in the building) And some guy said it could be a mobo issue. Could it be related? Or is this something totally else(It worked fine before last clean install...)
Thank you very much for taking time to help me, I really hope you're on to something!!
I got a train to catch, I can talk with you during the weekend, but not with data of this computer or such. I'll be back here sunday afternoon.
Thanks again!
Titus
I set System Voltage Control to manual, in order to see the voltages.
DRAM: 1,5V
DDR VTT: 0,75
NB:1,1V
NB PCIE: 1,8V
Normal CPU Core: 1,45V
1st
When the problems would be solved, I had a clean install of windows in mind. With some programs I didn't install now to cut down driver issues etc. And without some other programs I installed for removing drivers etc.
Would you recommend the clean install before we start working on the Voltages, or is it totally seperated from the install?
2nd
I'm also having trouble connecting to the internet with my LAN cable. I make connection through a PPPOE connection. But Sometimes I can't logon or what ever(as the only one in the building) And some guy said it could be a mobo issue. Could it be related? Or is this something totally else(It worked fine before last clean install...)
Thank you very much for taking time to help me, I really hope you're on to something!!
I got a train to catch, I can talk with you during the weekend, but not with data of this computer or such. I'll be back here sunday afternoon.
Thanks again!
Titus
OK, we'll adjust the voltage when you get back.
Just post here and I'll get a notification.
Have a good weekend.
1st,
Let's try the voltage adjustment first, maybe a clean install if the issues persist.
2nd,
There is a BIOS update for that, it's a beta version so you can try it, at some risk.
There is an interesting test done on your motherboard and AMD Phenom II x6 1090T BE CPU concerning RAM with speeds above 1333Mhz.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Edit: And, AMD�s Phenom II AM3 has memory problems
As mentioned here, it is recommended to run in single channel mode (un-ganged) if you are setting your RAM above 1333MHZ.
This is due to the integrated memory controller in the CPU.
Just post here and I'll get a notification.
Have a good weekend.
1st,
Let's try the voltage adjustment first, maybe a clean install if the issues persist.
2nd,
There is a BIOS update for that, it's a beta version so you can try it, at some risk.
There is an interesting test done on your motherboard and AMD Phenom II x6 1090T BE CPU concerning RAM with speeds above 1333Mhz.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Edit: And, AMD�s Phenom II AM3 has memory problems
As mentioned here, it is recommended to run in single channel mode (un-ganged) if you are setting your RAM above 1333MHZ.
This is due to the integrated memory controller in the CPU.
Hi Dave, I read your post and had some questions:
1st, No matter whether we get a stable system without a clean install, I would like to do a clean install anyway(for myself etc, nog for performance). So would you recommend to do it prior to the voltage adjustments, so the system we'll be testing will be a more "realistic" system, with programs like Adobe CS4 running etc and other things(although I use Starcraft 2 on max atm as a crash tester)
2nd
what are the risks of installing a beta bios, crashes? In that case it would be better not to install it yet.
3rd
I was reading your link and I have memory running at 1333Mhz, the module simply is 1333Mhz, so that should be cool right? And what about this:
Does that mean that when/if I buy 2 more 2gb RAM sticks at 1333Mhz they will cause trouble? Or am I mixing up different names(DIMM DDR3 etc?)
4th
Given the fact that I ran starcraft 2 no problem with one RAM stick in slot 1(let's call this ram stick 1), but encountered crashes with the other RAM stick(stick 2) in slot 1, couldn't there just be one broken one, instead of something wrong with the Voltages on NB?
I'm not sceptical about raising voltages or something, I would love to try and see if it works. It's just that I got a email from the company where I bought them replying on my question on what to do and test to see whether my RAM is broken, saying that it might just be better just to return them and that they will supply new ones. So I guess that if raising voltages doesnt work this should, that is if it's the ram and not something else(the mobo).
5th
Raising voltages won't "break" anything, giving the company a excuse not to except the RMA?
Thanks again,
I'm looking forward to Sunday. A working system would be a great birthday gift for my 18th birthday monday
1st, No matter whether we get a stable system without a clean install, I would like to do a clean install anyway(for myself etc, nog for performance). So would you recommend to do it prior to the voltage adjustments, so the system we'll be testing will be a more "realistic" system, with programs like Adobe CS4 running etc and other things(although I use Starcraft 2 on max atm as a crash tester)
2nd
what are the risks of installing a beta bios, crashes? In that case it would be better not to install it yet.
3rd
I was reading your link and I have memory running at 1333Mhz, the module simply is 1333Mhz, so that should be cool right? And what about this:
Quote:
The Phenom II only supports 1333MHz DDR3�at least, officially�with a single DIMM in each memory channel. With four DDR3 DIMMs, 1066MHz is the standard. Such limitations are nothing new, of course. Previous Phenoms have long supported 1066MHz DDR2 memory, but only with a single DIMM per channel.
4th
Given the fact that I ran starcraft 2 no problem with one RAM stick in slot 1(let's call this ram stick 1), but encountered crashes with the other RAM stick(stick 2) in slot 1, couldn't there just be one broken one, instead of something wrong with the Voltages on NB?
I'm not sceptical about raising voltages or something, I would love to try and see if it works. It's just that I got a email from the company where I bought them replying on my question on what to do and test to see whether my RAM is broken, saying that it might just be better just to return them and that they will supply new ones. So I guess that if raising voltages doesnt work this should, that is if it's the ram and not something else(the mobo).
5th
Raising voltages won't "break" anything, giving the company a excuse not to except the RMA?
Thanks again,
I'm looking forward to Sunday. A working system would be a great birthday gift for my 18th birthday monday
�� Quote: Originally Posted by iTitus Hi Dave, I read your post and had some questions:
1st, No matter whether we get a stable system without a clean install, I would like to do a clean install anyway(for myself etc, nog for performance). So would you recommend to do it prior to the voltage adjustments, so the system we'll be testing will be a more "realistic" system, with programs like Adobe CS4 running etc and other things(although I use Starcraft 2 on max atm as a crash tester)
1st, No matter whether we get a stable system without a clean install, I would like to do a clean install anyway(for myself etc, nog for performance). So would you recommend to do it prior to the voltage adjustments, so the system we'll be testing will be a more "realistic" system, with programs like Adobe CS4 running etc and other things(although I use Starcraft 2 on max atm as a crash tester)
�� Quote: Originally Posted by iTitus 2nd
what are the risks of installing a beta bios, crashes? In that case it would be better not to install it yet.
what are the risks of installing a beta bios, crashes? In that case it would be better not to install it yet.
It's better to keep the variables to a minimum, especially since it's still beta, so would be better to do this after the RAM is sorted.
�� Quote: Originally Posted by iTitus 3rd
I was reading your link and I have memory running at 1333Mhz, the module simply is 1333Mhz, so that should be cool right? And what about this:
Does that mean that when/if I buy 2 more 2gb RAM sticks at 1333Mhz they will cause trouble? Or am I mixing up different names(DIMM DDR3 etc?)
I was reading your link and I have memory running at 1333Mhz, the module simply is 1333Mhz, so that should be cool right? And what about this:
Quote:
The Phenom II only supports 1333MHz DDR3�at least, officially�with a single DIMM in each memory channel. With four DDR3 DIMMs, 1066MHz is the standard. Such limitations are nothing new, of course. Previous Phenoms have long supported 1066MHz DDR2 memory, but only with a single DIMM per channel.
It says that it will work at 1333MHz in single channel mode, which would be slots 1 & 3 or Slots 2 & 4.
They stated that using unganged was more stable for 1600MHz.
Try the RAM in these slots and see if it makes a difference.
Should be no problem, in single channel mode, according to that test.
The 1600MHz was unstable and difficult to setup and run, two sticks at 1333MHz should be ok.
AMD Phenom� II Processor Model Number and Feature Comparisons
Quote:
Type of Memory Supported
Support for unregistered DIMMs up to PC2 8500(DDR2-1066MHz) and PC3 10600 (DDR3-1333MHz)
Support for unregistered DIMMs up to PC2 8500(DDR2-1066MHz) and PC3 10600 (DDR3-1333MHz)
According to this information, it should work in dual channel mode, but try single channel mode to see if it helps.
If you get two more sticks, total four, you will have to run your RAM at 1066MHz.
/Edit
�� Quote: Originally Posted by iTitus 4th
Given the fact that I ran starcraft 2 no problem with one RAM stick in slot 1(let's call this ram stick 1), but encountered crashes with the other RAM stick(stick 2) in slot 1, couldn't there just be one broken one, instead of something wrong with the Voltages on NB?
I'm not sceptical about raising voltages or something, I would love to try and see if it works. It's just that I got a email from the company where I bought them replying on my question on what to do and test to see whether my RAM is broken, saying that it might just be better just to return them and that they will supply new ones. So I guess that if raising voltages doesnt work this should, that is if it's the ram and not something else(the mobo).
Given the fact that I ran starcraft 2 no problem with one RAM stick in slot 1(let's call this ram stick 1), but encountered crashes with the other RAM stick(stick 2) in slot 1, couldn't there just be one broken one, instead of something wrong with the Voltages on NB?
I'm not sceptical about raising voltages or something, I would love to try and see if it works. It's just that I got a email from the company where I bought them replying on my question on what to do and test to see whether my RAM is broken, saying that it might just be better just to return them and that they will supply new ones. So I guess that if raising voltages doesnt work this should, that is if it's the ram and not something else(the mobo).
Did you run stick 2 in another slot?
To confirm, run stick 2 in another slot, run memtest86+. If you get any errors, stop the test and RMA the RAM, both sticks so they can send you a new matched pair.
Did the memtest86+ pass with both sticks?
It is possible that the NB bump will solve this, but even a small incompatibility may cause problems if later you want to add more RAM.
�� Quote: Originally Posted by iTitus 5th
Raising voltages won't "break" anything, giving the company a excuse not to except the RMA?
Raising voltages won't "break" anything, giving the company a excuse not to except the RMA?
The key to adjusting voltages on RAM is to do very small steps, know the limits and do not exceed them.
All of the RAM manufacturers suggest the same voltages increase to get the RAM stable.
To check you can post at the RAM and/or motherboard forums, explain your problem and ask for a solution or if bumping the NP voltage to 1.2v is advisable.
This is the standard answer on most RAM/motherboard forums for this issue.
Your motherboard has a known issue with stability, due to the integrated memory controller, with any RAM higher than 1333MHz.
�� Quote: Originally Posted by iTitus Thanks again,
I'm looking forward to Sunday. A working system would be a great birthday gift for my 18th birthday monday
I'm looking forward to Sunday. A working system would be a great birthday gift for my 18th birthday monday
In advance, have a Happy birthday!
1st
I'll do a clean install first
4th
I ran a memtest with stick 1 in slot 1 and stick 2 in slot 2(dual channel unganged mode)
9 passes no errors. But upon using my computer(as a test Starcraft 2 was a good indication), it kept crashing.
Then I removed stick 2 from slot 2 and played starcraft and used my system no problemo(didnt run memtest)
Then I removed stick 1 from slot 1 AND Insterted stick 2 in slot 1.
That gave me the same unstable system with crashes random and during starcraft.(again, no memtest)
Concluding:
So I ran only 1 memtest, with both sticks in their slots.
I ran my system with only 1 stick in slot 1 twice, once with stick 1 and once with stick 2. Stick 1 did fine and stick 2 gave problems.
That's why I wonder if it could be stick 2 that is the problem here.
I'll do a clean install first
4th
I ran a memtest with stick 1 in slot 1 and stick 2 in slot 2(dual channel unganged mode)
9 passes no errors. But upon using my computer(as a test Starcraft 2 was a good indication), it kept crashing.
Then I removed stick 2 from slot 2 and played starcraft and used my system no problemo(didnt run memtest)
Then I removed stick 1 from slot 1 AND Insterted stick 2 in slot 1.
That gave me the same unstable system with crashes random and during starcraft.(again, no memtest)
Concluding:
So I ran only 1 memtest, with both sticks in their slots.
I ran my system with only 1 stick in slot 1 twice, once with stick 1 and once with stick 2. Stick 1 did fine and stick 2 gave problems.
That's why I wonder if it could be stick 2 that is the problem here.
The puzzling thing is that memtest86+ passed with both sticks installed.
Put stick 2 into slot 1 and run memtest86+.
If you get errors, tell us what the errors are, when the errors start repeating you can stop the test.
Then put stick 2 in slot 2 and run memtest86+, note the errors, if any.
*Always monitor temperatures with Core Temp when running any test/game while we are troubleshooting. Let us know the temps when the tests/games are running.
Just found a reference to install RAM in slots 3 and 4 if they are 1333MHz or above.
Also see the Edit in post #97, try them in single channel, slots 1 & 3.
If stick 2 fails in both slots and stick 1 passes in both, RMA the RAM.
Are you running in AHCI mode?
This is mentioned to cause crashes.
When the crashes occurred, how long had the computer been running?
Have you noticed that the crashes don't or do occur within the first 30 minutes of starting it or is it after its been running for 30 minutes?
Or are they completely random?
Asking this as one of the components may be heating up and causing/contributing to the crashes.
Next crash, carefully touch the north bridge and give your best estimate of the temperature.
Added another link to the AMD RAM issue in post #95.
Put stick 2 into slot 1 and run memtest86+.
If you get errors, tell us what the errors are, when the errors start repeating you can stop the test.
Then put stick 2 in slot 2 and run memtest86+, note the errors, if any.
*Always monitor temperatures with Core Temp when running any test/game while we are troubleshooting. Let us know the temps when the tests/games are running.
Just found a reference to install RAM in slots 3 and 4 if they are 1333MHz or above.
Also see the Edit in post #97, try them in single channel, slots 1 & 3.
If stick 2 fails in both slots and stick 1 passes in both, RMA the RAM.
Are you running in AHCI mode?
This is mentioned to cause crashes.
When the crashes occurred, how long had the computer been running?
Have you noticed that the crashes don't or do occur within the first 30 minutes of starting it or is it after its been running for 30 minutes?
Or are they completely random?
Asking this as one of the components may be heating up and causing/contributing to the crashes.
Next crash, carefully touch the north bridge and give your best estimate of the temperature.
Added another link to the AMD RAM issue in post #95.
I Read your post,
I'll run the memtest series when I get back(how many passes is advised?) Both modules in both slots one at a time.(slot 1 and 2 only or slot 3 and 4 also? Given your reference?)
What's AHCI mode?
The crashes are kinda random, somtimes within 30 minutes, sometimes after like 2 hours. It's really strange.
http://www.ixbt.com/mainboard/gigaby...3/board-sm.jpg
You see the coolblock that says gigabyte, I noticed that that actually becomes pretty damn hot.
But then again IMO the GPU becomes pretty hot too...
This is going to take a loooooong while to test xD But atleast I already have the clearence from the shop to stop by and trade them in, or I think so :P
Thanks again for helping and answering questions. When I get back I'll first run the memtests and try voltages, when the system is steady I'll do a clean install.w
I'll run the memtest series when I get back(how many passes is advised?) Both modules in both slots one at a time.(slot 1 and 2 only or slot 3 and 4 also? Given your reference?)
What's AHCI mode?
The crashes are kinda random, somtimes within 30 minutes, sometimes after like 2 hours. It's really strange.
http://www.ixbt.com/mainboard/gigaby...3/board-sm.jpg
You see the coolblock that says gigabyte, I noticed that that actually becomes pretty damn hot.
But then again IMO the GPU becomes pretty hot too...
This is going to take a loooooong while to test xD But atleast I already have the clearence from the shop to stop by and trade them in, or I think so :P
Thanks again for helping and answering questions. When I get back I'll first run the memtests and try voltages, when the system is steady I'll do a clean install.w
Open and run Core Temp during all testing, note the temps and let us know.
Disclaimer: If you don't feel comfortable running stress tests on your computer, then don't.
There is a potential to damage components. Proceed at your own risk.
�� Quote: Originally Posted by iTitus If stick 2 fails in two slots, I'd say its bad.
You should see something by the end of two passes, if no errors let it run for 7 passes.
This will let us rule out the bad RAM possibility.
If you get to the stage of testing two 'good' RAM sticks in slots 1 & 3, run memtest86+ on both of them, 7 passes, overnight.
�� Quote: Originally Posted by iTitus AHCI, Advanced Host Controller Interface
In your BIOS, Integrated Peripherals, (motherboard manual pg 48) OnChip SATA Type.
Check what the setting is and let us know.
�� Quote: Originally Posted by iTitus So the crashes are random.
�� Quote: Originally Posted by iTitus Yes, the block that says Gigabyte.
GPUs normally run pretty hot, that's normal. The north bridge shouldn't be very hot, should be able to hold your finger on it.
�� Quote: Originally Posted by iTitus After you run the memtest86+, let us know the results.
According to the info from AMD, let's increase the DRAM voltage first.
Set it to 1.55v,
Run prime95, enable 6 cores, torture test - Blend.
If the temps are 35ish, it's not running correctly and will not stress the CPU or RAM.
It should show and error within a couple of minutes of starting if the system isn't stable.
30 minutes should be good enough for this test.
If Prime95 stops or the computer crashes it's a fail.
Do not exceed 1.65v.
If Prime95 fails or the system crashes go to 1.6v, same test as above.
Your BIOS should have a max of 1.64v, it should increase in .02v intervals, the 1.66v setting should be in red color.
Go to 1.64v, same test as above.
If stable at any voltage, Prime95 keeps running, no crash. Stop test after 30 min, test with most stressful game for several hours.
If it's not stable at 1.64v then bring it back to 1.5v and let us know the steps you have taken and the temperatures at each.
Disclaimer: If you don't feel comfortable running stress tests on your computer, then don't.
There is a potential to damage components. Proceed at your own risk.
�� Quote: Originally Posted by iTitus I Read your post,
I'll run the memtest series when I get back(how many passes is advised?) Both modules in both slots one at a time.(slot 1 and 2 only or slot 3 and 4 also? Given your reference?)
I'll run the memtest series when I get back(how many passes is advised?) Both modules in both slots one at a time.(slot 1 and 2 only or slot 3 and 4 also? Given your reference?)
You should see something by the end of two passes, if no errors let it run for 7 passes.
This will let us rule out the bad RAM possibility.
If you get to the stage of testing two 'good' RAM sticks in slots 1 & 3, run memtest86+ on both of them, 7 passes, overnight.
�� Quote: Originally Posted by iTitus What's AHCI mode?
In your BIOS, Integrated Peripherals, (motherboard manual pg 48) OnChip SATA Type.
Check what the setting is and let us know.
�� Quote: Originally Posted by iTitus The crashes are kinda random, somtimes within 30 minutes, sometimes after like 2 hours. It's really strange.
�� Quote: Originally Posted by iTitus http://www.ixbt.com/mainboard/gigaby...3/board-sm.jpg
You see the coolblock that says gigabyte, I noticed that that actually becomes pretty damn hot.
But then again IMO the GPU becomes pretty hot too...
You see the coolblock that says gigabyte, I noticed that that actually becomes pretty damn hot.
But then again IMO the GPU becomes pretty hot too...
GPUs normally run pretty hot, that's normal. The north bridge shouldn't be very hot, should be able to hold your finger on it.
�� Quote: Originally Posted by iTitus This is going to take a loooooong while to test xD But atleast I already have the clearence from the shop to stop by and trade them in, or I think so :P
Thanks again for helping and answering questions. When I get back I'll first run the memtests and try voltages, when the system is steady I'll do a clean install.w
Thanks again for helping and answering questions. When I get back I'll first run the memtests and try voltages, when the system is steady I'll do a clean install.w
According to the info from AMD, let's increase the DRAM voltage first.
Set it to 1.55v,
Run prime95, enable 6 cores, torture test - Blend.
In the Prime95 advanced tab, check 'Round off Checking'*Have Core Temp open and running, watch the temps closely when the test starts, then until it levels off. Should be in the 50 - 60c range. Max CPU temp is 62c.
Options tab, Torture Test, select Blend, Number of Torture Test threads to run: 6
If the temps are 35ish, it's not running correctly and will not stress the CPU or RAM.
It should show and error within a couple of minutes of starting if the system isn't stable.
30 minutes should be good enough for this test.
If Prime95 stops or the computer crashes it's a fail.
Do not exceed 1.65v.
If Prime95 fails or the system crashes go to 1.6v, same test as above.
Your BIOS should have a max of 1.64v, it should increase in .02v intervals, the 1.66v setting should be in red color.
Go to 1.64v, same test as above.
If stable at any voltage, Prime95 keeps running, no crash. Stop test after 30 min, test with most stressful game for several hours.
If it's not stable at 1.64v then bring it back to 1.5v and let us know the steps you have taken and the temperatures at each.
Ok here I go:
I did a lot of memtests:
Stick 1(the one that seemed good while testing SC2)
Passed all slots with 2,5 passes each time. Due to shortage of time I only did 2,5 passes
Stick 2(the one that seemed to mallfunction while testing SC2)
Passed slot 1 2,5 passes
failed at slot 2, 2 different times, one short run and one long run(see pics for error codes)
passed slot 3, 2,5 passes
failed at slot 4(tested 1 time, 3 passes i thought)
The pics are attached.
Onchip Sata type: "Native IDE".
So AHCI is disabled i think
Also I touched my NB cooling block during ram test, and IMO I couldn't hold my finger there(although my friend could)
I didn't raise voltages yet... First I'd like some info on the errors :P
I did a lot of memtests:
Stick 1(the one that seemed good while testing SC2)
Passed all slots with 2,5 passes each time. Due to shortage of time I only did 2,5 passes
Stick 2(the one that seemed to mallfunction while testing SC2)
Passed slot 1 2,5 passes
failed at slot 2, 2 different times, one short run and one long run(see pics for error codes)
passed slot 3, 2,5 passes
failed at slot 4(tested 1 time, 3 passes i thought)
The pics are attached.
Onchip Sata type: "Native IDE".
So AHCI is disabled i think
Also I touched my NB cooling block during ram test, and IMO I couldn't hold my finger there(although my friend could)
I didn't raise voltages yet... First I'd like some info on the errors :P
Good job on the memtest86+ tests. A little short on run times, but the information is useful.
Normally the errors are enough to indicate the problem and a long test is not necessary.
When there are no errors, running the tests longer can show errors later in the test, this is very useful information.
Test #6 will detect data sensitive errors.
RAM #2 had errors in slots 2 and 4 which is in two different channels and both memory controllers, when running unganged.
This indicates the DRAM voltage may help.
Bump the DRAM voltage as described.
According to the info from AMD, let's increase the DRAM voltage first.
Let's work on RAM #2 first.
When it passes all tests, then we can if check RAM #1 will run at those settings.
Set it to 1.55v,
First run memtest86+ for 7 passes or stop it if your getting errors.
* Always have Core Temp and HWMonitor open and running, watch the temps closely when the test starts, then until it levels off. Should be in the low 50's. Don't let it go past 60c. Max temp for your CPU is 62c.
Also run CPUID HWMonitor, this is important, there are reports that some AMD processors don't give accurate CPU temp information. You need to confirm the temps.
If it passes memtest86+:
Run prime95, enable 6 cores, torture test - Blend.
In the Prime95 advanced tab, check 'Round off Checking'
Options tab, Torture Test, select Blend, Number of Torture Test threads to run: 6
*Have Core Temp open and running, watch the temps closely when the test starts, then until it levels off. Should be in the low 50's. Don't let it go past 60c. Max temp for your CPU is 62c.
Also run CPUID HWMonitor, this is important, there are reports that some AMD processors don't give accurate CPU temp information. You need to confirm the temps.
If the temps are 35ish, it's not running correctly and will not stress the CPU or RAM.
It should show and error within a couple of minutes of starting if the system isn't stable.
30 minutes should be good enough for this test.
If Prime95 stops or the computer crashes it's a fail.
Do not exceed 1.65v.
If Prime95 fails or the system crashes go to 1.6v, same tests as above.
Your BIOS should have a max of 1.64v, it should increase in .02v intervals, the 1.66v setting should be in red color.
Go to 1.64v, same tests as above.
If stable at any voltage, Prime95 keeps running, no crash. Stop test after 30 min, test with most stressful game for several hours.
If it's not stable at 1.64v then bring it back to 1.5v and let us know the steps you have taken and the temperatures at each.
Normally the errors are enough to indicate the problem and a long test is not necessary.
When there are no errors, running the tests longer can show errors later in the test, this is very useful information.
Test #6 will detect data sensitive errors.
RAM #2 had errors in slots 2 and 4 which is in two different channels and both memory controllers, when running unganged.
This indicates the DRAM voltage may help.
Bump the DRAM voltage as described.
According to the info from AMD, let's increase the DRAM voltage first.
Let's work on RAM #2 first.
When it passes all tests, then we can if check RAM #1 will run at those settings.
Set it to 1.55v,
First run memtest86+ for 7 passes or stop it if your getting errors.
* Always have Core Temp and HWMonitor open and running, watch the temps closely when the test starts, then until it levels off. Should be in the low 50's. Don't let it go past 60c. Max temp for your CPU is 62c.
Also run CPUID HWMonitor, this is important, there are reports that some AMD processors don't give accurate CPU temp information. You need to confirm the temps.
If it passes memtest86+:
Run prime95, enable 6 cores, torture test - Blend.
In the Prime95 advanced tab, check 'Round off Checking'
Options tab, Torture Test, select Blend, Number of Torture Test threads to run: 6
*Have Core Temp open and running, watch the temps closely when the test starts, then until it levels off. Should be in the low 50's. Don't let it go past 60c. Max temp for your CPU is 62c.
Also run CPUID HWMonitor, this is important, there are reports that some AMD processors don't give accurate CPU temp information. You need to confirm the temps.
If the temps are 35ish, it's not running correctly and will not stress the CPU or RAM.
It should show and error within a couple of minutes of starting if the system isn't stable.
30 minutes should be good enough for this test.
If Prime95 stops or the computer crashes it's a fail.
Do not exceed 1.65v.
If Prime95 fails or the system crashes go to 1.6v, same tests as above.
Your BIOS should have a max of 1.64v, it should increase in .02v intervals, the 1.66v setting should be in red color.
Go to 1.64v, same tests as above.
If stable at any voltage, Prime95 keeps running, no crash. Stop test after 30 min, test with most stressful game for several hours.
If it's not stable at 1.64v then bring it back to 1.5v and let us know the steps you have taken and the temperatures at each.
So if I understand correctly:
Put stick 2 in slot 2
Raise DRAM voltage(only that one) to 1,55V
Run memtest 7 passes or when errors reoccur
Then: How can I run that software during Memtest? Memtest is booted from an usb device and the software is windows related??
If it passes 30 minutes prime95:
When I ran the prime95 test the other time for 12 hours, Max temp was about 36C. Same for each time I run Prime. Note that I DO have a 3rd party cooler. I don't know if it lowers the temps by 30C but :P...
If it failes raise to 1,6 and repeat till 1,64
I attached a screen of the normal temps according to CPUID hardware:
Put stick 2 in slot 2
Raise DRAM voltage(only that one) to 1,55V
Run memtest 7 passes or when errors reoccur
Then: How can I run that software during Memtest? Memtest is booted from an usb device and the software is windows related??
If it passes 30 minutes prime95:
When I ran the prime95 test the other time for 12 hours, Max temp was about 36C. Same for each time I run Prime. Note that I DO have a 3rd party cooler. I don't know if it lowers the temps by 30C but :P...
If it failes raise to 1,6 and repeat till 1,64
I attached a screen of the normal temps according to CPUID hardware:
I Raised the DRAM voltage to 1,56V With stick 2 in slot 2 and did a memtest.
Is this enough to call it a "fail" for 1,56V?
Is this enough to call it a "fail" for 1,56V?
Yes thats a fail. Raise the voltage to 1.6v and test again.
Ya, you won't be able to run a temperature monitor when doing the memtest86+.
Be sure to monitor temps when running Prime95.
Something is not right if Prime95 only gives you 36c.
That is a nice cooler, same as mine, but you should have temps in the 50s when running Prime95.
Are you using CUPID Hardware Monitor when testing?
It should be accurate, run Core Temp at the same time to check/verify the temps.
What does Windows Task Manager > Performance tab > Resource monitor, say when your running Prime95?
All cores should be 100%, RAM also.
Ya, you won't be able to run a temperature monitor when doing the memtest86+.
Be sure to monitor temps when running Prime95.
Something is not right if Prime95 only gives you 36c.
That is a nice cooler, same as mine, but you should have temps in the 50s when running Prime95.
Are you using CUPID Hardware Monitor when testing?
It should be accurate, run Core Temp at the same time to check/verify the temps.
What does Windows Task Manager > Performance tab > Resource monitor, say when your running Prime95?
All cores should be 100%, RAM also.
I'm going to raise the voltage to 1,6 now. Then 1,64.
I ran a program called "LinX", which was a suggestion from GEIL. Gave me a error too, stick 2 in slot 2. Here's a screen.
When I visit task manager during a prime95 test, it says both CPU and RAM 100% usage.
So does Core Temp.
brb with results
I ran a program called "LinX", which was a suggestion from GEIL. Gave me a error too, stick 2 in slot 2. Here's a screen.
When I visit task manager during a prime95 test, it says both CPU and RAM 100% usage.
So does Core Temp.
brb with results
LinX is good also, it will should give you higher temps that Prime95.
Be sure to monitor your temps during testing with either LinX or Prime95.
Those are some low temps, I have read some posts about AMD not giving the correct temps in some cases.
Let us know the results and the temps.
Be sure to monitor your temps during testing with either LinX or Prime95.
Those are some low temps, I have read some posts about AMD not giving the correct temps in some cases.
Let us know the results and the temps.
I am having exact same behavior on ASUS M4A785TD-M EVO mobo. Just now finalized both mobo bios and video driver update (direct from ATI). (The card is Sapphire 512mb, windows had loaded its own WDM drivers). My CPUID returned 9,9,9,24,33 so I will try those settings and the volt bumps. Here though, I have four brand new builds, exactly the same. In the 7 days since install, three crash repeatedly while one has not crashed ever. Sure smells like unstable RAM production.
Dear Dave,
I Raised the voltage to 1,6V and ran 8 passes memtest with NO errors.
Please advise on the next step, the prime95 test. I fear that i'll still get the 35ish temperatures... But I'll turn it on for half an hour now
See you in Half an Hour
EDIT:
2 pics before and after running prime. No errors or something, but still 35ish temperatures
I Raised the voltage to 1,6V and ran 8 passes memtest with NO errors.
Please advise on the next step, the prime95 test. I fear that i'll still get the 35ish temperatures... But I'll turn it on for half an hour now
See you in Half an Hour
EDIT:
2 pics before and after running prime. No errors or something, but still 35ish temperatures
The results look good.
If Prime95 is running all cores at 100% then it's working.
The low temps aren't bad, just unusual, maybe thats normal for your CPU.
Run Prime95 or LinX for 30 minutes, as you mentioned.
If it passes, install the other RAM stick and run Prime95 or LinX again, if it passes you can use your computer normally and see if it remains stable, play your most computer stressing/demanding games.
Memtest86+, Prime95 and LinX are good testing apps but it's not impossible for the problem to return.
There can be several reasons for this, hopefully it will run stable.
If the tests don't pass, give detailed info here and we'll proceed to the next step.
Let us know the progress.
Edit:
That TMPIN2 82c, is a bit high.
Will depend on your motherboard what that is for, from your pics it's not CPU, GPU or HDD.
Might be NB temp, if your friend can hold his finger on it, it can't be 82c.
Might be case temp, which would tell me that the sensor is bad.
Has it always been like that?
You can try this:
If Prime95 is running all cores at 100% then it's working.
The low temps aren't bad, just unusual, maybe thats normal for your CPU.
Run Prime95 or LinX for 30 minutes, as you mentioned.
If it passes, install the other RAM stick and run Prime95 or LinX again, if it passes you can use your computer normally and see if it remains stable, play your most computer stressing/demanding games.
Memtest86+, Prime95 and LinX are good testing apps but it's not impossible for the problem to return.
There can be several reasons for this, hopefully it will run stable.
If the tests don't pass, give detailed info here and we'll proceed to the next step.
Let us know the progress.
Edit:
That TMPIN2 82c, is a bit high.
Will depend on your motherboard what that is for, from your pics it's not CPU, GPU or HDD.
Might be NB temp, if your friend can hold his finger on it, it can't be 82c.
Might be case temp, which would tell me that the sensor is bad.
Has it always been like that?
You can try this:
Quote:
I have this same "issue" with my Phenom II x4 940 (in both Speedfan and CPUID Hardware Monitor).
Speedfan is displaying inaccurate values. There are two kinds of temperature monitoring devices in place on motherboards, thermistors and diodes. If the diode is set to read as a thermistor it will give you unusually high numbers as you're seeing, and I'd imagine the opposite is true of a thermistor being read as diode (although I haven't experienced this personally).
To remedy the issue in speedfan, select the "configure" button on the "readings" tab.
Select the "advanced" tab.
On the "chip" drop-down menu there should be two choices, "AMD K10 at..." and another that is specific to your motherboard. Choose the one that isn't "AMD K10 at..."
There should be a list of values in the box below the drop-down menu.
On my machine the first three under the "Property" column being:
Temperature sensor diode 1
Temperature sensor diode 2
Temperature sensor diode 3
The "Value" column adjacent to these indicates whether it is being read as a thermistor or diode.
You can select one of these values and then in the "Set to" drop-down menu below set the "Value" to thermistor or diode.
---------
In my case the "Property" said diode right in the description and the "Value" was set to thermistor so it was fairly straight forward to just switch the "Value" to diode and the temperature came to a much more realistic ~35C.
Speedfan is displaying inaccurate values. There are two kinds of temperature monitoring devices in place on motherboards, thermistors and diodes. If the diode is set to read as a thermistor it will give you unusually high numbers as you're seeing, and I'd imagine the opposite is true of a thermistor being read as diode (although I haven't experienced this personally).
To remedy the issue in speedfan, select the "configure" button on the "readings" tab.
Select the "advanced" tab.
On the "chip" drop-down menu there should be two choices, "AMD K10 at..." and another that is specific to your motherboard. Choose the one that isn't "AMD K10 at..."
There should be a list of values in the box below the drop-down menu.
On my machine the first three under the "Property" column being:
Temperature sensor diode 1
Temperature sensor diode 2
Temperature sensor diode 3
The "Value" column adjacent to these indicates whether it is being read as a thermistor or diode.
You can select one of these values and then in the "Set to" drop-down menu below set the "Value" to thermistor or diode.
---------
In my case the "Property" said diode right in the description and the "Value" was set to thermistor so it was fairly straight forward to just switch the "Value" to diode and the temperature came to a much more realistic ~35C.
�� Quote: Originally Posted by soaringink I am having exact same behavior on ASUS M4A785TD-M EVO mobo. Just now finalized both mobo bios and video driver update (direct from ATI). (The card is Sapphire 512mb, windows had loaded its own WDM drivers). My CPUID returned 9,9,9,24,33 so I will try those settings and the volt bumps. Here though, I have four brand new builds, exactly the same. In the 7 days since install, three crash repeatedly while one has not crashed ever. Sure smells like unstable RAM production.
Good call on the BIOS and video drivers.
Check for chipset drivers and update if you find a newer one.
You can set your RAM timings manually to 9-9-9-24, leave the rest on Auto.
Read the posts at VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Including his first post on page 2, he clarified ganged and unganged info.
If your not set to unganged, change it.
D/L CPUZ and post the Memory and SPD tabs.
What is you current RAM voltage settings?
Don't recommend going past 1.65v.
Let us know your progress.
@Dave
I'll install the other ram stick and do the prime test.
If it doesnt work with 2 sticks, does it mean that stick one doesn't support the higher voltage, or does it mean that because stick 1 is inserted too, the voltage drops a little resulting in stick 2 failing?
Notice, when I tried the work arround from that guy the temp 80 went to -78, so I guess that didn't work xD
I don't know why the temps are so low?
I changed another value and the fan started spinning like hell. (reminds me why I didn't set "fan speed" to FULL in the bios but let it be "Automatic"
Titus
I'll install the other ram stick and do the prime test.
If it doesnt work with 2 sticks, does it mean that stick one doesn't support the higher voltage, or does it mean that because stick 1 is inserted too, the voltage drops a little resulting in stick 2 failing?
Notice, when I tried the work arround from that guy the temp 80 went to -78, so I guess that didn't work xD
I don't know why the temps are so low?
I changed another value and the fan started spinning like hell. (reminds me why I didn't set "fan speed" to FULL in the bios but let it be "Automatic"
Titus
Did RAM card #2 pass the Prime95 test for 30 minutes?
Those are the two most likely possibilities and of coarse, that RAM card (#2) is bad and won't play nicely with others.
If it won't pass with both cards inserted, we can do some minor voltage adjustments.
Now we know card #2 will work with a little more voltage.
Maybe a little NB Voltage bump, you have to very careful with this, lets not do this until last.
Let me know how it's going.
Those are the two most likely possibilities and of coarse, that RAM card (#2) is bad and won't play nicely with others.
If it won't pass with both cards inserted, we can do some minor voltage adjustments.
Now we know card #2 will work with a little more voltage.
Maybe a little NB Voltage bump, you have to very careful with this, lets not do this until last.
Let me know how it's going.
I think both test(ram 2 in slot 2 and both(1in1 and 2in2)) passed prime.
Also I think I found my "real" coretemp, being arround 40 something during prime.
I'll play some games and see if that works
Another question is: Is this higher voltage bad for either the RAM or the MOBO, because if that's the case I'll just RMA the ram/mobo(both bought at the same company). Thanks
And I might someday be interested in overclocking, due to this "start" I'm getting used to stability tests :P
Also I think I found my "real" coretemp, being arround 40 something during prime.
I'll play some games and see if that works
Another question is: Is this higher voltage bad for either the RAM or the MOBO, because if that's the case I'll just RMA the ram/mobo(both bought at the same company). Thanks
And I might someday be interested in overclocking, due to this "start"
I'm getting used to stability tests :P Good news both RAM cards passed.
Games are a good stress test, let us know if it stays stable.
Too high voltages are not good, you are still within the safe and reasonable limits.
You could RMA the RAM but, there's no guarantee that the new RAM wouldn't need the same adjustments.
Then again, they might not...
Be very careful of the overclocking bug, once bitten...
You'll be running stability tests all the time
It's an interesting learning experience, read up on the subject and then have fun.
Let us know how the system is running, this info will be useful to many others with similar issues.
Games are a good stress test, let us know if it stays stable.
Too high voltages are not good, you are still within the safe and reasonable limits.
You could RMA the RAM but, there's no guarantee that the new RAM wouldn't need the same adjustments.
Then again, they might not...
Be very careful of the overclocking bug, once bitten...
You'll be running stability tests all the time
It's an interesting learning experience, read up on the subject and then have fun.
Let us know how the system is running, this info will be useful to many others with similar issues.
so much trouble with a very new system, wouldn't it be easier to return it and get a functioning one? I'd understand if it would be a year old system, then you would try anything to get it back working, but atm if anything fails - no refunds.
I'd understand if it would be a year old system, then you would try anything to get it back working, but atm if anything fails - no refunds. Hi Guys,
Long time no see. I just played SC for 2 hours and upon alt+f4 ing out of the game I got a crash(not the best way to exit a game, will never do so etc etc)
But here are the files:
Everything is touchable, except the NB, which is damned hot!@
Long time no see. I just played SC for 2 hours and upon alt+f4 ing out of the game I got a crash(not the best way to exit a game, will never do so etc etc)
But here are the files:
Everything is touchable, except the NB, which is damned hot!@
I just figured out I was still running on DirectX 9,0c.
I Updated it now. Will let you guys know
I Updated it now. Will let you guys know
Thanks for the update.
Let us know how it's going.
Let us know how it's going.
It's been a while.. I suppose the PC is fine now?.. or just lost hope?
Knock on wood.
Hadn't had an error since the last starcraft fail. And I did play it
Seems to be a workarround/solved
Hadn't had an error since the last starcraft fail. And I did play it
Seems to be a workarround/solved
Glad to hear the news.
If you think it's 'Solved' click the red triangle in the upper right corner of your post and put 'Solved' in the message box.
Let us know if you have more issues.
If you think it's 'Solved' click the red triangle in the upper right corner of your post and put 'Solved' in the message box.
Let us know if you have more issues.
Just got a BSOD again
Don't know whether this is going to continue
Don't know whether this is going to continue
I haven't re-read the thread (yet), but have you tried a new GFX card?
...Summary of the Dumps:
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Oct 16 11:43:24.063 2010 (UTC - 4:00) System Uptime: 0 days 6:38:54.060 BugCheck 1000007E, {ffffffffc0000005, fffff880041d553a, fffff8800a0ce598, fffff8800a0cde00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+10e ) PROCESS_NAME: csrss.exe BUGCHECK_STR: 0x7E �������������������������������������������������������������������������������������� I havn't tried an other graphics card yet. But after getting this error I played starcraft for a few hours without problems. Strange...
I'm actually running ati 10.9a, the hotfix fixing the overscan issue:
GPU-78: ATI Catalyst
I'm actually running ati 10.9a, the hotfix fixing the overscan issue:
GPU-78: ATI Catalyst
I THINK the issue is PSU related! I googled a bit, such bsods appear on many people.. and all of them are fixed after a PSU upgrade.. I think you bought a too weak one (520W).. a 6 core CPU, a case which has LED's in them and god knows how many hard drives and extras. You are slightly underpowering your GPU, not a complete catastrophe, but enough to make it unstable and cause BSOD's.
No leds and just one hdd :P
But i'll keep it in mind
Titus
But i'll keep it in mind
Titus
It seems almost certain this is some kind of hardware issue. PSU is possible, although it seems like you have plenty of power from a reliable brand. Of course, any PSU can fail, especially older ones, but I would start checking other components first.
Test RAM again, with all sticks in. In case you threw away your CD or forgot how: RAM - Test with Memtest86+
Test GFX card: Video Card - Stress Test with Furmark
Test RAM again, with all sticks in. In case you threw away your CD or forgot how: RAM - Test with Memtest86+
Test GFX card: Video Card - Stress Test with Furmark
It could still be a PSU issue, its not the maximum watts I'm worried about, its the amps on 12v rails.
Had another crash...
They seem to occur rarely, although a little more often last time.
I've got the feeling that they are different each time.
What about the 12V rail?
Thanks
They seem to occur rarely, although a little more often last time.
I've got the feeling that they are different each time.
What about the 12V rail?
Thanks
I have read through this thread, and I notice a common cause throughout: video.
That can also be caused by bad RAM, which has been investigated earlier.
Run Memtest again, just to make sure.
If you have another graphics card to test, please do so. If you can't borrow one from a friend, purchase one from the local computer store. Be sure it allows you to return the card, should it turn out it wasn't the problem.
That can also be caused by bad RAM, which has been investigated earlier.
Run Memtest again, just to make sure.
If you have another graphics card to test, please do so. If you can't borrow one from a friend, purchase one from the local computer store. Be sure it allows you to return the card, should it turn out it wasn't the problem.
On pages 7 and 8 I described the tests with my old GPU, a Nvidia 6700XL
Hope that helps.
Cheers
Hope that helps.
Cheers
I guess all I can think of is a bad motherboard. Have you tried a new one?
Hi iTitus:
I know I'm sounding like a broken record here (reply 1) but I really think you should try a new board. The connection with video issues could be a result of the Northbridge under-power issues noted in replies 2 and 3.
Good luck... Brian
I know I'm sounding like a broken record here (reply 1) but I really think you should try a new board. The connection with video issues could be a result of the Northbridge under-power issues noted in replies 2 and 3.
Good luck... Brian
As mentioned previously by bwpotter, you need to bump your NB (North Bridge) voltage to 1.2v. This should help if the cause is the RAM.
Also, verify the RAM is in single channel and un-ganged, leave the DRAM voltage where they passed before.
Is the RAM voltage still at 1.6v?
If this doesn't help, go with bwpotter's suggestion and get a new motherboard.
Also, verify the RAM is in single channel and un-ganged, leave the DRAM voltage where they passed before.
Is the RAM voltage still at 1.6v?
If this doesn't help, go with bwpotter's suggestion and get a new motherboard.
Still running 1,6V DRAM.
Never did something to the NB
Also I'm running Dual channel un-ganged
Titus
Never did something to the NB
Also I'm running Dual channel un-ganged
Titus
Yes, for the time being, leave the DRAM at 1.6v and raise the NB to 1.2v; they are independent of each other.
Got another crash, it seems that this problem is returning.
I'll send a few emails to the store I bought the MoBo to see what they think about it and an RMA.
EDIT:
I emailed the shop and he said that I could try to lower the speed form 1333Mhz to 1066Mhz. He also said that if that didn't work I could return it. So I asked how the return procedure would work and what would happen if a possible new set of memory had the same problem(ie new mobo).
I'll send a few emails to the store I bought the MoBo to see what they think about it and an RMA.
EDIT:
I emailed the shop and he said that I could try to lower the speed form 1333Mhz to 1066Mhz. He also said that if that didn't work I could return it. So I asked how the return procedure would work and what would happen if a possible new set of memory had the same problem(ie new mobo).
Agree with bwpotter, leave the DRAM at 1.6v and raise the NB to 1.2v...
That's going to be your best bet. RMA the MOBO and RAM. Double check the MOBO recommended RAM and get it from their list.
If you want to give it one more shot, set your RAM to run in single channel mode. Your MOBO manual will tell you how, you will need to change the slots the RAM is in.
That's going to be your best bet. RMA the MOBO and RAM. Double check the MOBO recommended RAM and get it from their list.
If you want to give it one more shot, set your RAM to run in single channel mode. Your MOBO manual will tell you how, you will need to change the slots the RAM is in.
I decided to test the GFX card one more time.
That all worked out fine without crashes etc.
I'm emailing back and forth with the shop now.
Edit:
The guy said that if Memtest gave error's, the memory would probably be broken and that a RMA should solve it. So I decided to do that.
Upon getting (hopefully) new RAM I'll remove the DRAM Voltage bump and see what the new ram does in memtest86 :P
That all worked out fine without crashes etc.
I'm emailing back and forth with the shop now.
Edit:
The guy said that if Memtest gave error's, the memory would probably be broken and that a RMA should solve it. So I decided to do that.
Upon getting (hopefully) new RAM I'll remove the DRAM Voltage bump and see what the new ram does in memtest86 :P
Sounds like a good plan.
What RAM are you getting?
Make sure it's RAM made for the AMD motherboard, 'standard or Intel RAM' won't run as well as RAM designed for AMD.
You'll have better luck with 1333MHz or lower RAM, anything higher will be difficult to get running.
Start out with XMP enabled in your BIOS, this should be the best setting.
Then check all RAM settings to be sure they match the recommended manufactures specs. It should be in un-ganged mode.
Run Memtest86+.
You may still need to bump the NB voltage, this is common for AMD RAM.
Let us know how it's going.
What RAM are you getting?
Make sure it's RAM made for the AMD motherboard, 'standard or Intel RAM' won't run as well as RAM designed for AMD.
You'll have better luck with 1333MHz or lower RAM, anything higher will be difficult to get running.
Start out with XMP enabled in your BIOS, this should be the best setting.
Then check all RAM settings to be sure they match the recommended manufactures specs. It should be in un-ganged mode.
Run Memtest86+.
You may still need to bump the NB voltage, this is common for AMD RAM.
Let us know how it's going.
I'll be getting the same GEIL modules. Which were tested by Gigabyte and approved...
Ok so Image I could pick new RAM. Which RAM should I pick with my system.
I'm looking for 4gb in the first place, but you know 8gb is not wrong, just a little expensive :P
Also, here's a support list from my MoBo.
System
http://www.sevenforums.com/crashes-d...tml#post917681
I'm looking for 4gb in the first place, but you know 8gb is not wrong, just a little expensive :P
Also, here's a support list from my MoBo.
System
http://www.sevenforums.com/crashes-d...tml#post917681
It depends on which brand you prefer.
From your motherboard DDR3 1333 RAM list.
C13C1 2GB CORSAIR CM3X8GX3M4A1333C9 DS
G13C1 2GB GEIL GG34GB1333C9DC DS
GSET13C1 2GB G.SKILL F3-10666CL8D-4GBECO DS
Be sure to double check that the RAM is specifically designed for an AMD motherboard.
If it says Intel or doesn't name either, I would check for another from the motherboard RAM list.
Let us know how it's going.
From your motherboard DDR3 1333 RAM list.
C13C1 2GB CORSAIR CM3X8GX3M4A1333C9 DS
G13C1 2GB GEIL GG34GB1333C9DC DS
GSET13C1 2GB G.SKILL F3-10666CL8D-4GBECO DS
Be sure to double check that the RAM is specifically designed for an AMD motherboard.
If it says Intel or doesn't name either, I would check for another from the motherboard RAM list.
Let us know how it's going.
Just got my ram back. Triple bad:
It's different ram -_-
a) it's to big to fit under my cpu cooler, so 2/4 slots can't be used
b) it's C9 in stead of C7
c) one of the two sticks won't boot at all
Really thinking about different memory now.
Can someone with one of the memories named in the post by dave measure how high they are?
Thanks
It's different ram -_-
a) it's to big to fit under my cpu cooler, so 2/4 slots can't be used
b) it's C9 in stead of C7
c) one of the two sticks won't boot at all
Really thinking about different memory now.
Can someone with one of the memories named in the post by dave measure how high they are?
Thanks
With my Gigabyte Intel board, CM Hyper 212 Plus, Corsair XMS DDR3 RAM, I have about 1mm clearance between the fan on the CPU cooler and the first RAM card.
The CPU cooling fan just barely covers about 30% of the first RAM card, just enough to cause a problem if the Ram was 1mm higher.
Mine is 28mm from socket to top of RAM card, Ram installed in socket.
If your board layout is similar to mine, you definitely won't fit the Corsair Dominators, the heat sink is too big. The XMS should fit.
Measure the space between your RAM socket and the Hyper 212 Plus fan housing, post it here.
I Would search/ask at the Corsair forum (or other RAM Forum), give them the above measurement.
Memory Compatibility
Better to get 2 RAM cards, as there are reports of problems when using 4 cards.
Now is the time to plan for any future upgrades. Go with 8GB now if you think you might want it later.
Or take the chance that 4 cards will work on your board.
The CPU cooling fan just barely covers about 30% of the first RAM card, just enough to cause a problem if the Ram was 1mm higher.
Mine is 28mm from socket to top of RAM card, Ram installed in socket.
If your board layout is similar to mine, you definitely won't fit the Corsair Dominators, the heat sink is too big. The XMS should fit.
Measure the space between your RAM socket and the Hyper 212 Plus fan housing, post it here.
I Would search/ask at the Corsair forum (or other RAM Forum), give them the above measurement.
Memory Compatibility
Better to get 2 RAM cards, as there are reports of problems when using 4 cards.
Now is the time to plan for any future upgrades. Go with 8GB now if you think you might want it later.
Or take the chance that 4 cards will work on your board.
Just got email from the shop. Their mistake, they will be sending me the memory I had, but a fresh one. It seems all issue's will be solved and it will fit and I got my nice timings back.
Let's wait and see.
I'll get back on you guys.
Thanks
Let's wait and see.
I'll get back on you guys.
Thanks
Thanks for the update, let us know the results.
jeeeeej
/sarcasm mode off
I got my new RAM today. Popped it in, got past bios but freezed at windows logo.
I tried a few times and managed to get it past windows logo a few times, and even into windows itself. But even changing resolution or running 2 programs made it crash.
So I've got a few BSOD's for you
Also I would like tell you about the configuration:
From the wrong RAM they sent me one stick was just broken(didn't even bios, beep error code no memory)
The other one booted fine in slots 2,3,4.(It didn't fit into slot 1 because it was too high and my CPU cooler is there)
The new correct RAM is extremely unstable.
Stick 1 didn't finish winboot in slot 1,1,4(it did boot after I wobbled it arround a bit)
It did boot once in slot 3 and not after that.
Stick 2 didn't boot in 1,2,3(after pressing it harder into the mobo it did get past winlogo but crashed on windows welcome)
and slot 4 gave me a BSOD
I was so sick of this that I tried the wrong RAM again:
Stick 1 still beeped no memory and stick 2 still booted without problems
I mean, this is clear isn't it? No memtest86 is required?
But still I don't have a clue.
My only guess is that this New correct ram is faulty aswell, in which case I will return it and get another brand that is on the QVL.
The other guess is that my MOBO is the problem. I can't really imagine why.
But a good solution seemed to get both a new(different) mobo and new(different) RAM.
This would be a costly solution, also given the fact that I would need new thermal past etc etc etc.
Could you have a look at the BSOD and advise what to do with the RAM and/or Mobo
Thanks!!
/sarcasm mode off
I got my new RAM today. Popped it in, got past bios but freezed at windows logo.
I tried a few times and managed to get it past windows logo a few times, and even into windows itself. But even changing resolution or running 2 programs made it crash.
So I've got a few BSOD's for you
Also I would like tell you about the configuration:
From the wrong RAM they sent me one stick was just broken(didn't even bios, beep error code no memory)
The other one booted fine in slots 2,3,4.(It didn't fit into slot 1 because it was too high and my CPU cooler is there)
The new correct RAM is extremely unstable.
Stick 1 didn't finish winboot in slot 1,1,4(it did boot after I wobbled it arround a bit)
It did boot once in slot 3 and not after that.
Stick 2 didn't boot in 1,2,3(after pressing it harder into the mobo it did get past winlogo but crashed on windows welcome)
and slot 4 gave me a BSOD
I was so sick of this that I tried the wrong RAM again:
Stick 1 still beeped no memory and stick 2 still booted without problems
I mean, this is clear isn't it? No memtest86 is required?
But still I don't have a clue.
My only guess is that this New correct ram is faulty aswell, in which case I will return it and get another brand that is on the QVL.
The other guess is that my MOBO is the problem. I can't really imagine why.
But a good solution seemed to get both a new(different) mobo and new(different) RAM.
This would be a costly solution, also given the fact that I would need new thermal past etc etc etc.
Could you have a look at the BSOD and advise what to do with the RAM and/or Mobo
Thanks!!
Your .dmp file is still showing memory corruption... You need to retest with memtest in each memory slot to test the mobo..
This driver is outdated and needs to be updated ..
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {29c000619328, 2, 1, fffff80002ae53a4} Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca ) Followup: MachineOwner --------- Code:
PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D) ... Sonic CD/DVD driver (used by many different CD/DVD programs) ... pxHelp20.sys programs Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK This will break your CD/DVD program, but can easily be renamed after we've finished. [/b]
But doesn't not booting with one kind of RAM, and booting with another kind of RAM conclude that the ram is faulty?
Possibly, but what we are doing at this point is eliminating the mobo as a cause of the crash.. do this with the known good stick of memory...
Ok I will,
But it would also be safe to replace both? Or would that create to many new variables :P
I Was looking at a Asrock 870 extreme 3 with 2 kingston KVR1333D3N9/2G sticks
But it would also be safe to replace both? Or would that create to many new variables :P
I Was looking at a Asrock 870 extreme 3 with 2 kingston KVR1333D3N9/2G sticks
I know it is an expensive proposition and at the risk of sounding like a broken record again, you really should consider a new (read different model) M/B. You're going down the same road I did! I pulled a good bit of hair out in the process too! I RMA'd the RAM twice, a processor, and the M/B once, but until I changed to a different M/B altogether, I got nowhere! IMO, it's just a bad design; other forums are littered with the same conclusion.
The shop sent me new ram. Kingston this time:
KHX1333C7AD3K2/4G
http://www.valueram.com/datasheets/K...C7AD3K2_4G.pdf
It says C7 but CPU-Z reads it as 9 :O?
I guess changing the timings in the bios slows down the Mhz
Well, I'll see if there's gonna be crashes.
I'll let you know
KHX1333C7AD3K2/4G
http://www.valueram.com/datasheets/K...C7AD3K2_4G.pdf
It says C7 but CPU-Z reads it as 9 :O?
I guess changing the timings in the bios slows down the Mhz
Well, I'll see if there's gonna be crashes.
I'll let you know
Thanks for letting us know your progress.
The settings look good, lowering the MHz usually allows for tighter timings.
It all depends on the RAM specs.
You will not be able to notice the difference.
Hopefully you will have a stable system now.
The settings look good, lowering the MHz usually allows for tighter timings.
It all depends on the RAM specs.
You will not be able to notice the difference.
Hopefully you will have a stable system now.
This is really asking for it, but I'll say it anyway:
After 2 weeks I'm still crash-free(well only opera is a little unsteady but that's something else :P ).
This was totally a RAM issue.
The only question I have left is: Officially this is C7 ram. But right now it is set to 9-9-9-24(see last post)
The guy from the shop said that I might have to set it manually, but given this screenshot, I woul
Thanks! and for the mods:
Problem solved
After 2 weeks I'm still crash-free(well only opera is a little unsteady but that's something else :P ).
This was totally a RAM issue.
The only question I have left is: Officially this is C7 ram. But right now it is set to 9-9-9-24(see last post)
The guy from the shop said that I might have to set it manually, but given this screenshot, I woul
Thanks! and for the mods:
Problem solved
Problem totally gone.
Conclusion: The RAM was faulty.
Thanks everyone.
Thread is lockable.
Conclusion: The RAM was faulty.
Thanks everyone.
Thread is lockable.
Thanks for reporting back iTitus! Glad you are finally stable.
Good to hear your system is running stable, thanks for the feedback.
Không có nhận xét nào:
Đăng nhận xét