Tech Support banner

Status
Not open for further replies.
1 - 14 of 14 Posts

·
Registered
Joined
·
8 Posts
Discussion Starter #1
I have a problem with blue screen, to begin I will clarify what I have already tried, it is not my RAM, and the check with windows, I also made the memtest of 3 hours, and already disconnect them one by one, and have no problems, because probe the hard drive, and it has no problems, I already did the chksdk, also look for errors or bad sectors, and I take it out and try it on another pc, and it's ok, and re-check the minidump, in whocrashed, throw me this

On Fri 07-27-2018 05:42:14 your computer crashed or a problem is reported
crash dump file: C: \ Windows \ Minidump \ 072718-31262-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7FD00)
Bugcheck code: 0xA (0xFFFFF8A004AA0478, 0x2, 0x1, 0xFFFFF80003D028AA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C: \ Windows \ system32 \ ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by
Another driver that can not be identified at this time.

On Fri 07-27-2018 18:21:28 your computer crashed or a problem is reported
crash dump file: C: \ Windows \ MEMORY.DMP
This was probably caused by the following module: netr28x.sys (netr28x + 0x4BA8D)
Bugcheck code: 0xA (0xFFFFF8A004AEB478, 0x2, 0x1, 0xFFFFF80003D438AA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C: \ Windows \ system32 \ drivers \ netr28x.sys
product: MediaTek 802.11n Wireless Adapters
company: MediaTek Inc.
description: MediaTek 802.11 Wireless Adapter Driver
Bug check description: This indicates that Microsoft Windows or kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested that you look for an update for the following driver: netr28x.sys (MediaTek 802.11 Wireless Adapter Driver, MediaTek Inc.).
Google query: netr28x.sys MediaTek Inc. IRQL_NOT_LESS_OR_EQUAL





in bluescreenview strip that this is the problem

ntoskrnl.exe + 7fd00

I'm almost sure it's not hardware, but I do not even know what to think I'm fed up, I saw an interesting post where they helped someone with an error similar to mine, this to be exact.

https://www.techsupportforum.com/forums/f299/solved-bsod-irql_not_less_or_equal-ntoskrnl-exe-865002.html

was a IRQL_NOT_LESS_OR_EQUAL stop error like mine, i hope that some of u can help me, it took me a lot of time to replace this pc, im scared about lose it, please help me. thanks for any answer ill appreciated.
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts

·
Registered
Joined
·
8 Posts
Discussion Starter #3
I did it, im using the lastest drivers, and i try the old drivers too, i have the same error with any drivers of my wifi card, with ntoskrnl.exe maybe the problem its kernel files, because this windows its a version of all windows in one, so for upgrade to ultimate sp1 i did it manual, with a manual entire update of sp1, maybe that is the probem, ill download a windows 7 ultimate with the sp1 included, for see if that is the problem.
 

·
Super Moderator, Editor, Articles Team
Joined
·
12,118 Posts
Hi, :wave: and welcome to TSF.

ИЄЯФ-ДИБЄLФ;7695018 said:
this windows its a version of all windows in one
Where did you download that from? URL please.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #5
no, i mean the iso, is a iso with all versions of windows 7, u know some isos have multiple windows, like the xp, some isos have all xp versions sp1 sp1 or sp3, u decide which version install.
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts
ИЄЯФ-ДИБЄLФ;7695018 said:
I did it, im using the lastest drivers, and i try the old drivers too, i have the same error with any drivers of my wifi card, with ntoskrnl.exe maybe the problem its kernel files, because this windows its a version of all windows in one, so for upgrade to ultimate sp1 i did it manual, with a manual entire update of sp1, maybe that is the probem, ill download a windows 7 ultimate with the sp1 included, for see if that is the problem.
ntoskrnl.exe is absolutely NOT the actual cause of your BSODs. It is the Windows kernel and executive.

Please run - https://www.techsupportforum.com/forums/f299/blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-and-vista-452654.html

Upload the Sysnative zip file and attach it to your next post.

I need the files it contains.

Regards. . .

jcgriff2

`
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts
ИЄЯФ-ДИБЄLФ;7695044 said:
no, i mean the iso, is a iso with all versions of windows 7, u know some isos have multiple windows, like the xp, some isos have all xp versions sp1 sp1 or sp3, u decide which version install.
Each version has its own kernel.

Again, ntoskrnl.exe IS NOT the problem here.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #8
I cannot understand that protocole man its too complicated
i dont see some zip file in my documents, only see SysnativeFileCollectionApp normal folder.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #9
I need help, no one know what this is, i try any solutions from any pages, and nothing works, i format, and reinstall my windows, and the problem appear since i start.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #11
Some analisys here




Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0340e000 PsLoadedModuleList = 0xfffff800`03653e90
Debug session time: Mon Aug 6 02:55:59.025 2018 (UTC - 4:00)
System Uptime: 0 days 0:13:02.257
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INVALID_PROCESS_ATTACH_ATTEMPT (5)
Arguments:
Arg1: fffffa80032166f0
Arg2: fffffa80066fd060
Arg3: 0000000000000000
Arg4: 0000000000000001

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x5

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 2

LOCK_ADDRESS: fffff8000368a440 -- (!locks fffff8000368a440)

Resource @ nt!PiEngineLock (0xfffff8000368a440) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff8000368a440
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff800034f3ffa to fffff8000348e640

STACK_TEXT:
fffff800`00ba1c78 fffff800`034f3ffa : 00000000`00000005 fffffa80`032166f0 fffffa80`066fd060 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba1c80 fffff800`0378577d : fffff8a0`09efbb90 00000000`00000000 fffff800`00ba1cb0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x265fb
fffff800`00ba1d00 fffff800`03785471 : 00000000`00000000 fffffa80`00000000 fffff8a0`00001780 00000000`00000000 : nt!ObpDecrementHandleCount+0x17d
fffff800`00ba1d80 fffff800`03785a34 : 00000000`00000b50 fffffa80`066fd060 fffff8a0`00001780 00000000`00000b50 : nt!ObpCloseHandleTableEntry+0xb1
fffff800`00ba1e10 fffff800`0348d8d3 : fffffa80`069e2660 fffff800`00ba1ee0 fffff800`0378eed0 fffff800`0375d82c : nt!ObpCloseHandle+0x94
fffff800`00ba1e60 fffff800`03489e70 : fffff800`036ff34b fffffa80`03bd9a10 fffff800`0378eed0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff800`00ba1ff8 fffff800`036ff34b : fffffa80`03bd9a10 fffff800`0378eed0 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff800`00ba2000 fffff800`036ff4ec : fffffa80`03bd9a10 00000000`00000001 fffffa80`03bd3740 00000000`00000000 : nt!PiGetDeviceRegistryProperty+0xab
fffff800`00ba2160 fffff800`036ff184 : fffffa80`03bd9a10 fffffa80`03bd9a10 00000000`00000000 00000000`00000000 : nt!IoGetDeviceProperty+0xbc
fffff800`00ba2240 fffff800`036ff265 : 00000000`ffff0000 fffffa80`03392bd0 fffff880`01512110 fffffa80`047a4870 : nt!IopOpenOrCreateDeviceRegistryKey+0x14c
fffff800`00ba2400 fffff880`01558f02 : fffffa80`00000000 fffff800`00ba2590 fffffa80`053c8b58 00000000`000007ff : nt!IoOpenDeviceRegistryKey+0x11
fffff800`00ba2440 fffff880`014c1cd4 : fffff800`00ba2590 fffff800`00ba2568 fffffa80`046731a0 fffff880`0156d21d : ndis!NdisOpenConfiguration+0xb2
fffff800`00ba2480 fffff880`048e0a4f : fffffa80`00000000 fffff800`00ba2590 fffff880`04af0e68 00000000`00000000 : ndis!NdisOpenConfigurationEx+0xa4
fffff800`00ba24f0 fffffa80`00000000 : fffff800`00ba2590 fffff880`04af0e68 00000000`00000000 00000000`001801a9 : netr28x+0x4ba4f
fffff800`00ba24f8 fffff800`00ba2590 : fffff880`04af0e68 00000000`00000000 00000000`001801a9 fffffa80`046731a0 : 0xfffffa80`00000000
fffff800`00ba2500 fffff880`04af0e68 : 00000000`00000000 00000000`001801a9 fffffa80`046731a0 fffffa80`00000000 : 0xfffff800`00ba2590
fffff800`00ba2508 00000000`00000000 : 00000000`001801a9 fffffa80`046731a0 fffffa80`00000000 fffff880`048ecfd2 : netr28x+0x25be68


STACK_COMMAND: kb

FOLLOWUP_IP:
netr28x+4ba4f
fffff880`048e0a4f ?? ???

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: netr28x+4ba4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: netr28x

IMAGE_NAME: netr28x.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55ca9ffd

FAILURE_BUCKET_ID: X64_0x5_netr28x+4ba4f

BUCKET_ID: X64_0x5_netr28x+4ba4f

Followup: MachineOwner
---------
 

·
Registered
Joined
·
8 Posts
Discussion Starter #12
seems that its the wifi driver but i install the last version, and the problem persist
, and i let the old versions and the same, i dont know what to do.
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts
ИЄЯФ-ДИБЄLФ;7696838 said:
I cannot understand that protocole man its too complicated
i dont see some zip file in my documents, only see SysnativeFileCollectionApp normal folder.
If you don't see the Sysnative zip file, create it yourself by Zipping the entire SysnativeFileCollectionApp folder.

You'll end up with a zip file named SysnativeFileCollectionApp.zip

Upload and attach it to your next post.

Regards. . .

jcgriff2

`
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts
ИЄЯФ-ДИБЄLФ;7696846 said:
Some analisys here


Code:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. ([url]https://www.osr.com[/url])
Online Crash Dump Analysis Service
See [url=https://www.osronline.com]OSR Online - The Home Page for Windows Driver Developers[/url] for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0340e000 PsLoadedModuleList = 0xfffff800`03653e90
Debug session time: Mon Aug  6 02:55:59.025 2018 (UTC - 4:00)
System Uptime: 0 days 0:13:02.257
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INVALID_PROCESS_ATTACH_ATTEMPT (5)
Arguments:
Arg1: fffffa80032166f0
Arg2: fffffa80066fd060
Arg3: 0000000000000000
Arg4: 0000000000000001

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x5

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff8000368a440 -- (!locks fffff8000368a440)

Resource @ nt!PiEngineLock (0xfffff8000368a440)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff8000368a440
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800034f3ffa to fffff8000348e640

STACK_TEXT:  
fffff800`00ba1c78 fffff800`034f3ffa : 00000000`00000005 fffffa80`032166f0 fffffa80`066fd060 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba1c80 fffff800`0378577d : fffff8a0`09efbb90 00000000`00000000 fffff800`00ba1cb0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x265fb
fffff800`00ba1d00 fffff800`03785471 : 00000000`00000000 fffffa80`00000000 fffff8a0`00001780 00000000`00000000 : nt!ObpDecrementHandleCount+0x17d
fffff800`00ba1d80 fffff800`03785a34 : 00000000`00000b50 fffffa80`066fd060 fffff8a0`00001780 00000000`00000b50 : nt!ObpCloseHandleTableEntry+0xb1
fffff800`00ba1e10 fffff800`0348d8d3 : fffffa80`069e2660 fffff800`00ba1ee0 fffff800`0378eed0 fffff800`0375d82c : nt!ObpCloseHandle+0x94
fffff800`00ba1e60 fffff800`03489e70 : fffff800`036ff34b fffffa80`03bd9a10 fffff800`0378eed0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff800`00ba1ff8 fffff800`036ff34b : fffffa80`03bd9a10 fffff800`0378eed0 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff800`00ba2000 fffff800`036ff4ec : fffffa80`03bd9a10 00000000`00000001 fffffa80`03bd3740 00000000`00000000 : nt!PiGetDeviceRegistryProperty+0xab
fffff800`00ba2160 fffff800`036ff184 : fffffa80`03bd9a10 fffffa80`03bd9a10 00000000`00000000 00000000`00000000 : nt!IoGetDeviceProperty+0xbc
fffff800`00ba2240 fffff800`036ff265 : 00000000`ffff0000 fffffa80`03392bd0 fffff880`01512110 fffffa80`047a4870 : nt!IopOpenOrCreateDeviceRegistryKey+0x14c
fffff800`00ba2400 fffff880`01558f02 : fffffa80`00000000 fffff800`00ba2590 fffffa80`053c8b58 00000000`000007ff : nt!IoOpenDeviceRegistryKey+0x11
fffff800`00ba2440 fffff880`014c1cd4 : fffff800`00ba2590 fffff800`00ba2568 fffffa80`046731a0 fffff880`0156d21d : ndis!NdisOpenConfiguration+0xb2
fffff800`00ba2480 fffff880`048e0a4f : fffffa80`00000000 fffff800`00ba2590 fffff880`04af0e68 00000000`00000000 : ndis!NdisOpenConfigurationEx+0xa4
fffff800`00ba24f0 fffffa80`00000000 : fffff800`00ba2590 fffff880`04af0e68 00000000`00000000 00000000`001801a9 : netr28x+0x4ba4f
fffff800`00ba24f8 fffff800`00ba2590 : fffff880`04af0e68 00000000`00000000 00000000`001801a9 fffffa80`046731a0 : 0xfffffa80`00000000
fffff800`00ba2500 fffff880`04af0e68 : 00000000`00000000 00000000`001801a9 fffffa80`046731a0 fffffa80`00000000 : 0xfffff800`00ba2590
fffff800`00ba2508 00000000`00000000 : 00000000`001801a9 fffffa80`046731a0 fffffa80`00000000 fffff880`048ecfd2 : netr28x+0x25be68


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netr28x+4ba4f
fffff880`048e0a4f ??              ???

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  netr28x+4ba4f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netr28x

IMAGE_NAME:  netr28x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55ca9ffd

FAILURE_BUCKET_ID:  X64_0x5_netr28x+4ba4f

BUCKET_ID:  X64_0x5_netr28x+4ba4f

Followup: MachineOwner
---------
Code:
[font=lucida console]IMAGE_NAME:  netr28x.sys
[/font]
You are correct - that is your USB wifi driver.

If there are no further driver updates available, the device needs to be replaced with something that is compatible with your system + Windows OS.

i.e., you need a new wifi device.

Regards. . .

jcgriff2

`
 
1 - 14 of 14 Posts
Status
Not open for further replies.
Top