此主題已被鎖定
Stoneboi 2017 年 4 月 8 日 上午 10:29
IRQL_NOT_LESS_OR_EQUAL
HELP

This happens randomly and idk what to do
< >
目前顯示第 1-14 則留言,共 14
Omega 2017 年 4 月 8 日 上午 11:10 
Reinstalling Windows will fix it even if its a driver issue. Which it probably is.

Download the Media creation tool from the Microsoft website. It can found here[www.microsoft.com]. Then use the media creation tool to download and mount the Windows 10 installation files on a flash drive. Then once the tool is done boot form the flash drive on the PC you wish to install it on.
最後修改者:rotNdude; 2017 年 4 月 8 日 下午 1:54
Stoneboi 2017 年 4 月 8 日 上午 11:59 
引用自 Omega
Download the Media creation tool from the Microsoft website. It can found here[www.microsoft.com]. Then use the media creation tool to download and mount the Windows 10 installation files on a flash drive. Then once the tool is done boot form the flash drive on the PC you wish to install it on.
thats what I done last time and aparently all it did was make things worse
upcoast 2017 年 4 月 8 日 下午 1:07 
Test your ram and even go as far as running one stick at a time to see if your bsod clears up.

If you've overclocked anything put it back to default speeds.

If you've done a fresh win 10 install I'd be looking at hardware, tbh not less or equal to is generally bad OC or Ram.

Ps, put your full specs in your profile so we know what you've got right down to the psu make / model.
最後修改者:upcoast; 2017 年 4 月 8 日 下午 1:11
chiefputsilao 2017 年 4 月 8 日 下午 3:53 
memory problem?

i encoountered this problem more than a decade ago when mixing memory modules of different brands. same speed, same latency, same voltage, different brands, would manifest only in certain games like the sims.

maybe do what upcoast suggested.
[☥] - CJ - 2017 年 4 月 8 日 下午 5:38 
could be a driver, more likely a RAM issue

Download WhoCrashed and it'll give more details about the crash dump and what caused it
最後修改者:[☥] - CJ -; 2017 年 4 月 8 日 下午 5:38
Big Boom Boom 2017 年 4 月 8 日 下午 8:42 
Memory problem more likely. Had this issue before when I OC my CPU and the auto XMP is not enough. Manually tweak VCCIO and VSCCA made it stable for me.
最後修改者:Big Boom Boom; 2017 年 4 月 8 日 下午 9:25
Bad 💀 Motha 2017 年 4 月 8 日 下午 9:16 
Faulty RAM, test the RAM and DIMM slots one at time

Also check the BIOS to ensure RAM is setup correctly; enable XMP, otherwise your RAM is setup wrong. Which can lead to such errors because the RAM is not operating at the correct timings.
最後修改者:Bad 💀 Motha; 2017 年 4 月 8 日 下午 9:17
Dom 6 月 27 日 下午 2:54 
Windows Security > Device security > Core isolation details -> Memory Integrity on
Carlsberg 6 月 27 日 下午 3:40 
That's an interrupt error, most likely cause is a driver conflict, often its a sound driver.

If you have no clue start at the beginning. Update Chipset, reboot and then sound, network, gpu and any others as required. Do Not rely on windows for drivers, go to manufacturers sites and get the correct ones.
最後修改者:Carlsberg; 6 月 27 日 下午 3:41
Carlsberg 6 月 27 日 下午 3:44 
引用自 Omega
Reinstalling Windows will fix it even if its a driver issue. Which it probably is.

Really, that's your first suggestion. Hopefully no-one listens to you.
_I_ 6 月 27 日 下午 9:03 
引用自 Carlsberg
That's an interrupt error, most likely cause is a driver conflict, often its a sound driver.

If you have no clue start at the beginning. Update Chipset, reboot and then sound, network, gpu and any others as required. Do Not rely on windows for drivers, go to manufacturers sites and get the correct ones.
interrupts are controlled by drivers, but even the generic drivers never throw that error on their own

its almost always psu, ram or unstable overclock
Bad 💀 Motha 6 月 27 日 下午 9:39 
It's usually due to driver issue (like a random fault) or unstable memory settings (such as timings which could easily trip something in the OS to crash)... or faulty PSU.

It can be faulty motherboard and or GPU but tbat is much more rare
Carlsberg 6 月 28 日 上午 4:27 
引用自 _I_
its almost always psu, ram or unstable overclock


引用自 Bad 💀 Motha
It's usually due to driver issue (like a random fault) or unstable memory settings (such as timings which could easily trip something in the OS to crash)... or faulty PSU.

It can be faulty motherboard and or GPU but tbat is much more rare
I left the IT field around the time XP was released so my knowledge is a bit dated but surely we would treat drivers and possible OS corruption first to rule them out before we start throwing hardware away.

Edit; Re-reading the post, the OP states that the last time this happened they re-installed windows to fix it. Were correct drivers installed ?
最後修改者:Carlsberg; 6 月 28 日 上午 4:34
Mike 6 月 28 日 上午 6:34 
This thread was quite old before the recent post, so we're locking it to prevent confusion.
< >
目前顯示第 1-14 則留言,共 14
每頁顯示: 1530 50