BSOD before and after upgrading to Windows 10 - Windows 10 x64

SweetLola · Aug 21, 2015

Hello,
I had alot of BSOD when I had windows 7 but after upgrading to Windows 10 it still happens.
I have HP Probook 4540s laptop
-Windows 10 x64 as current OS.
-Windows 7 as original installed OS (pre-installed).
-Intel Core i3 3110M @ 2.40GHz

Help me please.

View attachment SysnativeFileCollectionApp.zip View attachment PERFMON Output.zip

x BlueRobot · Aug 22, 2015

Unfortunately, there doesn't appear to be any dump files, have used any file cleaning tools recently?

I would also suggest that you check your dump file settings and paging settings - https://www.sysnative.com/forums/bs...information/9599-bsods-but-no-dump-files.html

SweetLola · Aug 22, 2015

View attachment SysnativeFileCollectionApp.zip

Jared · Aug 22, 2015

While performing a thread auto boost, the IRQL was still at 2 meaning it wouldn't execute because an interrupt has priority.
However, this is an illegal function, most likely because the thread scheduler might never execute and the system would hang.

Code:

3: kd> !thread ffffe001fe3db080
GetPointerFromAddress: unable to read from fffff800064411c0
THREAD ffffe001fe3db080  Cid 06d4.155c  Teb: 000000007e876000 Win32Thread: 0000000000000000 RUNNING on processor 3
Not impersonating
GetUlongFromAddress: unable to read from fffff8000638ff38
Owning Process            ffffe00202e58780       Image:         plugincontaine
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      4363955      
Context Switch Count      811546         IdealProcessor: 0             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000010be0fa
Stack Init ffffd0017b124c90 Current ffffd0017b124870
Base ffffd0017b125000 Limit ffffd0017b11f000 Call 0
Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd001`778e20b8 fffff800`062ef818 : 00000000`00000192 ffffe001`fe3db080 ffffe001`fda19508 00000000`00000002 : nt!KeBugCheckEx
ffffd001`778e20c0 fffff800`0652a051 : ffffe002`00000200 00000000`00001000 ffffd001`778e2220 fffff800`00000004 : nt!ExAllocatePoolWithTag+0xeb8
ffffd001`778e21a0 fffff800`0652982f : ffffd001`778e23d8 ffffe001`ff1c0ec0 00000000`00010031 ffffd001`778e23d8 : nt!CmOpenDeviceRegKeyWorker+0x85
ffffd001`778e2260 fffff800`0652b37c : 00000000`00000000 00000000`00000000 ffffe001`ff1c0ec0 00000000`00000001 : nt!CmOpenDeviceRegKey+0xdb
ffffd001`778e2360 fffff800`06529969 : 00000000`0000c000 fffff800`e0ca3dd8 00000000`00010031 ffffd001`778e2610 : nt!CmGetDeviceRegPropWorker+0xf4
ffffd001`778e24c0 fffff800`065a4a4d : ffffe002`003cbda0 00000000`00000005 00000000`00000000 ffffe002`04f9a578 : nt!CmGetDeviceRegProp+0xf9
ffffd001`778e25d0 fffff800`065a4930 : fffff800`00000004 00000000`00000000 ffffd001`778e26e8 ffffd001`778e28e0 : nt!CmGetDeviceSoftwareKey+0x6d
ffffd001`778e26e0 fffff800`0652a4d2 : 00000000`0000003f 00000000`00000012 00000000`00000012 ffffccbe`a45d44dc : nt!CmGetDeviceSoftwareKeyPath+0x4c
ffffd001`778e27c0 fffff800`0652a08c : ffffe001`ff1c0ec0 ffffd001`778e2890 ffffc000`668f4da0 ffffd001`00000000 : nt!CmGetDeviceRegKeyPath+0x142
ffffd001`778e2810 fffff800`0652982f : ffffe001`fe0ed2c0 ffffe001`ff1c0ec0 00000000`00000000 ffffe001`fe0ed2c0 : nt!CmOpenDeviceRegKeyWorker+0xc0
ffffd001`778e28d0 fffff800`065a076f : 00000000`00000002 00000000`00000012 00000000`c2000000 ffffe001`fe0ed2c0 : nt!CmOpenDeviceRegKey+0xdb
ffffd001`778e29d0 fffff800`df32a388 : 00000000`00000000 ffffd001`778e2a70 ffffe001`fe0ed2a0 ffffe002`04abd1a0 : nt!IoOpenDeviceRegistryKey+0xbb
ffffd001`778e2a20 fffff800`e125b883 : 00000000`00000000 ffffd001`778e2b40 00000000`00000000 00000000`00000001 : ndis!NdisOpenConfigurationEx+0x128
ffffd001`778e2aa0 00000000`00000000 : ffffd001`778e2b40 00000000`00000000 00000000`00000001 ffffe001`001801a9 : netr28x+0x4b883

3: kd> lmvm netr28x
Browse full module list
start             end                 module name
fffff800`e1210000 fffff800`e1475000   netr28x  T (no symbols)           
    Loaded symbol image file: netr28x.sys
    Image path: \SystemRoot\system32\DRIVERS\netr28x.sys
    Image name: netr28x.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Dec 31 02:44:09 2014 (54A362F9)
    CheckSum:         0025F414
    ImageSize:        00265000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The netr28x network driver network driver is performing registry configurations when it tries to allocate memory and the system crashes. For whatever reason, the system had to be at a raised IRQL for this function, but doing so would delay the execution of a high priority thread.
I suggest upgrading the driver, which belongs to the Ralink network adapter.

Search

Search

BSOD before and after upgrading to Windows 10 - Windows 10 x64

SweetLola

New member

x BlueRobot

Administrator

SweetLola

New member

Jared

Sysnative Staff, BSOD Kernel Dump Expert