Sign in with
Sign up | Sign in
Your question
Solved

Having a lot of crashing, suspecting GPU driver

Tags:
  • GPUs
  • AMD
  • Windows 7
Last response: in Windows 7
Share
July 29, 2014 10:22:29 AM

Hey all, recently I've been having some BSODs and i have the who crashed program (so i could possibly find out why it keeps crashing), and it keeps saying its my AMD driver no matter what the crash type is....I've updated from AMD's website, and I've uninstalled them completely and re-installed them but to no avail..

here's my specs:
CPU: intel i5 4670k
GPU: MSI Radeon 7770
like i said I've been having some problems with my computer crashing and who crashed keeps saying its my AMD driver so I'm at a loss as what to do....
any help will be greatly appreciated!
Thanks!

More about : lot crashing suspecting gpu driver

a b À AMD
a b $ Windows 7
July 29, 2014 10:27:05 AM

we need the stop code that happens with the blue screen, it usually looks like 0x0000005b or 0x000000fe (that format). it will tell us all the information needed.
m
0
l
July 29, 2014 10:38:24 AM

where would i find the stop code?
m
0
l
Related resources
a b À AMD
a b $ Windows 7
July 29, 2014 10:51:41 AM

It should be displayed when it blue screens. You can also post the mini-dump file that should show exactly what's going on or post the who crashed report.
m
0
l
a b À AMD
a b $ Windows 7
July 29, 2014 1:42:18 PM

What driver package and version do you have installed? It might be TOO new for your OS. Was it an automatically updated driver or one you installed? I'd go into control panel and right click on your display adapter then select uninstall. Make sure to check the box that says "uninstall device driver" too. Then go into programs and features and uninstall any applications related to the card including the AMD catalyst control manager and the AMD Vision engine if they are there. Use the express feature when uninstall begins and uninstall everything. Prior to doing this though go to the Catalyst website and download the 14.4 driver package (Don't download the beta 14.6 or 14.7 package) so you already have it to install afterwards. Then reboot and when you get back into windows install the driver package.:

http://support.amd.com/en-us/download/desktop?os=Window...
m
0
l
July 29, 2014 2:27:24 PM

darkbreeze said:
What driver package and version do you have installed? It might be TOO new for your OS. Was it an automatically updated driver or one you installed? I'd go into control panel and right click on your display adapter then select uninstall. Make sure to check the box that says "uninstall device driver" too. Then go into programs and features and uninstall any applications related to the card including the AMD catalyst control manager and the AMD Vision engine if they are there. Use the express feature when uninstall begins and uninstall everything. Prior to doing this though go to the Catalyst website and download the 14.4 driver package (Don't download the beta 14.6 or 14.7 package) so you already have it to install afterwards. Then reboot and when you get back into windows install the driver package.:

http://support.amd.com/en-us/download/desktop?os=Window...


i have 14.4 and i went to AMD's site to install it, should i still uninstall everything then re-install?

m
0
l
a b À AMD
a b $ Windows 7
July 29, 2014 9:43:06 PM

Yes. Do just what I outlined. Go into programs and features in control panel and uninstall CCC and the AMD Vision engine. Then go into control panel>device manager right click on your display adapter or graphics card and select uninstall and make sure you check the box that says to uninstall the driver as well. After that reboot. Then reinstall the AMD 14.4 CCC but choose the custom install option and don't install the optional gaming enhancement at this time or the Quickstream option, if either of those are there or checked, uncheck them. Install, reboot and try it again.
m
0
l
July 30, 2014 9:05:14 AM

darkbreeze said:
Yes. Do just what I outlined. Go into programs and features in control panel and uninstall CCC and the AMD Vision engine. Then go into control panel>device manager right click on your display adapter or graphics card and select uninstall and make sure you check the box that says to uninstall the driver as well. After that reboot. Then reinstall the AMD 14.4 CCC but choose the custom install option and don't install the optional gaming enhancement at this time or the Quickstream option, if either of those are there or checked, uncheck them. Install, reboot and try it again.


I will try it when I get the chance, thanks for the info.
m
0
l
August 4, 2014 12:15:58 PM

OK, I uninstalled everything and re-installed it and everything is going smoothly so far! thanks for the help guys!
m
0
l
a b À AMD
a b $ Windows 7
August 4, 2014 12:58:22 PM

Glad to hear it. If you have problems in the future, don't hesitate to come back and ask. Take care.
m
0
l
August 4, 2014 5:08:54 PM

darkbreeze said:
Glad to hear it. If you have problems in the future, don't hesitate to come back and ask. Take care.

well, it just crashed.. again.... i'm at a loss as what to do now
m
0
l
a b À AMD
a b $ Windows 7
August 4, 2014 6:47:20 PM

Ok, so go into windows explorer and find the dump file which should be located in C:/Windows/Minidump and named minidump.dmp. Either email me a copy of the file or post it to one of the free online services like Google drive, MS Onedrive or filedropper ( http://www.filedropper.com/) and post a link to the file so one of us can access it. I'll see if I can find any clues using it or try to get one of the more experienced Tom's members to analyze it. Usually guy's like johnbl can pick up a ton of issues using the dump file that most would be clueless about.

If you prefer to email me the file, PM me and I'll give you the email address.
m
0
l
August 4, 2014 6:57:33 PM

darkbreeze said:
Ok, so go into windows explorer and find the dump file which should be located in C:/Windows/Minidump and named minidump.dmp. Either email me a copy of the file or post it to one of the free online services like Google drive, MS Onedrive or filedropper ( http://www.filedropper.com/) and post a link to the file so one of us can access it. I'll see if I can find any clues using it or try to get one of the more experienced Tom's members to analyze it. Usually guy's like johnbl can pick up a ton of issues using the dump file that most would be clueless about.

If you prefer to email me the file, PM me and I'll give you the email address.

thanks for your help, it is much appreciated! here's the link:
https://drive.google.com/file/d/0B9My10LCgiuTTWlkbTRMVU...
m
0
l
a b À AMD
a b $ Windows 7
August 4, 2014 7:13:12 PM

Ok, so translated to whocrashed, which is probably not as good as interpreting the actual dump file itself, it looks like a driver issue, which is usually the case. I don't know what driver or why but possibly somebody else will chime in with some answers and I'll ask around. In the meantime, make sure the rest of your drivers are all up to date. You can go into device manager and manually check for updated drivers by right clicking on the significant components and selecting update driver, update automatically. Some times updated drivers that didn't get picked up using windows update will pop up here. Apparently there's a conflict or faulty driver somewhere. Here's what whocrashed came up with.

On Mon 8/4/2014 11:27:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080414-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
m
0
l
August 5, 2014 7:53:51 AM

darkbreeze said:
Ok, so translated to whocrashed, which is probably not as good as interpreting the actual dump file itself, it looks like a driver issue, which is usually the case. I don't know what driver or why but possibly somebody else will chime in with some answers and I'll ask around. In the meantime, make sure the rest of your drivers are all up to date. You can go into device manager and manually check for updated drivers by right clicking on the significant components and selecting update driver, update automatically. Some times updated drivers that didn't get picked up using windows update will pop up here. Apparently there's a conflict or faulty driver somewhere. Here's what whocrashed came up with.

On Mon 8/4/2014 11:27:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080414-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

ok, I checked for updates on almost everything and there was 2 updates, 1 was for the intel HD graphics and the other one i don't remember..... now there is a yellow triangle with a exclamation point beside something called "teredo tunneling adapter"
and i cant update the driver software. when i go to properties it says "the device cannot start (code 10)," idk if this helps or not
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 12:05:39 PM

Are gaming online when your system crashes or are you just gaming locally? What kind of router do you have? We need to know if your router supports IPv6 protocol. If it doesn't, we need to disable the teredo tunneling adapter and IPv6 profile in networking.
m
0
l
August 5, 2014 1:57:47 PM

darkbreeze said:
Are gaming online when your system crashes or are you just gaming locally? What kind of router do you have? We need to know if your router supports IPv6 protocol. If it doesn't, we need to disable the teredo tunneling adapter and IPv6 profile in networking.


that's the thing, it just crashes at random. sometimes it wont even come out of sleep mode. My router is a belkin AC 1200 dual-band router, i think it has iPv6, but i'm not 100 percent sure... if that's not what you were needing let me know
m
0
l
August 5, 2014 2:22:23 PM

I had this problem with a GTX 660. Go into your Mobo BIOS and alternate between settings for your iGPU (integrated graphics). There should be a setting for iGPU memory, try switching between manual and auto. Mine was set to a large amount and when I set it to auto, the BSODs stopped.
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 3:01:34 PM

Yeah, this is definitely either a driver or memory issue. And the memory issue could very well be related to the iGPU. But it might also be a bad stick of RAM or one that's going bad. All your previous dump files indicate a software driver though. It almost has to be one of those. It would be nice if we could get one of the code guys to do a thorough analysis of those crashes. I'm positive there's something in there that's pointing directly at it I just don't know what it is.
m
0
l
August 5, 2014 3:10:10 PM

ok, so i went into my bios and there wasn't a setting for manual or auto, right now its set on 64M (megabytes i assume?). would i be better off just disabling them all together?
m
0
l
August 5, 2014 4:06:18 PM

Hscumbie said:
ok, so i went into my bios and there wasn't a setting for manual or auto, right now its set on 64M (megabytes i assume?). would i be better off just disabling them all together?


Yes, do that. Also try changing an iGPU setting called 'standby' or something like that. Download this: http://www.wagnardmobile.com/DDU/ , run the .exe, click yes to restart in safe mode. When it boots up, select 'NVIDIA' tab, click 'clean and do not restart', then select 'AMD' and click 'clean and restart'. When it reboots, install the latest Beta driver. I advise you to download your driver's setup file from AMD first, then do this.
m
0
l
August 5, 2014 4:20:40 PM

wait, so i need to go to AMD's site and download the latest beta driver? or just the latest official driver?
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 4:21:37 PM

Ok, so, I wouldn't install the beta drivers. Myself and everybody else I know who has used them has had nothing but issues with them. Plus, you're using windows 7, not 8.1, and really don't need them. The 14.4 drivers are known to be stable with Windows 7 and most have no issues due to the build. You can try the new drivers, but considering it's an older system with an older card (The chip was released back in 2012) you shouldn't need the newer beta drivers.

You can try it though and if it creates more issues or just doesn't work you can always just uninstall it with the utility gyking mentioned and then install the stable drivers. Either way, I don't think we're going to solve the issue like this. I think we really need to see what specifically is causing the issue. But it's your pc.
m
0
l
August 5, 2014 4:27:04 PM

darkbreeze said:
Ok, so, I wouldn't install the beta drivers. Myself and everybody else I know who has used them has had nothing but issues with them. Plus, you're using windows 7, not 8.1, and really don't need them. The 14.4 drivers are known to be stable with Windows 7 and most have no issues due to the build. You can try the new drivers, but considering it's an older system with an older card (The chip was released back in 2012) you shouldn't need the newer beta drivers.

You can try it though and if it creates more issues or just doesn't work you can always just uninstall it with the utility gyking mentioned and then install the stable drivers. Either way, I don't think we're going to solve the issue like this. I think we really need to see what specifically is causing the issue. But it's your pc.


i agree darkbreeze, ill try it anyways. whats there to lose.
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 4:32:51 PM

Nothing to lose really. How do you feel about doing a new installation or did we already go through that. I try to help so many different threads I can't remember sometimes without looking back through. Are you able to back everything up and do a clean install? That might end up being the only option. How long have you been running that particular instance of your installation. IOW, how long has that install of windows been on your machine?
m
0
l
August 5, 2014 4:54:31 PM

ever since April or May, so about 3-4 months. and yes, i back up and do a system image every month. to be honest i don't want to do a re-install its just to tedious for me. anything could go wrong. but if its what it takes then i will do it, only after the .dmp file is analyzed by someone and i know for a fact that a re-install will work
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 4:56:54 PM

Were you having similar problems that caused you to do the new install back in April?
m
0
l
August 5, 2014 5:33:47 PM

darkbreeze said:
Were you having similar problems that caused you to do the new install back in April?


no, that's actually when i built this rig. so there's only been 1 install
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 5:59:40 PM

Ok, and so has the problem existed ever since then, or was everything fine for a period of time and then just started happening with no changes to hardware and no new installations? I realize we've probably already covered this but sometimes it doesn't hurt to ask again because something may get jogged in memory.
m
0
l
August 5, 2014 6:19:01 PM

darkbreeze said:
Ok, and so has the problem existed ever since then, or was everything fine for a period of time and then just started happening with no changes to hardware and no new installations? I realize we've probably already covered this but sometimes it doesn't hurt to ask again because something may get jogged in memory.


if i remember right it was fine for 2-3 weeks then i started having problems. there wasn't any hardware changes.
or new installations.
m
0
l
August 5, 2014 7:02:47 PM

Hscumbie said:
darkbreeze said:
Ok, and so has the problem existed ever since then, or was everything fine for a period of time and then just started happening with no changes to hardware and no new installations? I realize we've probably already covered this but sometimes it doesn't hurt to ask again because something may get jogged in memory.


if i remember right it was fine for 2-3 weeks then i started having problems. there wasn't any hardware changes.
or new installations.


Do you use DAEMON Tools? If so, uninstall it. It's a common Imaging software that interferes with drivers.
m
0
l
August 5, 2014 7:10:00 PM

gyking94 said:
Hscumbie said:
darkbreeze said:
Ok, and so has the problem existed ever since then, or was everything fine for a period of time and then just started happening with no changes to hardware and no new installations? I realize we've probably already covered this but sometimes it doesn't hurt to ask again because something may get jogged in memory.


if i remember right it was fine for 2-3 weeks then i started having problems. there wasn't any hardware changes.
or new installations.


Do you use DAEMON Tools? If so, uninstall it. It's a common Imaging software that interferes with drivers.

i did not use it, and to be honest i have never heard of it either. i use windows backup to do my PC imaging and backups
m
0
l
August 5, 2014 7:40:17 PM

Hscumbie said:
gyking94 said:
Hscumbie said:
darkbreeze said:
Ok, and so has the problem existed ever since then, or was everything fine for a period of time and then just started happening with no changes to hardware and no new installations? I realize we've probably already covered this but sometimes it doesn't hurt to ask again because something may get jogged in memory.


if i remember right it was fine for 2-3 weeks then i started having problems. there wasn't any hardware changes.
or new installations.


Do you use DAEMON Tools? If so, uninstall it. It's a common Imaging software that interferes with drivers.

i did not use it, and to be honest i have never heard of it either. i use windows backup to do my PC imaging and backups


Reset the motherboard BIOS to default settings. If that doesn't work, then we can be sure it's a software/driver issue, because you never had any problems for the first 2-3 week as you stated.
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 7:51:46 PM

Now we just need to have this interpreted so we can determine which driver or device caused it or if it was a memory fault.

The only thing I could find so far was this but it may not be accurate, I'm just not sure:

"Probably a video driver causing it, seems to be common in W7, but other hardware can cause it also, bad memory modules are also highly suspect."



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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+0
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: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff88002fff268 -- (.exr 0xfffff88002fff268)
ExceptionAddress: fffff800034e6740 (nt!KiProcessExpiredTimerList+0x0000000000000110)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88002fff310 -- (.trap 0xfffff88002fff310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800a0febf0
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034e6740 rsp=fffff88002fff4a0 rbp=fffffa800a5f48b0
r8=fffff88002fd9301 r9=0000000000000002 r10=00000000000000b4
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!KiProcessExpiredTimerList+0x110:
fffff800`034e6740 f00fba2f07 lock bts dword ptr [rdi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800034d35be to fffff800034dbb90

STACK_TEXT:
fffff880`02ffe348 fffff800`034d35be : fffffa80`0ab81cf0 fffffa80`07b4ae98 fffff880`02ffeac0 fffff800`03506a90 : nt!KeBugCheck
fffff880`02ffe350 fffff800`0350675d : fffff800`036ea380 fffff800`03627260 fffff800`03466000 fffff880`02fff268 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffe380 fffff800`03505535 : fffff800`0362b038 fffff880`02ffe3f8 fffff880`02fff268 fffff800`03466000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffe3b0 fffff800`035164c1 : fffff880`02fff268 fffff880`02ffeac0 fffff880`00000000 61fffa80`0a1038d0 : nt!RtlDispatchException+0x415
fffff880`02ffea90 fffff800`034db242 : fffff880`02fff268 fffffa80`0a5f48b0 fffff880`02fff310 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02fff130 fffff800`034d9b4a : fffffa80`0a5f4a90 fffff880`02fff390 fffffa80`0a108940 00000000`00000002 : nt!KiExceptionDispatch+0xc2
fffff880`02fff310 fffff800`034e6740 : fffffa80`0a0fec10 fffffa80`09e29168 fffffa80`09e29168 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02fff4a0 fffff800`034e65de : 0000002a`637a1fb3 fffff880`02fffb18 00000000`0011ceb4 fffff880`02fdac08 : nt!KiProcessExpiredTimerList+0x110
fffff880`02fffaf0 fffff800`034e63c7 : 0000000e`0ac029c1 0000000e`0011ceb4 0000000e`0ac02969 00000000`000000b4 : nt!KiTimerExpiration+0x1be
fffff880`02fffb90 fffff800`034d38ca : fffff880`02fd7180 fffff880`02fe1fc0 00000000`00000000 fffff800`03422dec : nt!KiRetireDpcList+0x277
fffff880`02fffc40 00000000`00000000 : fffff880`03000000 fffff880`02ffa000 fffff880`02fffc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`034d35be 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb

FAILURE_BUCKET_ID: X64_0x1e_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1e_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 7:58:11 PM

Have you tried pulling a memory module and running with only one installed (Assuming you have two modules installed.) Then if the same thing happens pull the installed module and plug the other one in and try again. If no errors occur it's probably a bad module. Have you run memtest or Seatools? You might want to run both. You can just download seatools for windows. Run the short DST.
m
0
l
August 5, 2014 8:09:33 PM


darkbreeze said:
Have you tried pulling a memory module and running with only one installed (Assuming you have two modules installed.) Then if the same thing happens pull the installed module and plug the other one in and try again. If no errors occur it's probably a bad module. Have you run memtest or Seatools? You might want to run both. You can just download seatools for windows. Run the short DST.

i have run memtest and everything came back fine. here's the problem though, i can go for weeks with out a crash, and then sometimes it will repeatedly crash. there isn't an exact pinpoint as to where and when it will crash. so should i still go with 1 stick (yes i have 2, it's a 2x4)?
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 8:20:36 PM

I would. Try one stick or, if you have other RAM try a different pair. Run it until it either crashes or your sure it won't. Then, just to be sure, switch sticks. It should crash fairly soon, but it might not do it immediately, if the other stick is the culprit.
m
0
l
August 5, 2014 8:25:38 PM

darkbreeze said:
I would. Try one stick or, if you have other RAM try a different pair. Run it until it either crashes or your sure it won't. Then, just to be sure, switch sticks. It should crash fairly soon, but it might not do it immediately, if the other stick is the culprit.


ok will do. thanks for the help! i will let you know what happens.
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 8:38:30 PM

Run the seatools utility too, just for shits and giggles.
m
0
l
August 5, 2014 8:45:53 PM

darkbreeze said:
Run the seatools utility too, just for shits and giggles.

Ok, could you send me a link to the site?
I would hate to get the wrong one.
m
0
l
August 5, 2014 8:49:55 PM

Ok thanks darkbreeze for all your help so far, it is much appreciated!
m
0
l
a b À AMD
a b $ Windows 7
August 5, 2014 9:35:40 PM

Sometimes these things can be just, bastards! Other times you can get the problem right off the bat.
m
0
l
August 6, 2014 9:33:27 AM

Ok, well i don"t know if i just had a crash or not. with the one stick of RAM i couldn't come out of sleep mode, this has also happened to me with both modules installed too. so i switched them out. ill see if it happens again. I also ran the seatools utility and the short dst passed. is there anything else i should do?
m
0
l
a b À AMD
a b $ Windows 7
August 6, 2014 12:27:11 PM

Did this happen with both sticks of RAM installed singly? In other words, did you try both sticks by themselves and it happened each time? I think this might be a separate issue as I've come across this sleep issue before. Open an elevated prompt, ie, command prompt as administrator, and run powercfg.exe /hibernate off to disable hibernation. On some computers is seems to cause all sorts of goofy problems with the sleep modes. You do mean that it boots normally but then once you allow it to sleep it doesn't want to come out of sleep correct?
m
0
l
August 6, 2014 2:05:40 PM

darkbreeze said:
Did this happen with both sticks of RAM installed singly? In other words, did you try both sticks by themselves and it happened each time? I think this might be a separate issue as I've come across this sleep issue before. Open an elevated prompt, ie, command prompt as administrator, and run powercfg.exe /hibernate off to disable hibernation. On some computers is seems to cause all sorts of goofy problems with the sleep modes. You do mean that it boots normally but then once you allow it to sleep it doesn't want to come out of sleep correct?


It will come out of sleep, some times it won't. I'm pretty sure that I already disabled hibernation, but I'll be sure. I had both sticks installed at the same time and it would still only sometimes come out of sleep mode. I switched sticks this morning cause it wouldn't come out of sleep mode and I haven't had any problems coming out of it since.
m
0
l
a b À AMD
a b $ Windows 7
August 6, 2014 2:08:59 PM

It could very well be a bad stick then. Keep the one stick in by itself now and let's see if the problems come back. If they don't come back after a day or two I'd say get a new matched pair or if they are under warranty, then RMA the RAM.
m
0
l
a b À AMD
a b $ Windows 7
August 6, 2014 2:10:59 PM

Did you ever run memtest? Run this version http://www.memtest.org/ and run it for a good couple hours. Some problems with RAM don't show up until the RAM has had a chance to heat up and begin leaking from capacitors or come back to previously stored data and find an error because there's been leakage.
m
0
l
August 7, 2014 8:22:52 AM

darkbreeze said:
Did you ever run memtest? Run this version http://www.memtest.org/ and run it for a good couple hours. Some problems with RAM don't show up until the RAM has had a chance to heat up and begin leaking from capacitors or come back to previously stored data and find an error because there's been leakage.

I have run memtest before, but i don't remember how long though. I'll do it again to be sure. should i put both sticks in? or just the suspect one? i haven't had anymore problems ever since i replaced the stick. it must be a bad stick.
m
0
l
      • 1 / 2
      • 2
      • Newest
!