Can't figure out the cause - screen flickering/lagging issues
in IT Support ·
Well, if you tried it on a friend's PC and the exact same issue popped up with your case, then we're definitely looking at a Hardware problem...
Home ›
Nicholas Miller6 › Posts
Posts by Nicholas Miller6
62 posts shown.
Can't figure out the cause - screen flickering/lagging issues
in IT Support ·
I’m thinking the power supply might be the culprit here.
If you can, maybe try swapping it out for a stronger one and see if that helps.
If you can, maybe try swapping it out for a stronger one and see if that helps.
Can't figure out the cause - screen flickering/lagging issues
in IT Support ·
Have you tried plugging in a different monitor yet?
GPU overheating issues
in Hardware ·
When was the last time you actually sat down to install those Catalyst drivers or run a BIOS update?
Recovered photos coming up white after undelete?
in IT Support ·
Maybe try running a Pandora recovery to see if that fixes anything.
Best CPU cooler recommendations?
in Desktops ·
I think I'll pass on those two: http://www.spire-corp.com/cpu-cooler...85s1-v2/specs/
http://www.lc-power.de/index.php?id=311
http://www.lc-power.de/index.php?id=311
Best CPU cooler recommendations?
in Desktops ·
A few of those coolers you mentioned won't fit my socket. Thanks for the suggestions though, I'll definitely keep them in mind.
Best CPU cooler recommendations?
in Desktops ·
My temps are sitting at a max of 30.6 right now.
The temperature isn't really the issue; it's more that the fan is constantly pinned at 100%. Everything is set to AUTO in my BIOS, haha, so it’s getting a little loud...
I originally figured since it stays at 100% even on AUTO, maybe I should just swap it out—it feels like it might be struggling to keep up or something. xd
Now I'm torn on whether I should actually replace it. If you think I should, does anyone have a recommendation from here? http://www.amazon.com/cpu-coolers/b?node=12488712&tpkp=2?
The temperature isn't really the issue; it's more that the fan is constantly pinned at 100%. Everything is set to AUTO in my BIOS, haha, so it’s getting a little loud...
I originally figured since it stays at 100% even on AUTO, maybe I should just swap it out—it feels like it might be struggling to keep up or something. xd
Now I'm torn on whether I should actually replace it. If you think I should, does anyone have a recommendation from here? http://www.amazon.com/cpu-coolers/b?node=12488712&tpkp=2?
Best CPU cooler recommendations?
in Desktops ·
I was actually struggling a bit with the RPM readings... on my Intel Core i5-3570K, I'm just using the stock cooler, and according to Open Hardware Monitor, it tops out at 3488 RPM.
The noise isn't a huge deal to me, though obviously, quieter is always better.
I was thinking about picking up a different cooler... so, shadowlynx102, are you saying I should grab one specifically for the higher RPMs?
The noise isn't a huge deal to me, though obviously, quieter is always better.
I was thinking about picking up a different cooler... so, shadowlynx102, are you saying I should grab one specifically for the higher RPMs?
Best CPU cooler recommendations?
in Desktops ·
What’s the most important thing to look for when picking out a CPU cooler?
RAM issues
in IT Support ·
Is the monitor not turning on at all, or does it just take a while to kick in?
Are you hearing any beeps coming from the PC case?
Are you hearing any beeps coming from the PC case?
BSOD
in IT Support ·
Sorted.
I honestly doubt it was actually a BIOS issue, mostly because I was running updates right when things started acting up. I was messing around with so many different things that day—installing my new GPU, getting everything set up after being offline for a couple of weeks—that I kind of lost track of what I had changed...
It was probably just a BIOS glitch or some messy GPU drivers.
Could be a lock...
I honestly doubt it was actually a BIOS issue, mostly because I was running updates right when things started acting up. I was messing around with so many different things that day—installing my new GPU, getting everything set up after being offline for a couple of weeks—that I kind of lost track of what I had changed...
It was probably just a BIOS glitch or some messy GPU drivers.
Could be a lock...
BSOD
in IT Support ·
HD 5770 1GB - $150
No issues so far... I tried swapping the RAM to a different slot, moved the GPU around, and even replaced the SATA cables inside the case...
If I hit a BSOD, I'll let you guys know. I watched a few tutorials on YouTube, and apparently, if a Blue Screen pops up, I should try booting into Safe Mode. If it still crashes there, it's definitely a hardware issue; if it stays stable, then it's likely just a software glitch, probably some buggy driver.
No issues so far... I tried swapping the RAM to a different slot, moved the GPU around, and even replaced the SATA cables inside the case...
If I hit a BSOD, I'll let you guys know. I watched a few tutorials on YouTube, and apparently, if a Blue Screen pops up, I should try booting into Safe Mode. If it still crashes there, it's definitely a hardware issue; if it stays stable, then it's likely just a software glitch, probably some buggy driver.
BSOD
in IT Support ·
Turns out that didn't fix it, since I just hit another BSOD.
On Wednesday 10/01/2014 at 4:38:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query : KMODE_EXCEPTION_NOT_HANDLED
On Wednesday 10/01/2014 at 5:11:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100114-17940-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800524F5E0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query : KMODE_EXCEPTION_NOT_HANDLED
On Wednesday 10/01/2014 at 4:38:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query : KMODE_EXCEPTION_NOT_HANDLED
On Wednesday 10/01/2014 at 5:11:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100114-17940-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800524F5E0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query : KMODE_EXCEPTION_NOT_HANDLED
BSOD
in IT Support ·
I picked up a used GPU a few days ago, but it didn't come with a driver CD. The seller said he didn't have it and just told me to grab them from the AMD site.
I don't think he was being shady, though, because I asked him for some screenshots from GPU-Z before he shipped it just to make sure everything looked solid.
So far, even without the drivers installed, everything seems to be running fine; no BSOD to report yet.
I could really use a suggestion on which specific drivers I should install, since I'm pretty sure the driver is where the trouble will start. I've already seen some stuff online about people running into similar headaches with those Catalyst drivers.
I don't think he was being shady, though, because I asked him for some screenshots from GPU-Z before he shipped it just to make sure everything looked solid.
So far, even without the drivers installed, everything seems to be running fine; no BSOD to report yet.
I could really use a suggestion on which specific drivers I should install, since I'm pretty sure the driver is where the trouble will start. I've already seen some stuff online about people running into similar headaches with those Catalyst drivers.
BSOD
in IT Support ·
I was thinking about it and decided to just reinstall Windows, since I have a hunch the issue lies with my GPU drivers.
Right now, I don't have any drivers installed for my HD 5770, and I'm not getting any BSOD. I'm not going to spend all day installing drivers just to see if the BSOD pops up again. If it stays away, then I know for sure it’s a driver issue. Just to recap, I only picked up this GPU a few days ago, and I haven't even been able to use the PC much because my motherboard doesn't have integrated graphics. As soon as the GPU arrived and I started updating the drivers, things went sideways. I've also seen online that GPU driver issues are pretty common...
It looks like the latest versions might not be fully compatible right now. I'll keep an eye on it through the end of the day to see if the BSOD returns; if it doesn't, then the Catalyst drivers are definitely the culprit.
I'm honestly not sure which version would be the most stable to install.
At this point, it's all just guesswork, but as time goes by without a BSOD, I'm feeling a bit more happy about it. 😁
I'll check back in later with more info.
Right now, I don't have any drivers installed for my HD 5770, and I'm not getting any BSOD. I'm not going to spend all day installing drivers just to see if the BSOD pops up again. If it stays away, then I know for sure it’s a driver issue. Just to recap, I only picked up this GPU a few days ago, and I haven't even been able to use the PC much because my motherboard doesn't have integrated graphics. As soon as the GPU arrived and I started updating the drivers, things went sideways. I've also seen online that GPU driver issues are pretty common...
It looks like the latest versions might not be fully compatible right now. I'll keep an eye on it through the end of the day to see if the BSOD returns; if it doesn't, then the Catalyst drivers are definitely the culprit.
I'm honestly not sure which version would be the most stable to install.
At this point, it's all just guesswork, but as time goes by without a BSOD, I'm feeling a bit more happy about it. 😁
I'll check back in later with more info.
BSOD
in IT Support ·
I've got the BIOS updated.
I ran a quick MemTest86+ to check my RAM, but everything came back clean—no errors at all.
I've never overclocked my CPU... I did read somewhere that it could actually be a processor issue, but I honestly don't think that's what's happening here.
Here’s what I ran into today...
Your computer hit a wall and crashed on Wednesday, October 1st, 2014, at 8:53:57 GMT.
I've got the crash dump file here: C:\Windows\Minidump\100114-23634-01.dmp
It looks like this issue was likely triggered by the ntoskrnl.exe module (nt+0x75BC0).
Looks like I ran into a 0x1E bugcheck. Here’s the info: (0xFFFFFFFFC0000096, 0xFFFFF80002EAF95C, 0x0, 0x0).
I ran into a KMODE_EXCEPTION_NOT_HANDLED error earlier. Has anyone else dealt with this one?
It looks like you're pointing toward C:\Windows\system32\ntoskrnl.exe.
Microsoft Windows operating system
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
It looks like a kernel-mode program threw an exception that the error handler just couldn't catch.
It looks like a classic software driver issue to me, so I wouldn't worry too much about your hardware being the culprit here.
It looks like the crash happened within the Windows kernel. It’s possible some other driver is causing the trouble, but I haven't been able to pin down exactly which one it is just yet.
Your computer hit a snag and crashed on Wednesday, October 1st, 2014, at 8:53:57 GMT.
I've got a crash dump file located at C:\Windows\memory.dmp.
It looks like this issue was likely triggered by this specific module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0).
Looks like you're running into a 0x1E bugcheck. It’s a bit of a headache, but we can figure this out.
Google query : KMODE_EXCEPTION_NOT_HANDLED
Basically, this means a kernel-mode program threw an exception that the error handler just wasn't able to catch.
It looks like a classic software driver issue to me, so I wouldn't worry too much about your hardware being the culprit here.
It looks like the crash happened right in the Windows kernel. It’s possible some other driver is causing the trouble, but I can't quite pin down which one just yet.
Your computer hit a snag and crashed on Wednesday, October 1st, 2014, at 8:21:22 GMT.
I've got the crash dump file right here: C:\Windows\Minidump\100114-18423-01.dmp
It looks like this was likely triggered by the usbport.sys module (USBPORT+0x160A4).
Looks like I ran into a 0xA bugcheck. Not exactly the start to my day that I was hoping for.
I ran into an IRQL_NOT_LESS_OR_EQUAL error. Any ideas what might be causing this?
It looks like you're pointing to C:\Windows\system32\drivers\usbport.sys.
Microsoft Windows
Microsoft Corporation
Just a quick heads-up regarding the USB 1.1 & 2.0 Port Driver.
Basically, this means a Microsoft Windows driver or some part of the kernel tried to touch paged memory while running at DISPATCH_LEVEL or higher. It's one of those classic errors.
It looks like a classic software driver glitch rather than anything actually wrong with your hardware.
It looks like the crash happened within a standard Microsoft module. There's a chance your system configuration might be a bit off, or perhaps another driver is causing some trouble behind the scenes that hasn't been identified yet.
Your computer hit a snag and crashed on Wednesday, October 1, 2014, at 8:17:46 GMT.
I've got the crash dump file here: C:\Windows\Minidump\100114-18049-01.dmp
It looks like this issue was likely triggered by the ntoskrnl.exe module (nt+0x75B90).
I ran into a Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0). Any ideas what might be causing this?
I ran into a KMODE_EXCEPTION_NOT_HANDLED error today. Any ideas?
It looks like the culprit is located at C:\Windows\system32\ntoskrnl.exe.
Microsoft Windows
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
Basically, this means some kernel-mode program threw an exception that the error handler just wasn't able to catch.
It looks like a classic software driver issue rather than anything going wrong with your actual hardware.
It looks like the crash happened right in the Windows kernel. It’s possible some other driver is causing the trouble, but I haven't been able to pin down exactly which one it is yet.
Every time I hit a crash, the error points toward a software issue rather than anything with the hardware. Honestly, I'm starting to think that might actually be the culprit.
I have a feeling my GPU might be the culprit. I picked up a used one on eBay a few days ago, and since my motherboard doesn't have integrated graphics, I was totally stuck without it. I only started seeing the Blue Screen of Death the day after I finally got it installed. I'm starting to suspect there's something wrong with the card itself.
I ran a quick MemTest86+ to check my RAM, but everything came back clean—no errors at all.
I've never overclocked my CPU... I did read somewhere that it could actually be a processor issue, but I honestly don't think that's what's happening here.
Here’s what I ran into today...
Your computer hit a wall and crashed on Wednesday, October 1st, 2014, at 8:53:57 GMT.
I've got the crash dump file here: C:\Windows\Minidump\100114-23634-01.dmp
It looks like this issue was likely triggered by the ntoskrnl.exe module (nt+0x75BC0).
Looks like I ran into a 0x1E bugcheck. Here’s the info: (0xFFFFFFFFC0000096, 0xFFFFF80002EAF95C, 0x0, 0x0).
I ran into a KMODE_EXCEPTION_NOT_HANDLED error earlier. Has anyone else dealt with this one?
It looks like you're pointing toward C:\Windows\system32\ntoskrnl.exe.
Microsoft Windows operating system
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
It looks like a kernel-mode program threw an exception that the error handler just couldn't catch.
It looks like a classic software driver issue to me, so I wouldn't worry too much about your hardware being the culprit here.
It looks like the crash happened within the Windows kernel. It’s possible some other driver is causing the trouble, but I haven't been able to pin down exactly which one it is just yet.
Your computer hit a snag and crashed on Wednesday, October 1st, 2014, at 8:53:57 GMT.
I've got a crash dump file located at C:\Windows\memory.dmp.
It looks like this issue was likely triggered by this specific module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0).
Looks like you're running into a 0x1E bugcheck. It’s a bit of a headache, but we can figure this out.
Google query : KMODE_EXCEPTION_NOT_HANDLED
Basically, this means a kernel-mode program threw an exception that the error handler just wasn't able to catch.
It looks like a classic software driver issue to me, so I wouldn't worry too much about your hardware being the culprit here.
It looks like the crash happened right in the Windows kernel. It’s possible some other driver is causing the trouble, but I can't quite pin down which one just yet.
Your computer hit a snag and crashed on Wednesday, October 1st, 2014, at 8:21:22 GMT.
I've got the crash dump file right here: C:\Windows\Minidump\100114-18423-01.dmp
It looks like this was likely triggered by the usbport.sys module (USBPORT+0x160A4).
Looks like I ran into a 0xA bugcheck. Not exactly the start to my day that I was hoping for.
I ran into an IRQL_NOT_LESS_OR_EQUAL error. Any ideas what might be causing this?
It looks like you're pointing to C:\Windows\system32\drivers\usbport.sys.
Microsoft Windows
Microsoft Corporation
Just a quick heads-up regarding the USB 1.1 & 2.0 Port Driver.
Basically, this means a Microsoft Windows driver or some part of the kernel tried to touch paged memory while running at DISPATCH_LEVEL or higher. It's one of those classic errors.
It looks like a classic software driver glitch rather than anything actually wrong with your hardware.
It looks like the crash happened within a standard Microsoft module. There's a chance your system configuration might be a bit off, or perhaps another driver is causing some trouble behind the scenes that hasn't been identified yet.
Your computer hit a snag and crashed on Wednesday, October 1, 2014, at 8:17:46 GMT.
I've got the crash dump file here: C:\Windows\Minidump\100114-18049-01.dmp
It looks like this issue was likely triggered by the ntoskrnl.exe module (nt+0x75B90).
I ran into a Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0). Any ideas what might be causing this?
I ran into a KMODE_EXCEPTION_NOT_HANDLED error today. Any ideas?
It looks like the culprit is located at C:\Windows\system32\ntoskrnl.exe.
Microsoft Windows
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
Basically, this means some kernel-mode program threw an exception that the error handler just wasn't able to catch.
It looks like a classic software driver issue rather than anything going wrong with your actual hardware.
It looks like the crash happened right in the Windows kernel. It’s possible some other driver is causing the trouble, but I haven't been able to pin down exactly which one it is yet.
Every time I hit a crash, the error points toward a software issue rather than anything with the hardware. Honestly, I'm starting to think that might actually be the culprit.
I have a feeling my GPU might be the culprit. I picked up a used one on eBay a few days ago, and since my motherboard doesn't have integrated graphics, I was totally stuck without it. I only started seeing the Blue Screen of Death the day after I finally got it installed. I'm starting to suspect there's something wrong with the card itself.
BSOD
in IT Support ·
Thanks for the quick reply!
I tried reinstalling my DNS settings thinking it might stop the Blue Screen of Death, but no luck there :S
I'm kind of at a loss... I can't say exactly when the BSOD first popped up, but I think it started after I was messing around in the BIOS with my RAM timings. I didn't touch the voltage or anything. I probably need some tools to check if the RAM itself is failing or something... just so you know, I'm running a single 4GB Patriot Viper3 1866MHz stick.
I tried reinstalling my DNS settings thinking it might stop the Blue Screen of Death, but no luck there :S
I'm kind of at a loss... I can't say exactly when the BSOD first popped up, but I think it started after I was messing around in the BIOS with my RAM timings. I didn't touch the voltage or anything. I probably need some tools to check if the RAM itself is failing or something... just so you know, I'm running a single 4GB Patriot Viper3 1866MHz stick.