Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

over a year of BSODs later, I'm at my wit's end

This is a discussion on over a year of BSODs later, I'm at my wit's end within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. и Windows 7 professional sp 1 и 64bit и custom built this around Dec/Jan of 2009 и reinstalled the OS


Closed Thread
 
Thread Tools Search this Thread
Old 06-14-2011, 09:10 PM   #1
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



и Windows 7 professional sp 1
и 64bit
и custom built this around Dec/Jan of 2009
и reinstalled the OS about a two months or so ago (didn't fix BSODs obviously)

и CPU: AMD Phenom II X4 965 3.4Ghz
и Video Card: HIS Radeon HD 5750
и MoBo: GIGABYTE GA-790FXTA-UD5
и PSU: Rosewill Xtreme Series RX850-D-B 850W
и RAM: CORSAIR DOMINATOR 8GB 240-Pin DDR3 1600
и HDD: Western Digital Caviar Green WD15EADS 1.5TB
и DVD/CD: LG DVD/CD drive
и also note: there is another 2.5" fujitsu plugged in for the past couple of months that's from an old laptop (BSOD's have been happening long before it's installation)


As you can tell, I put quite a bit into this rig, and for the past year and a half I've been dealing with BSOD's and I'm finally at my wit's end. Drivers, hardware, everything, no matter what I change it wont go away.

I know from memory many of my BSOD's have been 0x7E, 0x3B, 0xBE, 0xD1 along with many others I'm sure you'll find in the logs. if you need any more info from me let me know, hell I'll take pictures of the inside if that would help lol.


BSOD info.zip
Lemcott is offline  
Sponsored Links
Advertisement
 
Old 06-14-2011, 11:22 PM   #2
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,336
OS: Windows 10, 8.1 + Windbg :)



Hi -

The 1st driver name probable cause in 1 BSOD; the others should be updated. Your wifi device/ driver - MRVW24C.sys is the reason that you have had so many networking problems (I saw the 100s of entries in the Event Viewer logs). The driver must be updated (2007 too old for Windows 7 x64 SP1) or the device replaced -
Code:
MRVW24C.sys          Sun Oct 28 23:22:31 2007 (472551F7)
RtNdPt60.sys         Sun Jul 19 22:27:32 2009 (4A63D614)
wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
bcgame.sys           Thu Feb 16 12:34:05 2006 (43F4B78D)
wdcsam64.sys         Wed Apr 16 04:39:08 2008 (4805BB2C)
Rt64win7.sys         Thu Feb 26 04:04:13 2009 (49A65B0D)
http://sysnative.com/0x1/DriverReference.html#RtNdPt60.sys
http://sysnative.com/0x1/DriverReference.html#wacommousefilter.sys
http://sysnative.com/0x1/DriverReference.html#MRVW24C.sys
http://sysnative.com/0x1/DriverReference.html#bcgame.sys
http://sysnative.com/0x1/DriverReference.html#wdcsam64.sys
http://sysnative.com/0x1/DriverReference.html#Rt64win7.sys

This error appears 43 times since May 11, 2011 -
Code:
Event[1848]:
 Log Name: System
 Source: Microsoft Antimalware
 Date: 2011-06-13T20:09:31.000
 Event ID: 3002
 Task: N/A
 Level: Error
 Description: 
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
    Feature: Behavior Monitoring
    Error Code: 0x80004005
    Error description: Unspecified error 
    Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.
Update MSE definitions - https://www.microsoft.com/security/po.../HowToMSE.aspx

If error, uninstall MSE, then reinstall - https://support.microsoft.com/kb/2435760/

Chrome began failing on May 11 -
Code:
Event[34709]:
 Log Name: System
 Source: Application Popup
 Date: 2011-05-11T22:23:17.000
 Description: 
Application popup: ???????s?????????????????????????????????????????????????: 
        chrome.exe - Application Error : The exception unknown 
        software exception (0xc0000409) occurred in the application at location 0x75a5a667.
The ?????????? should not be there. Run a malwarebyte scan - https://fileforum.betanews.com/detail...e/1186760019/1


65 of these errors since May 6 -
Code:
Event[33412]:
 Log Name: System
 Source: Service Control Manager
 Date: 2011-05-13T23:23:00.239
 Level: Error
 Description: 
The AODDriver4.0 service failed to start due to the following error: 
The system cannot find the path specified.
This is the driver - AMD Overdrive -
Code:
amdiox64.sys         Thu Feb 18 10:17:53 2010 (4B7D5A21)
http://sysnative.com/0x1/DriverReference.html#amdiox64.sys





Regards. . .

jcgriff2


