电脑经常蓝屏是什么原因啊,要疯了

Chimcham62-avatar

Chimcham62

这个照片不全,英语差,没读懂。

大概意思是重启,再重启,然后找人[s:pst:偷笑3]
zEthereal-avatar

zEthereal

IRQL_NOT_|LESS_OR_EQUAL
|
|
|
|
|题可能有很多原因,但看一
|下面又写了0000A,觉得这
|显了,也很确定,只要把机
|就好了,问题解决!
Chrispy-chicken-avatar

Chrispy-chicken

Reply to [pid=488446750,25285997,1]Reply[/pid] Post by [uid=42351226]O1ga[/uid] (2021-01-26 22:27)[s:ac:哭笑]老哥给你点个赞
dobby-avatar

dobby

[quote][pid=488446750,25285997,1]Reply[/pid] Post by [uid=42351226]O1ga[/uid] (2021-01-26 22:27):

IRQL_NOT_|LESS_OR_EQUAL
|
|
|
|
|题可能有很多原因,但看一
|下面又写了0000A,觉得这
|显了,也很确定,只要把机
|就好了,问题解决![/quote]还是老铁会玩[s:a2:不明觉厉]
O 口 O-avatar

O 口 O

[quote][pid=488446750,25285997,1]Reply[/pid] Post by [uid=42351226]O1ga[/uid] (2021-01-26 22:27):

IRQL_NOT_|LESS_OR_EQUAL
|
|
|
|
|题可能有很多原因,但看一
|下面又写了0000A,觉得这
|显了,也很确定,只要把机
|就好了,问题解决![/quote]啥意思啊没看懂谢谢
Hyperrrrs-avatar

Hyperrrrs

[quote][pid=488448804,25285997,1]Reply[/pid] Post by [uid=43042664]琥珀川珺[/uid] (2021-01-26 22:37):

啥意思啊没看懂谢谢[/quote]意思就是叫你拍照拍全
Logi-avatar

Logi

[quote][tid=25285997]Topic[/tid] Post by [uid=43042664]琥珀川珺[/uid] (2021-01-26 22:13):

[img]https://img.nga.178.com/attachments/mon_202101/26/9aQs4te-8c1qXbZ31T3cSqo-zk.jpg.medium.jpg[/img][/quote][url]http://www.zhuangjiba.com/help/7996.html[/url]
[url]https://jingyan.baidu.com/article/f96699bb7ace11c94f3c1b5a.html[/url]

STOP:0x0000000A
搜这个就是了

结论是新硬件的驱动不兼容引起的
要么换系统,要么更新驱动,要么换硬件
O 口 O-avatar

O 口 O

[quote][pid=488450324,25285997,1]Reply[/pid] Post by [uid=575003]lovingvurtne[/uid] (2021-01-26 22:45):

[url]http://www.zhuangjiba.com/help/7996.html[/url]
[url]https://jingyan.baidu.com/article/f96699bb7ace11c94f3c1b5a.html[/url]

STOP:0x0000000A
搜这个就是了

结论是新硬件的驱动不兼容引起的
要么换系统,要么更新驱动,要么换硬件[/quote]谢谢
我研究下
Anuqis変態-avatar

Anuqis変態

[url]https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa--irql-not-less-or-equal[/url]

官方文档其实写的很清楚,不过对于这种已经停止support的系统建议in-place upgrade到Windows 10。

This bug check is usually caused by kernel-mode device drivers that use improper addresses.

This bug check indicates that an attempt was made to access an invalid address while at a raised interrupt request level (IRQL). This is either a bad memory pointer or a pageability problem with the device driver code.

Following are some general guidelines that you can use to categorize the type of coding error that caused the bug check:

If parameter 1 is less than 0x1000, the issue is likely a NULL pointer dereference.

If !pool reports that parameter 1 is paged pool (or other types of pageable memory), then the IRQL is too high to access this data. Run at a lower IRQL, or allocate the data in the nonpaged pool.

If parameter 3 indicates that this was an attempt to execute pageable code, then the IRQL is too high to call this function. Run at a lower IRQL, or do not mark the code as pageable.

Otherwise, this may be a bad pointer, possibly caused by use-after-free or bit-flipping. Investigate the validity of parameter 1 with !pte, !address, and ln (list nearest symbols).