Getting random blue screens with my new computer. Thought it was just a random occurance, but I'm getting them every few hours now.
Driver IRQL Not Less Than or Equal,
Kernal Mode Exception Not Handled,
System Thread Exception Not Handled, etc.
Show Content
I've gotten like 10 of them in the last 24 hours
Getting random blue screens with my new computer. Thought it was just a random occurance, but I'm getting them every few hours now.
Driver IRQL Not Less Than or Equal,
Kernal Mode Exception Not Handled,
System Thread Exception Not Handled, etc.
[spoiler][img]http://i.imgur.com/xC7T0jE.png[/img][/spoiler]
I've gotten like 10 of them in the last 24 hours
CamusBuy a new computer
if i followed this advice after every problem with my computer I would have about 12 computers.
[quote=Camus]Buy a new computer[/quote]
if i followed this advice after every problem with my computer I would have about 12 computers.
just got another one. All of the sudden the audio just starts looping in this super high pitched thing. Like when tf2 used to glitch with alt tabs, except 5 times louder and shorter bursts (if that makes any sense whatsoever which I doubt).
Show Content
I could just deal with it, since with w8 and an ssd it boots up almost instanty...
just got another one. All of the sudden the audio just starts looping in this super high pitched thing. Like when tf2 used to glitch with alt tabs, except 5 times louder and shorter bursts (if that makes any sense whatsoever which I doubt).
[spoiler]I could just deal with it, since with w8 and an ssd it boots up almost instanty...[/spoiler]
Set everything to stock clock/timing, try and see if it's based on stress, if so, try and see what component is failing (Do heavy RAM testing, then CPU, etc).
Set everything to stock clock/timing, try and see if it's based on stress, if so, try and see what component is failing (Do heavy RAM testing, then CPU, etc).
Couple things (just answer what you can):
Is your system automatically overclocking your processor at all? Many of these new Z87 boards automatically overclock your CPU to the highest turbo multiplier (3.9GHz for 4770Ks), though 99% of them work fine with that.
Have you installed the latest drivers for your chipset, USB 3.0 controller, etc. and not from the outdated driver CD?
Do your BSODs reference drivers e.g. nvlddmkm.sys and/or hexadecimal error codes e.g. 0x00000124?
Does this happen randomly or does doing a certain task provoke the computer to BSOD?
It might be useful to go into Control Panel > Administrative Tools > Event Viewer and retrieve the Event IDs from any critical system events.
Couple things (just answer what you can):
Is your system automatically overclocking your processor at all? Many of these new Z87 boards automatically overclock your CPU to the highest turbo multiplier (3.9GHz for 4770Ks), though 99% of them work fine with that.
Have you installed the latest drivers for your chipset, USB 3.0 controller, etc. and not from the outdated driver CD?
Do your BSODs reference drivers e.g. nvlddmkm.sys and/or hexadecimal error codes e.g. 0x00000124?
Does this happen randomly or does doing a certain task provoke the computer to BSOD?
It might be useful to go into Control Panel > Administrative Tools > Event Viewer and retrieve the Event IDs from any critical system events.
Jstn7477Couple things (just answer what you can):
Is your system automatically overclocking your processor at all? Many of these new Z87 boards automatically overclock your CPU to the highest turbo multiplier (3.9GHz for 4770Ks), though 99% of them work fine with that.
Have you installed the latest drivers for your chipset, USB 3.0 controller, etc. and not from the outdated driver CD?
Do your BSODs reference drivers e.g. nvlddmkm.sys and/or hexadecimal error codes e.g. 0x00000124?
Does this happen randomly or does doing a certain task provoke the computer to BSOD?
It might be useful to go into Control Panel > Administrative Tools > Event Viewer and retrieve the Event IDs from any critical system events.
I'll have to write down what it says exactly next time, but I'm pretty sure it was different file locations, like windows/sys/whatever
Didn't use any of the old cd drivers, but the bios might be out of date. I'll have to go look that up. I do have the cpu overclocked to 4.2, but that was just a recent thing. It was happening before that. I'll try stock and report back if it does it again and the info etc.
[quote=Jstn7477]Couple things (just answer what you can):
Is your system automatically overclocking your processor at all? Many of these new Z87 boards automatically overclock your CPU to the highest turbo multiplier (3.9GHz for 4770Ks), though 99% of them work fine with that.
Have you installed the latest drivers for your chipset, USB 3.0 controller, etc. and not from the outdated driver CD?
Do your BSODs reference drivers e.g. nvlddmkm.sys and/or hexadecimal error codes e.g. 0x00000124?
Does this happen randomly or does doing a certain task provoke the computer to BSOD?
It might be useful to go into Control Panel > Administrative Tools > Event Viewer and retrieve the Event IDs from any critical system events.[/quote]I'll have to write down what it says exactly next time, but I'm pretty sure it was different file locations, like windows/sys/whatever
Didn't use any of the old cd drivers, but the bios might be out of date. I'll have to go look that up. I do have the cpu overclocked to 4.2, but that was just a recent thing. It was happening before that. I'll try stock and report back if it does it again and the info etc.
As the owner of a Haswell system myself with a good month of tweaking the platform (owned since launch week), I'd advise you to return the processor cores and the the cache/ring component back to automatic settings. My sample requires 1.123v for both the cores and ring to operate at 4.3GHz, and improper voltage settings will almost always guarantee a 0x124 BSOD.
I'd definitely see about updating the UEFI BIOS if you can, as my board vendor (ASRock) pumped out about 5 updates within the last two months for various stability issues.
I also noticed that your RAM timings are pretty loose for 1600 MHz DDR3. Do you know what speed you purchased and its CAS latency? Sounds like it may need some manual adjustment, or for you to engage the XMP profile in your BIOS.
As the owner of a Haswell system myself with a good month of tweaking the platform (owned since launch week), I'd advise you to return the processor cores and the the cache/ring component back to automatic settings. My sample requires 1.123v for both the cores and ring to operate at 4.3GHz, and improper voltage settings will almost always guarantee a 0x124 BSOD.
I'd definitely see about updating the UEFI BIOS if you can, as my board vendor (ASRock) pumped out about 5 updates within the last two months for various stability issues.
I also noticed that your RAM timings are pretty loose for 1600 MHz DDR3. Do you know what speed you purchased and its CAS latency? Sounds like it may need some manual adjustment, or for you to engage the XMP profile in your BIOS.
For ram timings I just have it at stock, havent gotten around to overclocking it with all these stupid blue screens
For ram timings I just have it at stock, havent gotten around to overclocking it with all these stupid blue screens
Drop me the full error message you're getting. IRQL can be many things. GPU and LAN drivers are the 2 most common causes for the crash in my experience.
Drop me the full error message you're getting. IRQL can be many things. GPU and LAN drivers are the 2 most common causes for the crash in my experience.
If you have the space, make a whole new partition and install windows 8 on it. If 8 is anything like all past versions boot loader will let you choose between both. Being that its a window directory it can be either sys/drivers or windows missing files during install. Possibly both. But I like using the partition trick to test out OS issues. Without that exact bsod code it is too hard to tell.
If you have the space, make a whole new partition and install windows 8 on it. If 8 is anything like all past versions boot loader will let you choose between both. Being that its a window directory it can be either sys/drivers or windows missing files during install. Possibly both. But I like using the partition trick to test out OS issues. Without that exact bsod code it is too hard to tell.
and check if your power supply is haswell ready too. power delivery is very important as the lower power consumption of haswell processors make them more sensitive to fluctuations
and check if your power supply is haswell ready too. power delivery is very important as the lower power consumption of haswell processors make them more sensitive to fluctuations
http://www.overclock.net/t/1241077/beginner-bsod-crash-dump-analysis-and-debugging-guide
CamusBuy a new computer
I say ban
[quote=Camus]Buy a new computer[/quote]
I say ban