`


BSOD SUMMARY
Code:
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061411-21559-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 14 22:11:33.668 2011 (GMT-4)
System Uptime: 0 days 11:05:03.792
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  where.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`02ed516c
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061411-17472-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 14 11:05:04.905 2011 (GMT-4)
System Uptime: 0 days 13:40:39.868
Probably caused by : afd.sys ( afd!AfdReturnBuffer+7f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  Dropbox.exe
FAILURE_BUCKET_ID:  X64_0xBE_afd!AfdReturnBuffer+7f
Bugcheck code 000000BE
Arguments fffff880`03e6e5d0 80000002`20a9f121 fffff880`0b0973d0 00000000`0000000b
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061311-29125-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 13 21:20:28.149 2011 (GMT-4)
System Uptime: 0 days 1:01:53.663
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+cd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+cd
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`04565d45 fffff880`02998868 fffff880`029980c0
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061311-20982-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 13 20:14:25.852 2011 (GMT-4)
System Uptime: 0 days 0:05:28.976
BugCheck D1, {ffffef801c24b656, 2, 1, fffff8800519fbd0}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USBPORT.SYS - 
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for MRVW24C.sys
*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
Probably caused by : hardware ( MRVW24C+384e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 000000D1
Arguments ffffef80`1c24b656 00000000`00000002 00000000`00000001 fffff880`0519fbd0
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061211-28719-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 12 23:42:27.316 2011 (GMT-4)
System Uptime: 0 days 4:53:29.830
Probably caused by : atikmdag.sys ( atikmdag+37510e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  World of Wa
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+37510e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`04bc310e fffff880`0c133780 00000000`00000000
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061211-23431-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 12 18:47:40.578 2011 (GMT-4)
System Uptime: 0 days 1:36:13.092
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`04537cee fffff880`069ed6a8 fffff880`069ecf00
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061211-33072-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 12 17:09:52.998 2011 (GMT-4)
System Uptime: 0 days 7:38:41.512
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+443cb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  googletalk.exe
FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+443cb
Bugcheck code 000000BE
Arguments fffff880`01011908 80000000`03d1a121 fffff880`08c91780 00000000`0000000a
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061211-20077-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 12 09:28:43.513 2011 (GMT-4)
System Uptime: 0 days 0:06:37.027
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0421deb0 fffff880`029916d8 fffff880`02990f30
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061211-23540-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 12 05:51:33.407 2011 (GMT-4)
System Uptime: 0 days 9:41:55.531
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Dropbox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02e89c25 fffff880`07c2fa60 00000000`00000000
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061111-20077-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 09:48:04.903 2011 (GMT-4)
System Uptime: 0 days 3:31:44.027
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiDeliverApc+d4
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02c92284 fffff880`06c96020 00000000`00000000
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061111-19968-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 06:15:25.819 2011 (GMT-4)
System Uptime: 0 days 5:49:03.943
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!PspReturnQuota+46
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02cee906 fffff880`031d2938 fffff880`031d2190
BiosVersion = F1
BiosReleaseDate = 11/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-790FXTA-UD5
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
 
 
by jcgriff2     
 
        J. C. Griffith, Microsoft MVP   
 
                    https://mvp.support.microsoft.com/profile/Griffith   
 
 
                    www.sysnative.com
 
                    www.jcgriff2.com 
 
 
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее
jcgriff2 is offline  
Old 06-15-2011, 08:14 AM   #3
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



if this works, I will build a shrine in your honor.

uninstalled/reinstalled MSE and updated the definitions

I found a newer driver for my usb WLAN adapter (WUSB300N), but sadly it's still a vista driver, so I'll have to wait and see if it fixes it. I was thinking about getting a new adapter soon simply because there's no way I can get this one working on my ubuntu partition. Guess I'll have to do it sooner rather than later.

chrome crashing I'm not to worried about, I have the dev branch so every time they kick out a new update it can get finicky. I also think chrome records it as a "Crash" if it's still open when windows is shutting down, or if it's still open while I BSOD (which happens a lot obviously)

I did run that malware software, but like I suspected, it came back empty.

I disabled AMD overdrive (amdiox64.sys) from the device manager from now. sysnative said to rename the file extension as .bak but I couldn't find it. I'll look for it again if the BSOD's continue.


for a bonus i decided to run the verifier that's in the sticky, but it wouldn't run. I would set it all up, finish, reboot, and windows would boot just like always without running anything or getting any BSOD's. maybe ubuntu's grub is messing with the startup service?

I'll keep you posted.
Lemcott is offline  
Sponsored Links
Advertisement
 
Old 06-15-2011, 09:43 AM   #4
TSF Enthusiast
 
Join Date: Jun 2010
Posts: 2,210
OS: Windows 7 SP1



Driver Verifier is only an extra set of driver checks that Windows will perform on specified drivers. Windows should run normally as usual (or slower) and you should continue your usual activity with it. Should it have caused BSODs during Windows startup, it would mean that a driver that was loaded at Windows startup failed the new Driver Verifier checks and caused Windows to crash.

Just simply continue running things as normal and whenever a crash does appear it should offer improved crashdumps for us to eyeball. Driver Verifier will persist to 'run' even after restarts and crashes, until you manually disable the settings. You can verify it running by going to Driver Verifier again and go to "Display existing settings" if there's anything that is listed, then it means those DV checks are enabled.
VirGnarus is offline  
Old 06-15-2011, 04:13 PM   #5
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



thanks for the info! glad to know it's working then. I assumed it was some sort of stress test that had to run, but I guess not.

speaking of which, I just got my first BSOD since doing those few changes, so I guess I'm not fixed yet :(

anything i should look at in verifier since i BS'd?
Lemcott is offline  
Old 06-15-2011, 05:55 PM   #6
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



my desktop windows manager is crashing all the time now since I made those changes. everytime i open a program or click a link etc. etc. whole screen flashes black and I get the notification.
Lemcott is offline  
Old 06-15-2011, 11:27 PM   #7
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,336
OS: Windows 10, 8.1 + Windbg :)



It sounds like you are experiencing video TDR timeouts (0x117 Live Kernel Events). See if ATI has video driver updates -

https://sysnative.com/0x1/DriverReference.html#atikmdag.sys

Regards. . .

jcgriff2

`
jcgriff2 is offline  
Old 06-27-2011, 02:35 PM   #8
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



Hey all, I'm back...

the blue screens have not gone down in any rate since the last time I posted here, even after a few hardware changes.

I recently updated to this Sapphire 6870 and replaced my WLAN adapter with this rosewill, which I thought was the cause of most of my problems... they were installed on friday the 24th.

I re-ran the blue screen compiler and attached it. I've had the verifier running since my original post, so hopefully the files will have a little more info. as far as I know everything's been updated to the newest drivers.

bsod info v2.zip
Lemcott is offline  
Old 06-27-2011, 06:23 PM   #9
TSF Enthusiast
 
Join Date: Jun 2010
Posts: 2,210
OS: Windows 7 SP1



mmk, well it looks like it's still hardware, especially since it's grown to be even more random, and DV isn't catching it. To add, majority point at IP misalignment, which is caused primarily by RAM or CPU issues (or variations thereof, like PSU or Motherboard).

What hardware have you actually changed lately to try and prevent the BSODs? I can tell that if you already changed out RAM and it still didn't work, then it's most likely CPU or Motherboard. Often times people will change any hardware except these two and still wonder why their BSODs continue, especially the motherboard (because it's such a pain to replace).

If you've been having your PC overclocked, I recommend you reset to factory defaults. Then go ahead and start doing some hardware tests:

RAM: memtest86+ (overnight)
CPU: Prime95 (Torture Test; Blend; Overnight)

Check also voltages and temps with HWMonitor.

Sorry this sounds rather generic response, but I am very confident we got hardware probs, and mainly this kinda stuff is hard to discern unless one ends up doing some heavy testing and eventually swapping.
VirGnarus is offline  
Old 06-27-2011, 07:17 PM   #10
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



I've run memtest multiple times to no avail, but I'll go ahead and run it again for good measure. Prime I've never seen and will definitely give it a run through.

I've actually begun shopping around for a new motherboard already, just looking at which processes are causing me problems I assumed that's the part giving me problems, hopefully after I run prime I'll know for certain.

The only thing I have OC'd is the memory rate. the memory is 1600, which the board can support by OCing the frequency. I used to have even more bsod's when I first built the computer caused by the ram, but since I OC'd it I've never seen another ram related blue screen.
Lemcott is offline  
Old 06-27-2011, 07:45 PM   #11
TSF Enthusiast
 
Join Date: Jun 2010
Posts: 2,210
OS: Windows 7 SP1



Well do note the ones I'm seeing now are quite memory-related.
VirGnarus is offline  
Old 06-27-2011, 08:54 PM   #12
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



really? I must be worst at telling what means what when it comes to blue screens then I thought.

lookng through my ram again I noticed this line:
"8GB memory kit (4 x 2GB) for use with Dual Channel DDR3 Intel Core i5 and Core i7 processors
Intel XMP (Extreme Memory Profile) Support"

I assumed memory can be optimized to be used with different cpu's, but do you think it could be a big of enough difference to cause my problems since I'm running an amd cpu? and if it's mostly memory problems, how does that explain a lot of my crashes being usbport.sys, fltmgr.sys, and other non-memory related problems?
Lemcott is offline  
Old 06-27-2011, 09:18 PM   #13
TSF Enthusiast
 
Join Date: Jun 2010
Posts: 2,210
OS: Windows 7 SP1



I'm not sure in regards to types of memory if it's incompatible or not. Most cases it's reliant on the motherboard for compatibility and not the cpu itself.

As for the different memory problems, understand that if it's memory it's going to affect anything and everything, it's just that whatever is used most frequently (fltmgr especially) is going to have more risk of tripping over the problem than what isn't used much. However the patterns resulting in memory issues are easier to find than, say, PSU issues.

Again, I'm saying the crashes are heavily memory-related, BUT that doesn't mean they are. It's best to continue testing other hardware to reduce possible suspect hardware. Though I assure you, if it's the motherboard or PSU causing the issue, then it's going to manifest itself as anything and everything, from memory-related, to disk, to cpu, and so on. Everything hinges on a reliable motherboard and power supply, so if any of them fails to operate properly, everything else will hurt as a result.
VirGnarus is offline  
Old 06-29-2011, 11:00 AM   #14
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



I dont know why i doubted you guys, but I'm totally starting to believe it may be the RAM.

I've had memtest86+ running all night (current elapsed time is about 16:20 hours) 9 passes 1024 errors. I'm going to go out on a limb and assume that's a bad thing.

is there anything else that could contribute to so many memory failures, or is it a safe bet to go ahead and by new ram?
Lemcott is offline  
Old 06-29-2011, 12:02 PM   #15
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



okay, now I'm really confused.

i took a second to look at the stats on the memtest screen and my RAM seems to be all kinds of screwed up. my ram should be at 1600 speed, with a latency of 8-8-8-24, and here's what the memtest screen says:

Code:
Settings: RAM: 800MHz (DDR1600) / CAS : 11-11-11-29 / DDR3 (64 bits)
this concerns me. As I said earlier, I did OC the mobo to run the ram at 1600 (the ram is 1600, the mobo supports 1600 O.C. [see links in OP]) but did I screw something up? what's going on with those stats?
Lemcott is offline  
Old 06-29-2011, 01:18 PM   #16
TSF Enthusiast
 
Join Date: Jun 2010
Posts: 2,210
OS: Windows 7 SP1



You may have burnt out the ram stick(s). Those cas ratings are purty high, and I wouldn't doubt it's what's causing the heavy instability. Try resetting any OCed BIOS settings to factory default and do more memtest. If it still comes up ill, then it looks like you fried yer RAM.

I can assure at least that unless the motherboard/psu are in horrible shape, they would not be producing as many RAM errors on memtest as you are experiencing. They will present very seldom, occasional errors (though one error is enough to break your PC). What you may be getting is huge strides (strips) of bad memory ranges
VirGnarus is offline  
Old 06-29-2011, 03:07 PM   #17
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



just saw your post, but I already did a couple things myself.

I went into the bios and manually set cas latency (it was actually SET To 11-11-11-29) to the correct settings, and noticed the dram voltage was set to 1.45 when the ram is actually 1.65v so I upped that as well.

so far so good! I've been running a game for a little while and no crashes/BSODs yet, I can only assume the ram was trying to pull too much voltage from the mobo and crashing it?
Lemcott is offline  
Old 06-29-2011, 03:23 PM   #18
TSF Enthusiast
 
Join Date: Jun 2010
Posts: 2,210
OS: Windows 7 SP1



It won't crash the mobo, it'll just cause synch issues and other various problems. It simply wasn't gettin enough juice.
VirGnarus is offline  
Old 07-05-2011, 08:10 PM   #19
Registered Member
 
Join Date: Jun 2011
Posts: 24
OS: windows 7 Pro 64bit sp1



So I've been running relatively stable since making the changes, but I seem to still be getting a 0x3B after about 6-7 hours of heavy usage (which is still quite an improvement).

Looking around in my bios again I noticed that SPD says my ram is 9-9-9-24 when everywhere online, and the box it came in, says 8-8-8-24. any chance corsair put the wrong ram into the heat shields? or is SPD not all that reliable?

the other thing that bugs me is that I can't change the DDR VTT voltage which is set to .750v. if you remember, i had to set DRAM voltage to 1.650v, and I may be mistaken, but isn't there something about VTT where it has to be like .50v within range of the DRAM?

Here's what the bios says about ram: some of these just confuse me, so I'm hoping one of you might be able to tell me what's up:

(formatting: setting>currently set to>spd)
cas latency>8>9
Ras to Cas>8>9
row precharge>8>9
min ras active time>24>24
1t/2t com timing>2>-->-- (that's seriously all it has, just "--")
twtr com delay>6>5
trfc0 for dimm1>110ns>110ns
trfc2 for dimm2>110ns>110ns
trfc1 for dimm3>110ns>110ns
trfc3 for dimm4>110ns>110ns
write recovery time>12>10
precharge>6>5
row cycle time>41>34
ras to ras delay>6>5

all the ones that aren't set to SPD are settings I've never changed (except the 8-8-8-24), so they're set to the defaults. you think any of these might be causing my problem? as opposed to the 8-8-8-24, I'm going to hold off on changing any of these until I hear from you guys. if there are any other settings you'd be interested in seeing, just let me know and I'll post em.

the only other possible thing it might be is that I'm using a pcie 2.1 x16 video card in a pcie 2.0 x16 slot. I'm fairly certain this isn't a problem, but it may be worth pointing out, iunno.


oh, and a few little questions/things about bios because maybe they mean something, and/or I just like learning :)
-"cpu clock ratio" is set to 3400mhz, which is all fine and good. but there's a seperate "cpu frequency(Mhz)" set to "200" that can only be edited by setting "CPU Host CLock Control" to manual. whats up with that?
-read somewhere someone was having problems with the same ram, and they upped uncore voltage from 1.1 to 1.2v. does uncore voltage have another name? I can't seem to find it anywhere in my bios (note: pretty sure this only matters for intel chipsets, but i have no idea).
-manually set HT link width to 16bit instead of auto, figured it cant hurt.
-bios says my case is open when it's not, the screws aren't in however, so i dont know if that affects it.
-I have my RAM fan plugged into the NB Fan slot (only open port and i dont have an NB fan), while just sitting in bios it's running at a whopping 4218 RPM. should I worry? (cpu is 2606rpm)
Lemcott is offline  
Old 07-06-2011, 10:42 AM   #20
Administrator
Team Manager, Gaming
Team Manager, Microsoft Support
Team Manager, Hardware Team
Microsoft MVP
 
Wrench97's Avatar

Microsoft Most Valuable Professional
 
Join Date: May 2008
Location: S.E. Pennsylvania
Posts: 53,913
OS: Win7



I see a couple issues with the ram,
1 you will often see issues when filling all the ram ram slots and running overclocked ram, 1333 is the native speed for AMD controllers above that is considered OC settings.
DDR - Double Data Rate, the memory reads and writes on the up and down of the frequency pulse so is CPUz(HW Monitor) reads it as 800, 800x2= 1600.

2 The ram you're using has Intel OC settings built into the micro code on the sticks, doesn't mean it won't work but filling the all the slots and Overclocking will be problematic.

First thing I would do is pull the 2 sticks out of the second channel, set the remaining sticks to 1333 and run the system to see if it's stable.

What Voltage readings did you get for the 12v, 5v, and 3.2v power rails?
If HwMonitor did not give them to you look in the Bios on the PC health page.
How about the CPU and Chipset(system) temps?
Wrench97 is online now  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
burn process failed ! Nero Vision 4
I am new to using Nero and burning DVD's so I really need help with this. Everytime I try to burn a DVD it gets about 80% done and than I get a message saying, "Burn Process Failed. An error log file was created that can be very helpful in diagnosing problems." My computer is Windows Vista and my...
kathern.otter Other Hardware Support 4 04-02-2011 08:34 PM
Multiple random BSODs, whits end
I built a custom pc in august, it started getting BSODs in december. I reinstalled windows, didn't help. bluescreens started getting worse, reinstalled windows again, helped for a week or so but they started again. There are no dump files from BSODs, but I have been taking pictures of the error...
whitenova BSOD, App Crashes And Hangs 12 02-25-2011 03:00 PM
Assistance with trying to complete a event procedure using VB 8 (VB.NET)
I've written a program that calculates a t-shirt order and stores the summary. The person selects the various shirt sizes through radio buttons. Now I am trying to go back and write an event procedure using the case function, but I'm having issues. I've posted my code as is. I'm having trouble...
tigerfansince84 Programming 0 02-16-2011 11:47 AM
[SOLVED] VCExpress Problem, Probably AppData\Permissions Problem?
I think it should be related to this forum because I think the problem is something with AppData \ Permissions which is related to Windows 7. I'm having a problem while running\installing Visual C++. The problem started 2 days ago, it did work before. When I'm trying to run I'm getting this...
benben12 Windows 7 , Windows Vista Support 8 02-09-2011 01:45 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 04:26 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts