I've been freezing in firefox and crashing in Bioshock DLC, but I can't figure out what the issue is. I feel like the new drivers are crashing more often. Does anyone have a clue which is more stable for my GPU? Here is the specs and the things I have already tried, any help would be great. BTW, I will be gone this weekend for my birthday, so it may take me time to respond.
Specs
CPU- I5-2500K overclocked to 4.4, already tried stock settings and didn't help. I used to have it at 4.7 without any issues too. CPU stays around 40-45C in any game at that speed of 4.4.
RAM- Corsair 8 gigs at 9-9-9-24. Ran Memtest for 3 hours and no errors.
Motherboard- Asus P8P67 Pro rev 3.1, all up to date drivers including bios.
GPU- GTX 560 Ti (I think PNY, I forgot) at normal no OC. Ran Furmark at highest setting for 30 mins, no errors.
Ran every single virus check I could find and they didn't pick up anything. Here is the last Windows freeze that I can show in the last few times are these. (No BSOD's, just pure freezing)
On Wed 11/13/2013 11:12:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111313-20638-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x13080C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF9600013080C, 0x0, 0x1)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 11/10/2013 6:41:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-17472-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800801D40C)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x0, 0xFFFFF8800801D40C, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
I've been freezing in firefox and crashing in Bioshock DLC, but I can't figure out what the issue is. I feel like the new drivers are crashing more often. Does anyone have a clue which is more stable for my GPU? Here is the specs and the things I have already tried, any help would be great. BTW, I will be gone this weekend for my birthday, so it may take me time to respond.
Specs
CPU- I5-2500K overclocked to 4.4, already tried stock settings and didn't help. I used to have it at 4.7 without any issues too. CPU stays around 40-45C in any game at that speed of 4.4.
RAM- Corsair 8 gigs at 9-9-9-24. Ran Memtest for 3 hours and no errors.
Motherboard- Asus P8P67 Pro rev 3.1, all up to date drivers including bios.
GPU- GTX 560 Ti (I think PNY, I forgot) at normal no OC. Ran Furmark at highest setting for 30 mins, no errors.
Ran every single virus check I could find and they didn't pick up anything. Here is the last Windows freeze that I can show in the last few times are these. (No BSOD's, just pure freezing)
On Wed 11/13/2013 11:12:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111313-20638-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x13080C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF9600013080C, 0x0, 0x1)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 11/10/2013 6:41:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-17472-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800801D40C)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x0, 0xFFFFF8800801D40C, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Oh and Firefox is updated, windows 7, and everything else.
Oh and Firefox is updated, windows 7, and everything else.
Try uninstalling and reinstalling your videocard driver to try to fix the second one.
If that fails try what it says here: http://technet.microsoft.com/en-us/library/cc957625.aspx
Try uninstalling and reinstalling your videocard driver to try to fix the second one.
If that fails try what it says here: http://technet.microsoft.com/en-us/library/cc957625.aspx
to really uninstall and re-install your video driver you should use a program like driver sweeper
http://www.guru3d.com/content_page/guru3d_driver_sweeper.html
to really uninstall and re-install your video driver you should use a program like driver sweeper
http://www.guru3d.com/content_page/guru3d_driver_sweeper.html
yea i have the same problem, it is most likely due to new drivers... downgrading should fix it, I'm about to do it now
yea i have the same problem, it is most likely due to new drivers... downgrading should fix it, I'm about to do it now
ikpureyea i have the same problem, it is most likely due to new drivers... downgrading should fix it, I'm about to do it now
What did you downgrade to?
[quote=ikpure]yea i have the same problem, it is most likely due to new drivers... downgrading should fix it, I'm about to do it now[/quote]
What did you downgrade to?
ive been getting the kmode exception not handled and whea_uncorrectable error a ton lately. will probably reinstall windows and see if it goes away
ive been getting the kmode exception not handled and whea_uncorrectable error a ton lately. will probably reinstall windows and see if it goes away
Ok, I have tried everything in this thread, but I think the issue is a buggy updated driver, what nvidia drivers are people using for 560TI, or anything close to it?
Sorry, for the late post but we were stuck in a cabin last night after a tornado hit about 10 mins away from where we were staying. While, I guess it was a free night, it was still scary as hell without power in the middle of the woods without cell phone signals.
Ok, I have tried everything in this thread, but I think the issue is a buggy updated driver, what nvidia drivers are people using for 560TI, or anything close to it?
Sorry, for the late post but we were stuck in a cabin last night after a tornado hit about 10 mins away from where we were staying. While, I guess it was a free night, it was still scary as hell without power in the middle of the woods without cell phone signals.
FzeroSorry, for the late post but we were stuck in a cabin last night after a tornado hit about 10 mins away from where we were staying. While, I guess it was a free night, it was still scary as hell without power in the middle of the woods without cell phone signals.
Its like a horror movie, glad you're safe.
[quote=Fzero]
Sorry, for the late post but we were stuck in a cabin last night after a tornado hit about 10 mins away from where we were staying. While, I guess it was a free night, it was still scary as hell without power in the middle of the woods without cell phone signals.[/quote]
Its like a horror movie, glad you're safe.
I have a 560TI, I'm just using the 306.97 drivers on the site, I haven't had any problems like what you're talking about it. I remember something similar would happen for a few days after over-overclocking my CPU, you might want to try manually clearing CMOS(i.e, removing the battery for a good 2 minutes) to make sure. That's what fixed a similar problem for me, at least.
I have a 560TI, I'm just using the 306.97 drivers on the site, I haven't had any problems like what you're talking about it. I remember something similar would happen for a few days after over-overclocking my CPU, you might want to try manually clearing CMOS(i.e, removing the battery for a good 2 minutes) to make sure. That's what fixed a similar problem for me, at least.
WaldoI have a 560TI, I'm just using the 306.97 drivers on the site, I haven't had any problems like what you're talking about it. I remember something similar would happen for a few days after over-overclocking my CPU, you might want to try manually clearing CMOS(i.e, removing the battery for a good 2 minutes) to make sure. That's what fixed a similar problem for me, at least.
The latest drivers are 331.65, so that maybe the issue. Clearing CMOS should not do anything since I have not changed a single bios setting since having these issues, so I don't think it has anything to do with my settings.
[quote=Waldo]I have a 560TI, I'm just using the 306.97 drivers on the site, I haven't had any problems like what you're talking about it. I remember something similar would happen for a few days after over-overclocking my CPU, you might want to try manually clearing CMOS(i.e, removing the battery for a good 2 minutes) to make sure. That's what fixed a similar problem for me, at least.[/quote]
The latest drivers are 331.65, so that maybe the issue. Clearing CMOS should not do anything since I have not changed a single bios setting since having these issues, so I don't think it has anything to do with my settings.
This case is closed, after going back to my old 314.xx drivers, I have no issues. At least it wasn't the video card dying again.
This case is closed, after going back to my old 314.xx drivers, I have no issues. At least it wasn't the video card dying again.
I lied, after doing everything I still crashed while talking to some on my Friends lists on steam.
I lied, after doing everything I still crashed while talking to some on my Friends lists on steam.
LOL, I guess the new drivers kick up the voltage on fermi cards and cause a lot of issues, including frying. If you have any fermi cards, downgrade ASAP.
LOL, I guess the new drivers kick up the voltage on fermi cards and cause a lot of issues, including frying. If you have any fermi cards, downgrade ASAP.
On the plus side, they ended up shipping me a 650 model instead of the 560. Even better, it seems it is not the card but something else, so a free small upgrade
On the plus side, they ended up shipping me a 650 model instead of the 560. Even better, it seems it is not the card but something else, so a free small upgrade
Ok, so I still crashing. I've wiped windows and got a new video card. So I am thinking that it's either the memory or HDD. Regarding the memory, what's the chance of it being a bad stick when I show no errors on memtest?
Ok, so I still crashing. I've wiped windows and got a new video card. So I am thinking that it's either the memory or HDD. Regarding the memory, what's the chance of it being a bad stick when I show no errors on memtest?