[SOLVED] New PC Bluescreen

Lurizan

Lurizan

Active member
Joined
Jan 10, 2022
Posts
43
  • A brief description of your problem (but you can also include the steps you tried)-Updated windows
  • System Manufacturer?-HP
  • Laptop or Desktop?-Desktop
  • Exact model number (if laptop, check label on bottom)- HP PRODESK 400G7 MT I5 31J14PA
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista)-windows 10
  • x86 (32bit) or x64 (64bit)?-64bit
  • (Only for Vista, Windows 7) Service pack?
  • What was original installed OS on system?-windwos 10
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?-oem
  • Age of system? (hardware)2-3 weeks
  • Age of OS installation?-3 weeks
  • Have you re-installed the OS?-no
  • CPU-Intel Core i5-10500
  • RAM (brand, EXACT model, what slots are you using?)-DIMM1 8GB SAMSUNG M378A1K43EB2-CWE
  • Video Card-Intel UHD Graphics 630 (Comet Lake-S GT2) [G1] [Hewlett-Packard]
  • MotherBoard - (if NOT a laptop)-HP 8717
  • Power Supply - brand & wattage (if laptop, skip this one)-180W HK280-85PP S1
  • Is driver verifier enabled or disabled?-DISABLED
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)-microsoft defender
  • Are you using proxy, vpn, ipfilters or similar software?-no
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)-no
  • Are you currently under/overclocking? Are there overclocking software installed on your system?-no


link http://speccy.piriform.com/results/nP5UShQ6JIPvNauRhYClR4n
 

Attachments

