win 8.1 start with error DRIVER_IRQL_NOT_LESS_OR_EQUAL

Laddy

Member
Joined
Feb 20, 2014
Posts
6
Hello

sorry for my English , i am french, and i speak a little bit.

Since winupdate (12.02.2014), when win 8.1 starts, I have a blue screen with the following error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Windows restart and I can go to my session, but when i shutdown my computer, it begins again BSOD

I do not understand where it comes from, no program has been installed on this pc. I have no viruses.

Code:
==================================================
Dump File         : 022014-10875-01.dmp
Crash Time        : 20.02.2014 15:48:59
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`00000000
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000008
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14dca0
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+14dca0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\022014-10875-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 280 712
Dump File Time    : 20.02.2014 15:49:51
==================================================

I made sfc /scannow , here is the result:
is this related?


Code:
Lignes avec Repairing, Repaired, ou "cannot" :
============================================
LIGNES AVEC REPAIRING :
=====================
2014-02-20 17:16:01, Info                  CSI    00000865 [SR] Repairing 1 components
============================================
LIGNES AVEC REPAIRED :
====================
============================================
LIGNES AVEC CANNOT :
==================
2014-02-20 17:13:31, Info                  CSI    000004fb [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-20 17:13:32, Info                  CSI    000004fd [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-20 17:16:02, Info                  CSI    00000868 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-20 17:16:02, Info                  CSI    0000086a [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

Can you help ? :huh:
Please

Thanks a lot for your replies
Laddy
 
Hello



I followed the instructions but B tool does not work very well on my pc
I have attached the reports.

RAM is new.
SSD (OS) is also new

I hope you can help me

·
OS - Windows 8.1
· x64
· What was original installed OS on system?
· full retail version , i buy DVD in a reseller
· Age of system (hardware) : 2010 -Upgrade my computer with SSD (oct.2013), Memory (oct.2013)
· Age of OS installation : OCTOBER 2013 : NO problem before Windows update 12 febrary 2014.

· CPU : intel core i7
· Video Card : AMD ATI RAEDEON HD 6700 (2012)
· MotherBoard : asus rampage II exterme
· Power Supply : coolmaster silent pro 1000 watt

· System Manufacturer : assembly computer
Desktop tower


Thanks

Laddy
 

Attachments

Hi,

All of the attached DMP files are of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bug check.

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

Code:
Unable to load image \SystemRoot\system32\DRIVERS\[I][B]athwnx.sys[/B][/I], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [I][B]athwnx.sys[/B][/I]
*** ERROR: Module load completed but symbols could not be loaded for [I][B]athwnx.sys[/B][/I]
Probably caused by : [B][I]athwnx.sys[/I][/B] ( [I][B]athwnx+2e3f8 [/B][/I])

^^ athwnx.sys = Qualcomm Atheros Extensible Wireless LAN device driver.

-----------------

1. Remove and replace Norton with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's likely causing conflicts:

Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

2. Ensure all of your network drivers are up to date - ROG - RAMPAGE II EXTREME

Regards,

Patrick
 
Hello Patrick
Thank you very much for your help.

I followed your instructions and
I updated the wireless driver, the last date is 11/12/2013. I used to find the driver wlan : maconfig.com website
I reinstall Norton.
There is no LAN driver update on the asus website

Since Windows 8.1 starts quickly without error message.




Thanks a lot for your replies and help
Laddy
 
Thanks for the update, so if I understand your post correct, you haven't had any crashes?

Regards,

Patrick
 
Great, I was just making sure I didn't misunderstand. Keep me updated for 1-2 more days, and then we'll consider it solved if no more crashes occur.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top