Of the five dumps in your upload, four have a length of zero bytes and are thus unusable. The one that is a valid dump is a DPC_WATCHDOG_VIOLATION, which means that the back-end of a device interrupt ran for too long. In the call stack we see a third-party driver being called; rtwlanu.sys. This is a Realtek wireless LAN driver, and also from the call stack it would appear to be a USB attached wireless device. I suspect that this is your TOTOLink Wireless USB Adapter?
Rich (BB code): 
0: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff802`3c6a7e18 fffff802`36043690     nt!KeBugCheckEx
01 fffff802`3c6a7e20 fffff802`35e813c3     nt!KeAccumulateTicks+0x1bfa70
02 fffff802`3c6a7e80 fffff802`35e80eaa     nt!KeClockInterruptNotify+0x453
03 fffff802`3c6a7f30 fffff802`35f3e965     nt!HalpTimerClockIpiRoutine+0x1a
04 fffff802`3c6a7f60 fffff802`35ffdbaa     nt!KiCallInterruptServiceRoutine+0xa5
05 fffff802`3c6a7fb0 fffff802`35ffe377     nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
06 fffff802`3c697930 fffff802`35f405bc     nt!KiInterruptDispatchNoLockNoEtw+0x37
07 fffff802`3c697ac0 fffff802`35e1e678     nt!KxWaitForSpinLockAndAcquire+0x2c
08 fffff802`3c697af0 fffff802`56718558     nt!KeAcquireSpinLockRaiseToDpc+0x88
09 fffff802`3c697b20 fffff802`5644446e     rtwlanu!PlatformAcquireSpinLock+0x88
0a fffff802`3c697b50 fffff802`5640d7b3     rtwlanu!RmMonitorSignalStrength+0x4a
0b fffff802`3c697c10 fffff802`5640d56b     rtwlanu!ProcessReceivedPacketForEachPortSpecific+0x233
0c fffff802`3c697f10 fffff802`565b4cae     rtwlanu!ProcessReceivedPacket+0xd7
0d fffff802`3c697f50 fffff802`565b51a5     rtwlanu!ProcessSegregatedPackets_8821C+0x132
0e fffff802`3c697f90 fffff802`565b4b4d     rtwlanu!SegregateDmaAggPackets_8821C+0x189
0f fffff802`3c698000 fffff802`565b466f     rtwlanu!ParsingRxAggregation_8821C+0x75
10 fffff802`3c698040 fffff802`56366eac     rtwlanu!HalUsbInMpduComplete8821CUsb+0xcb
11 fffff802`3c698090 fffff802`3ada9249     rtwlanu!WdfUsb_InComplete+0x15c
12 fffff802`3c698120 fffff802`3adac854     Wdf01000!FxRequestBase::CompleteSubmitted+0xe9
13 (Inline Function) --------`--------     Wdf01000!FxIoTarget::CompleteRequest+0x8
14 (Inline Function) --------`--------     Wdf01000!FxIoTarget::RequestCompletionRoutine+0xab
15 fffff802`3c6981b0 fffff802`35f25726     Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xe4
16 fffff802`3c698220 fffff802`35e92735     nt!IopUnloadSafeCompletion+0x56
17 fffff802`3c698250 fffff802`35e92577     nt!IopfCompleteRequest+0x1a5
18 fffff802`3c698330 fffff802`3ada811a     nt!IofCompleteRequest+0x17
19 (Inline Function) --------`--------     Wdf01000!FxIrp::CompleteRequest+0x13
1a fffff802`3c698360 fffff802`3ada5bbf     Wdf01000!FxRequest::CompleteInternal+0x23a
1b (Inline Function) --------`--------     Wdf01000!FxRequest::Complete+0x31
1c fffff802`3c6983f0 fffff802`5085c1ed     Wdf01000!imp_WdfRequestComplete+0x8f
1d fffff802`3c698450 fffff802`5085c0b1     USBXHCI!Bulk_Transfer_CompleteCancelable+0xc9
1e fffff802`3c6984b0 fffff802`5085bea0     USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
1f fffff802`3c698560 fffff802`50856911     USBXHCI!Bulk_EP_TransferEventHandler+0x10
20 fffff802`3c698590 fffff802`50856445     USBXHCI!Endpoint_TransferEventHandler+0xb1
21 fffff802`3c6985f0 fffff802`5085611c     USBXHCI!Interrupter_DeferredWorkProcessor+0x315
22 fffff802`3c6986f0 fffff802`3ada38f6     USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
23 (Inline Function) --------`--------     Wdf01000!FxInterrupt::DpcHandler+0x6e
24 fffff802`3c698720 fffff802`35e8b57e     Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa6
25 fffff802`3c698760 fffff802`35e8a864     nt!KiExecuteAllDpcs+0x30e
26 fffff802`3c6988d0 fffff802`3600050e     nt!KiRetireDpcList+0x1f4
27 fffff802`3c698b60 00000000`00000000     nt!KiIdleLoop+0x9e
The version of rtwlanu.sys that you have installed is old, dating from 2019...
Rich (BB code): 
0: kd> lmDvmrtwlanu
Browse full module list
start             end                 module name
fffff802`56320000 fffff802`56caf000   rtwlanu    (pdb symbols)          c:\mysymbols\rtwlanu.pdb\9C10FF687684407483FA9D0613F6E91F2\rtwlanu.pdb
    Loaded symbol image file: rtwlanu.sys
    Mapped memory image file: c:\mysymbols\rtwlanu.sys\5D3EB1CD98f000\rtwlanu.sys
    Image path: \SystemRoot\System32\drivers\rtwlanu.sys
    Image name: rtwlanu.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 29 11:43:57 2019 (5D3EB1CD)
    CheckSum:         00970F46
    ImageSize:        0098F000
    File version:     1030.38.712.2019
    Product version:  1030.38.712.2019
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Realtek Semiconductor Corporation                         
        ProductName:      Realtek WLAN Wireless USB 2.0 Adapter                                      
        InternalName:     rtwlanu.sys
        OriginalFilename: rtwlanu.sys
        ProductVersion:   1030.38.0712.2019
        FileVersion:      1030.38.0712.2019
        FileDescription:  Realtek WLAN USB NDIS Driver 80816
        LegalCopyright:   Copyright (C) 2014 Realtek Semiconductor Corporation
I would suggest you visit the TOTOLink support site and download the latest driver for your USB wireless adapter.
 
ubuysa said:
Of the five dumps in your upload, four have a length of zero bytes and are thus unusable. The one that is a valid dump is a DPC_WATCHDOG_VIOLATION, which means that the back-end of a device interrupt ran for too long. In the call stack we see a third-party driver being called; rtwlanu.sys. This is a Realtek wireless LAN driver, and also from the call stack it would appear to be a USB attached wireless device. I suspect that this is your TOTOLink Wireless USB Adapter?
Rich (BB code): 
0: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff802`3c6a7e18 fffff802`36043690     nt!KeBugCheckEx
01 fffff802`3c6a7e20 fffff802`35e813c3     nt!KeAccumulateTicks+0x1bfa70
02 fffff802`3c6a7e80 fffff802`35e80eaa     nt!KeClockInterruptNotify+0x453
03 fffff802`3c6a7f30 fffff802`35f3e965     nt!HalpTimerClockIpiRoutine+0x1a
04 fffff802`3c6a7f60 fffff802`35ffdbaa     nt!KiCallInterruptServiceRoutine+0xa5
05 fffff802`3c6a7fb0 fffff802`35ffe377     nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
06 fffff802`3c697930 fffff802`35f405bc     nt!KiInterruptDispatchNoLockNoEtw+0x37
07 fffff802`3c697ac0 fffff802`35e1e678     nt!KxWaitForSpinLockAndAcquire+0x2c
08 fffff802`3c697af0 fffff802`56718558     nt!KeAcquireSpinLockRaiseToDpc+0x88
09 fffff802`3c697b20 fffff802`5644446e     rtwlanu!PlatformAcquireSpinLock+0x88
0a fffff802`3c697b50 fffff802`5640d7b3     rtwlanu!RmMonitorSignalStrength+0x4a
0b fffff802`3c697c10 fffff802`5640d56b     rtwlanu!ProcessReceivedPacketForEachPortSpecific+0x233
0c fffff802`3c697f10 fffff802`565b4cae     rtwlanu!ProcessReceivedPacket+0xd7
0d fffff802`3c697f50 fffff802`565b51a5     rtwlanu!ProcessSegregatedPackets_8821C+0x132
0e fffff802`3c697f90 fffff802`565b4b4d     rtwlanu!SegregateDmaAggPackets_8821C+0x189
0f fffff802`3c698000 fffff802`565b466f     rtwlanu!ParsingRxAggregation_8821C+0x75
10 fffff802`3c698040 fffff802`56366eac     rtwlanu!HalUsbInMpduComplete8821CUsb+0xcb
11 fffff802`3c698090 fffff802`3ada9249     rtwlanu!WdfUsb_InComplete+0x15c
12 fffff802`3c698120 fffff802`3adac854     Wdf01000!FxRequestBase::CompleteSubmitted+0xe9
13 (Inline Function) --------`--------     Wdf01000!FxIoTarget::CompleteRequest+0x8
14 (Inline Function) --------`--------     Wdf01000!FxIoTarget::RequestCompletionRoutine+0xab
15 fffff802`3c6981b0 fffff802`35f25726     Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xe4
16 fffff802`3c698220 fffff802`35e92735     nt!IopUnloadSafeCompletion+0x56
17 fffff802`3c698250 fffff802`35e92577     nt!IopfCompleteRequest+0x1a5
18 fffff802`3c698330 fffff802`3ada811a     nt!IofCompleteRequest+0x17
19 (Inline Function) --------`--------     Wdf01000!FxIrp::CompleteRequest+0x13
1a fffff802`3c698360 fffff802`3ada5bbf     Wdf01000!FxRequest::CompleteInternal+0x23a
1b (Inline Function) --------`--------     Wdf01000!FxRequest::Complete+0x31
1c fffff802`3c6983f0 fffff802`5085c1ed     Wdf01000!imp_WdfRequestComplete+0x8f
1d fffff802`3c698450 fffff802`5085c0b1     USBXHCI!Bulk_Transfer_CompleteCancelable+0xc9
1e fffff802`3c6984b0 fffff802`5085bea0     USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
1f fffff802`3c698560 fffff802`50856911     USBXHCI!Bulk_EP_TransferEventHandler+0x10
20 fffff802`3c698590 fffff802`50856445     USBXHCI!Endpoint_TransferEventHandler+0xb1
21 fffff802`3c6985f0 fffff802`5085611c     USBXHCI!Interrupter_DeferredWorkProcessor+0x315
22 fffff802`3c6986f0 fffff802`3ada38f6     USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
23 (Inline Function) --------`--------     Wdf01000!FxInterrupt::DpcHandler+0x6e
24 fffff802`3c698720 fffff802`35e8b57e     Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa6
25 fffff802`3c698760 fffff802`35e8a864     nt!KiExecuteAllDpcs+0x30e
26 fffff802`3c6988d0 fffff802`3600050e     nt!KiRetireDpcList+0x1f4
27 fffff802`3c698b60 00000000`00000000     nt!KiIdleLoop+0x9e
The version of rtwlanu.sys that you have installed is old, dating from 2019...
Rich (BB code): 
0: kd> lmDvmrtwlanu
Browse full module list
start             end                 module name
fffff802`56320000 fffff802`56caf000   rtwlanu    (pdb symbols)          c:\mysymbols\rtwlanu.pdb\9C10FF687684407483FA9D0613F6E91F2\rtwlanu.pdb
    Loaded symbol image file: rtwlanu.sys
    Mapped memory image file: c:\mysymbols\rtwlanu.sys\5D3EB1CD98f000\rtwlanu.sys
    Image path: \SystemRoot\System32\drivers\rtwlanu.sys
    Image name: rtwlanu.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 29 11:43:57 2019 (5D3EB1CD)
    CheckSum:         00970F46
    ImageSize:        0098F000
    File version:     1030.38.712.2019
    Product version:  1030.38.712.2019
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Realtek Semiconductor Corporation                        
        ProductName:      Realtek WLAN Wireless USB 2.0 Adapter                                     
        InternalName:     rtwlanu.sys
        OriginalFilename: rtwlanu.sys
        ProductVersion:   1030.38.0712.2019
        FileVersion:      1030.38.0712.2019
        FileDescription:  Realtek WLAN USB NDIS Driver 80816
        LegalCopyright:   Copyright (C) 2014 Realtek Semiconductor Corporation
I would suggest you visit the TOTOLink support site and download the latest driver for your USB wireless adapter.
Click to expand...
That is the latest driver from microsoft update....if i download from totolink site the latest driver back to 2017 date....
 
ubuysa said:
Of the five dumps in your upload, four have a length of zero bytes and are thus unusable. The one that is a valid dump is a DPC_WATCHDOG_VIOLATION, which means that the back-end of a device interrupt ran for too long. In the call stack we see a third-party driver being called; rtwlanu.sys. This is a Realtek wireless LAN driver, and also from the call stack it would appear to be a USB attached wireless device. I suspect that this is your TOTOLink Wireless USB Adapter?
Rich (BB code): 
0: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff802`3c6a7e18 fffff802`36043690     nt!KeBugCheckEx
01 fffff802`3c6a7e20 fffff802`35e813c3     nt!KeAccumulateTicks+0x1bfa70
02 fffff802`3c6a7e80 fffff802`35e80eaa     nt!KeClockInterruptNotify+0x453
03 fffff802`3c6a7f30 fffff802`35f3e965     nt!HalpTimerClockIpiRoutine+0x1a
04 fffff802`3c6a7f60 fffff802`35ffdbaa     nt!KiCallInterruptServiceRoutine+0xa5
05 fffff802`3c6a7fb0 fffff802`35ffe377     nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
06 fffff802`3c697930 fffff802`35f405bc     nt!KiInterruptDispatchNoLockNoEtw+0x37
07 fffff802`3c697ac0 fffff802`35e1e678     nt!KxWaitForSpinLockAndAcquire+0x2c
08 fffff802`3c697af0 fffff802`56718558     nt!KeAcquireSpinLockRaiseToDpc+0x88
09 fffff802`3c697b20 fffff802`5644446e     rtwlanu!PlatformAcquireSpinLock+0x88
0a fffff802`3c697b50 fffff802`5640d7b3     rtwlanu!RmMonitorSignalStrength+0x4a
0b fffff802`3c697c10 fffff802`5640d56b     rtwlanu!ProcessReceivedPacketForEachPortSpecific+0x233
0c fffff802`3c697f10 fffff802`565b4cae     rtwlanu!ProcessReceivedPacket+0xd7
0d fffff802`3c697f50 fffff802`565b51a5     rtwlanu!ProcessSegregatedPackets_8821C+0x132
0e fffff802`3c697f90 fffff802`565b4b4d     rtwlanu!SegregateDmaAggPackets_8821C+0x189
0f fffff802`3c698000 fffff802`565b466f     rtwlanu!ParsingRxAggregation_8821C+0x75
10 fffff802`3c698040 fffff802`56366eac     rtwlanu!HalUsbInMpduComplete8821CUsb+0xcb
11 fffff802`3c698090 fffff802`3ada9249     rtwlanu!WdfUsb_InComplete+0x15c
12 fffff802`3c698120 fffff802`3adac854     Wdf01000!FxRequestBase::CompleteSubmitted+0xe9
13 (Inline Function) --------`--------     Wdf01000!FxIoTarget::CompleteRequest+0x8
14 (Inline Function) --------`--------     Wdf01000!FxIoTarget::RequestCompletionRoutine+0xab
15 fffff802`3c6981b0 fffff802`35f25726     Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xe4
16 fffff802`3c698220 fffff802`35e92735     nt!IopUnloadSafeCompletion+0x56
17 fffff802`3c698250 fffff802`35e92577     nt!IopfCompleteRequest+0x1a5
18 fffff802`3c698330 fffff802`3ada811a     nt!IofCompleteRequest+0x17
19 (Inline Function) --------`--------     Wdf01000!FxIrp::CompleteRequest+0x13
1a fffff802`3c698360 fffff802`3ada5bbf     Wdf01000!FxRequest::CompleteInternal+0x23a
1b (Inline Function) --------`--------     Wdf01000!FxRequest::Complete+0x31
1c fffff802`3c6983f0 fffff802`5085c1ed     Wdf01000!imp_WdfRequestComplete+0x8f
1d fffff802`3c698450 fffff802`5085c0b1     USBXHCI!Bulk_Transfer_CompleteCancelable+0xc9
1e fffff802`3c6984b0 fffff802`5085bea0     USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
1f fffff802`3c698560 fffff802`50856911     USBXHCI!Bulk_EP_TransferEventHandler+0x10
20 fffff802`3c698590 fffff802`50856445     USBXHCI!Endpoint_TransferEventHandler+0xb1
21 fffff802`3c6985f0 fffff802`5085611c     USBXHCI!Interrupter_DeferredWorkProcessor+0x315
22 fffff802`3c6986f0 fffff802`3ada38f6     USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
23 (Inline Function) --------`--------     Wdf01000!FxInterrupt::DpcHandler+0x6e
24 fffff802`3c698720 fffff802`35e8b57e     Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa6
25 fffff802`3c698760 fffff802`35e8a864     nt!KiExecuteAllDpcs+0x30e
26 fffff802`3c6988d0 fffff802`3600050e     nt!KiRetireDpcList+0x1f4
27 fffff802`3c698b60 00000000`00000000     nt!KiIdleLoop+0x9e
The version of rtwlanu.sys that you have installed is old, dating from 2019...
Rich (BB code): 
0: kd> lmDvmrtwlanu
Browse full module list
start             end                 module name
fffff802`56320000 fffff802`56caf000   rtwlanu    (pdb symbols)          c:\mysymbols\rtwlanu.pdb\9C10FF687684407483FA9D0613F6E91F2\rtwlanu.pdb
    Loaded symbol image file: rtwlanu.sys
    Mapped memory image file: c:\mysymbols\rtwlanu.sys\5D3EB1CD98f000\rtwlanu.sys
    Image path: \SystemRoot\System32\drivers\rtwlanu.sys
    Image name: rtwlanu.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 29 11:43:57 2019 (5D3EB1CD)
    CheckSum:         00970F46
    ImageSize:        0098F000
    File version:     1030.38.712.2019
    Product version:  1030.38.712.2019
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Realtek Semiconductor Corporation                       
        ProductName:      Realtek WLAN Wireless USB 2.0 Adapter                                    
        InternalName:     rtwlanu.sys
        OriginalFilename: rtwlanu.sys
        ProductVersion:   1030.38.0712.2019
        FileVersion:      1030.38.0712.2019
        FileDescription:  Realtek WLAN USB NDIS Driver 80816
        LegalCopyright:   Copyright (C) 2014 Realtek Semiconductor Corporation
I would suggest you visit the TOTOLink support site and download the latest driver for your USB wireless adapter.
Click to expand...
I suspected the usb wifi adapter faulty because if boot into windows pe the pc also bluescreen after connected to the wifi...but im totally wrong because if connect to other wifi network no bluescreen at all
 
Are there any other dumps in C:\Windows\Minidump?

It could also be the USB port on the PC. If it fails in PE as well then its not a Windows problem.

Do other USB devices work in that port?
 
Last edited:
ubuysa said:
Are there any other dumps in C:\Windows\Minidump?

It could also be the USB port on the PC. If it fails in PE as well then its not a Windows problem.

Do other USB devices work in that port?
Click to expand...
Work perfectly fine
 
Lurizan said:
That is the latest driver from microsoft update....if i download from totolink site the latest driver back to 2017 date....
Click to expand...
I would suggest you delete the existing driver and install the TOTOLink one. The age of a driver doesn't matter - as long as it works - and the TOTLink driver should work.
 
ubuysa said:
I would suggest you delete the existing driver and install the TOTOLink one. The age of a driver doesn't matter - as long as it works - and the TOTLink driver should work.
Click to expand...
use another usb wifi adapter also bsod...i think i fixed the problem. i did system upgrade in media creation tool and so far no bsod...
 
Ok, as long as you're sorted.

BTW. Why would you buy a new PC with Windows 10 installed? Why didn't you ask for Windows 11? Once you're sure the PC is stable you can, and should, upgrade to Windows 11.
 

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

Back
Top