Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Unexpected crash during RDP session


  • Please log in to reply
8 replies to this topic

#1 Suncatcher

Suncatcher

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Local time:06:02 AM

Posted 07 January 2017 - 04:05 AM

Hi, there,

well, this happened during RDP session without any visible reason, but I suppose that this is connected with redirected local storage, and bugcheck 0x27 code tells us so.

Attached logs/reports according guidelines, additionally attached analysis of dump from WinDbg I made via !analyze -v command

 

 

 

 
Microsoft ® Windows Debugger Version 10.0.14321.1024 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
 
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
Machine Name:
Kernel base = 0xfffff800`0b47f000 PsLoadedModuleList = 0xfffff800`0b784060
Debug session time: Sat Jan  7 09:34:13.698 2017 (UTC + 2:00)
System Uptime: 1 days 23:32:06.501
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
 
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 27, {fcb0027c, ffffe487c56576d8, ffffe487be9be520, 0}
 
Page 200 not present in the dump file. Type ".hh dbgerr004" for details
Page 200 not present in the dump file. Type ".hh dbgerr004" for details
Page 200 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : rdbss.sys ( rdbss!RxSelectAndSwitchPagingFileObject+aa99 )
 
Followup:     MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
RDR_FILE_SYSTEM (27)
    If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the
    exception record and context record. Do a .cxr on the 3rd parameter and then kb to
    obtain a more informative stack trace.
    The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined
    as follows:
     RDBSS_BUG_CHECK_CACHESUP  = 0xca550000,
     RDBSS_BUG_CHECK_CLEANUP   = 0xc1ee0000,
     RDBSS_BUG_CHECK_CLOSE     = 0xc10e0000,
     RDBSS_BUG_CHECK_NTEXCEPT  = 0xbaad0000,
Arguments:
Arg1: 00000000fcb0027c
Arg2: ffffe487c56576d8
Arg3: ffffe487be9be520
Arg4: 0000000000000000
 
Debugging Details:
------------------
 
Page 200 not present in the dump file. Type ".hh dbgerr004" for details
Page 200 not present in the dump file. Type ".hh dbgerr004" for details
Page 200 not present in the dump file. Type ".hh dbgerr004" for details
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  14393.576.amd64fre.rs1_release_inmarket.161208-2252
 
SYSTEM_MANUFACTURER:  Dell Inc.
 
SYSTEM_PRODUCT_NAME:  Inspiron 7559
 
SYSTEM_SKU:  0706
 
SYSTEM_VERSION:  1.2.0
 
BIOS_VENDOR:  Dell Inc.
 
BIOS_VERSION:  1.2.0
 
BIOS_DATE:  09/22/2016
 
BASEBOARD_MANUFACTURER:  Dell Inc.
 
BASEBOARD_PRODUCT:  0H87XC
 
BASEBOARD_VERSION:  A00
 
DUMP_TYPE:  1
 
BUGCHECK_P1: fcb0027c
 
BUGCHECK_P2: ffffe487c56576d8
 
BUGCHECK_P3: ffffe487be9be520
 
BUGCHECK_P4: 0
 
EXCEPTION_RECORD:  ffffe487c56576d8 -- (.exr 0xffffe487c56576d8)
ExceptionAddress: ffffe487c56576e8
   ExceptionCode: 0130ec30
  ExceptionFlags: 00000001
NumberParameters: -983206168
   Parameter[0]: ffffe487c56575e0
   Parameter[1]: ffffe487be9be520
   Parameter[2]: ffffc20e0cbd5c50
   Parameter[3]: ffffc20e0b57d110
   Parameter[4]: ffffc20e0a7ce270
   Parameter[5]: 0000000006400200
   Parameter[6]: 0000000000000000
   Parameter[7]: 0000000000000000
   Parameter[8]: 0000000000000000
   Parameter[9]: ffffe487c5657698
   Parameter[10]: ffffe487c5657698
   Parameter[11]: ffffe487c5657750
   Parameter[12]: ffffe487c5657750
   Parameter[13]: 0000000001000000
   Parameter[14]: 0000000000000000
 
CONTEXT:  ffffe487be9be520 -- (.cxr 0xffffe487be9be520)
rax=0000000000000000 rbx=0000000000400800 rcx=0000000000000000
rdx=0040000000000003 rsi=0000000000000000 rdi=0000000000000001
rip=ffffe487c5657668 rsp=ffffffffffffffff rbp=ffffffffffffffff
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=00a71da000000000
iopl=2 vip vif nv dn di ng nz na po cy
cs=e558  ss=be9b  ds=be9b  es=e487  fs=ffff  gs=e558             efl=ffffe487
e558:7668 ??              ???
Resetting default scope
 
CPU_COUNT: 4
 
CPU_MHZ: 900
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 5e
 
CPU_STEPPING: 3
 
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x27
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ERROR_CODE: (NTSTATUS) 0x130ec30 - <Unable to get error code text>
 
EXCEPTION_CODE: (Win32) 0x130ec30 (19983408) - <Unable to get error code text>
 
EXCEPTION_CODE_STR:  130ec30
 
EXCEPTION_PARAMETER1:  ffffe487c56575e0
 
EXCEPTION_PARAMETER2:  ffffe487be9be520
 
EXCEPTION_PARAMETER3:  ffffc20e0cbd5c50
 
EXCEPTION_PARAMETER4: 0
 
ANALYSIS_SESSION_HOST:  DELLANO
 
ANALYSIS_SESSION_TIME:  01-07-2017 10:58:20.0314
 
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
 
LAST_CONTROL_TRANSFER:  from 0000000000000000 to ffffe487c5657668
 
BAD_STACK_POINTER:  ffffffffffffffff
 
UNALIGNED_STACK_POINTER:  ffffffffffffffff
 
STACK_TEXT:  
ffffb201`45373378 fffff802`5c28fcc9 : 00000000`00000027 00000000`fcb0027c ffffe487`c56576d8 ffffe487`be9be520 : nt!KeBugCheckEx
ffffb201`45373380 fffff802`5c2c3cf6 : ffffe487`00000000 00000000`00000000 ffffc20e`0721d301 ffffc20e`0721d350 : rdbss!RxSelectAndSwitchPagingFileObject+0xaa99
ffffb201`453734d0 fffff802`5c28299b : ffffc20e`0721d350 ffffe487`be9be520 ffffe487`c56576d8 00000000`00000000 : rdbss!RxCommonClose+0x126
ffffb201`45373570 fffff802`5c2be6e6 : 00000000`00000000 ffffc20e`00000000 ffffc20e`07f3a69c ffffc20e`0cbd5c50 : rdbss!RxFsdCommonDispatch+0x55b
ffffb201`453736f0 fffff802`61251203 : ffffc20e`0a665620 ffffc20e`0f2e2dc0 ffffc20e`0737c010 fffff802`5b4f4ba3 : rdbss!RxFsdDispatch+0x86
ffffb201`45373740 fffff802`5c58dc8c : ffffc20e`0b962010 ffffc20e`0b962010 00000000`00000000 ffffc20e`0fa4a8e8 : rdpdr!DrPeekDispatch+0x203
ffffb201`453737c0 fffff802`5c58c64c : ffffe487`af15d800 ffffc20e`0cbd5c50 ffffc20e`0fa4a740 ffffc20e`0b962010 : mup!MupStateMachine+0x1dc
ffffb201`45373830 fffff802`5b4f5206 : ffffc20e`0737c010 00000000`00000000 ffffc20e`0d06b010 ffffb201`45373940 : mup!MupClose+0x8c
ffffb201`45373890 fffff802`5b4f3146 : ffffc20e`06d59500 ffffc20e`07e58df0 00000000`00000001 ffffc20e`06c96240 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a6
ffffb201`45373920 fffff800`0b90b86d : ffffc20e`0cbd5c50 00000000`00000001 ffffc20e`0fa4a740 ffffc20e`08dafd80 : FLTMGR!FltpDispatch+0xb6
ffffb201`45373980 fffff800`0b906ce8 : fffff800`0b8a10ec 00000000`00000001 ffffc20e`06ca76e0 00000000`00000001 : nt!IopDeleteFile+0x12d
ffffb201`45373a00 fffff800`0b8a13c0 : 00000000`00000000 ffffc20e`0cbd5c20 fffff800`0b8a10ec fffff800`0b781d80 : nt!ObpRemoveObjectRoutine+0x78
ffffb201`45373a60 fffff800`0b5161b9 : ffffc20e`11ade7c0 fffff800`0b8a10ec fffff800`0b781d80 00000000`a620708b : nt!ObpProcessRemoveObjectQueue+0x2d4
ffffb201`45373b00 fffff800`0b481729 : 00000000`00000000 00000000`00000080 ffffc20e`06cab040 ffffc20e`11ade7c0 : nt!ExpWorkerThread+0xe9
ffffb201`45373b90 fffff800`0b5cebb6 : ffffb201`3b440180 ffffc20e`11ade7c0 fffff800`0b4816e8 ffffb201`45373ca0 : nt!PspSystemThreadStartup+0x41
ffffb201`45373be0 00000000`00000000 : ffffb201`45374000 ffffb201`4536d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  63fdefc2918e145d88f7a85d117da71842bda082
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d247342837d0bf9d42e1a0c67ff9590e580c7afe
 
THREAD_SHA1_HASH_MOD:  ed6fe6e7b54740eb8140216d5f68249590f044fd
 
FOLLOWUP_IP: 
rdbss!RxSelectAndSwitchPagingFileObject+aa99
fffff802`5c28fcc9 cc              int     3
 
FAULT_INSTR_CODE:  cf8b49cc
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  rdbss!RxSelectAndSwitchPagingFileObject+aa99
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: rdbss
 
IMAGE_NAME:  rdbss.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  58258a93
 
BUCKET_ID_FUNC_OFFSET:  aa99
 
FAILURE_BUCKET_ID:  0x27_STACKPTR_ERROR_rdbss!RxSelectAndSwitchPagingFileObject
 
BUCKET_ID:  0x27_STACKPTR_ERROR_rdbss!RxSelectAndSwitchPagingFileObject
 
PRIMARY_PROBLEM_CLASS:  0x27_STACKPTR_ERROR_rdbss!RxSelectAndSwitchPagingFileObject
 
TARGET_TIME:  2017-01-07T07:34:13.000Z
 
OSBUILD:  14393
 
OSSERVICEPACK:  0
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2016-12-09 11:23:02
 
BUILDDATESTAMP_STR:  161208-2252
 
BUILDLAB_STR:  rs1_release_inmarket
 
BUILDOSVER_STR:  10.0.14393.576.amd64fre.rs1_release_inmarket.161208-2252
 
ANALYSIS_SESSION_ELAPSED_TIME: c68
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x27_stackptr_error_rdbss!rxselectandswitchpagingfileobject
 
FAILURE_ID_HASH:  {b874da1d-c0ec-3942-d2ad-623a22f6ba89}
 
Followup:     MachineOwner
---------

 

· OS - Windows 10 x64 Pro
· x64
· Originally Win10 Home was installed
· OEM version
· Less than a year (bought in 2016)
· Age of OS installation - 4 days. I reinstalled Win 10 Anniversary just recently

· CPU = Core i5 6300HQ
· Video Card = Onboard Intel HD Graphics 530 + Discrete Nvidia GTX 960M

· System Manufacturer = Dell
· Exact model number = Dell Inspiron 7559

· Laptop

Attached Files



BC AdBot (Login to Remove)

 


#2 Suncatcher

Suncatcher
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Local time:06:02 AM

Posted 09 January 2017 - 09:44 AM

I assume this is MS bug and is to be fixed by them.


Edited by Suncatcher, 10 January 2017 - 09:15 AM.


#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:02 PM

Posted 10 January 2017 - 08:29 AM

Your UEFI/BIOS (version 1.2.0) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 3 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

D: drive only has about 7% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

My best guess here is that it's most likely due to missing Windows Updates.

If the updates are all there, then I'd suspect the bug (but am not all that familiar with it).

Good luck!

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Jan  7 02:34:13.698 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010717-6859-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:1 days 23:32:06.501
*** ERROR: Module load completed but symbols could not be loaded for rdpdr.sys
Probably caused by :rdbss.sys ( rdbss!RxGetRDBSSProcess+3749 )
BugCheck 27, {fcb0027c, ffffe487c56576d8, ffffe487be9be520, 0}
BugCheck Info: RDR_FILE_SYSTEM (27)
Arguments:
Arg1: 00000000fcb0027c
Arg2: ffffe487c56576d8
Arg3: ffffe487be9be520
Arg4: 0000000000000000
BUGCHECK_STR:  0x27
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x27_STACKPTR_ERROR_rdbss!RxGetRDBSSProcess
CPUID:        "Intel® Core™ i5-6300HQ CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2304
  BIOS Version                  1.2.0
  BIOS Release Date             09/22/2016
  Manufacturer                  Dell Inc.
  Product Name                  Inspiron 7559
  Baseboard Product             0H87XC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sat Jan  7 02:34:13.698 2017 (UTC - 5:00)**************************
DellRbtn.sys                Fri Aug  3 17:32:54 2012 (501C4386)
rt640x64.sys                Thu Jan 21 03:17:40 2016 (56A09424)
Netwtw04.sys                Thu Feb 25 13:26:53 2016 (56CF476D)
iaLPSS2i_I2C.sys            Wed Mar  2 21:06:42 2016 (56D79C32)
iaLPSS2i_GPIO2.sys          Wed Mar  2 21:06:59 2016 (56D79C43)
RtsPer.sys                  Mon Mar  7 02:10:54 2016 (56DD297E)
TeeDriverW8x64.sys          Mon Mar 28 14:59:41 2016 (56F97F1D)
IntcDAud.sys                Fri Apr 15 22:54:21 2016 (5711A95D)
igdkmd64.sys                Wed May  4 15:21:11 2016 (572A4BA7)
dptf_acpi.sys               Mon May 16 14:31:46 2016 (573A1212)
dptf_cpu.sys                Mon May 16 14:31:47 2016 (573A1213)
esif_lf.sys                 Mon May 16 14:31:57 2016 (573A121D)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
RTKVHD64.sys                Fri Aug 12 06:01:39 2016 (57AD9E83)
ibtusb.sys                  Fri Sep  2 15:37:28 2016 (57C9D4F8)
nvvad64v.sys                Tue Oct  4 03:20:09 2016 (57F35829)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
VBoxNetLwf.sys              Tue Dec 20 10:29:45 2016 (58594E69)
VBoxUSBMon.sys              Tue Dec 20 10:29:45 2016 (58594E69)
VBoxDrv.sys                 Tue Dec 20 10:29:45 2016 (58594E69)
VBoxNetAdp6.sys             Tue Dec 20 10:29:45 2016 (58594E69)


http://www.carrona.org/drivers/driver.php?id=DellRbtn.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
Netwtw04.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iaLPSS2i_I2C.sys
iaLPSS2i_GPIO2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=dptf_acpi.sys
http://www.carrona.org/drivers/driver.php?id=dptf_cpu.sys
http://www.carrona.org/drivers/driver.php?id=esif_lf.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetAdp6.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#4 Suncatcher

Suncatcher
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Local time:06:02 AM

Posted 11 January 2017 - 04:14 AM

Only 3 Windows Update hotfixes installed.

 

Well, just now I checked for updates, it installed several cumulative updates but no hotfixes. wmic qfe get Hotfixid command still gives me 3 hotfixes:

HotFixID
KB3199986
KB3214628
KB3213986

Where can I check what updates are intended for my system?

The drivers that follow belong to software or devices that were not developed by Microsoft. 

 

Do you think some 3rd party drivers can be cause of this issue? The bug code explicitly says that rdbss.sys is the reason.


Edited by Suncatcher, 11 January 2017 - 04:15 AM.


#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:02 PM

Posted 11 January 2017 - 03:39 PM

I'm not a Windows Update expert.

I simply check teh number of hotfixes listed towards the bottom of the systeminfo.txt report

Most W10 Anniversary Update systems have 7 hotfixes - but each system can be different.

The point here is to check - if it says there isn't anything available, then you'll just have to take it's word for it (as long as there's no errors).

 

90+% for BSOD's are due to 3rd party drivers (about 10% are hardware, and less than 1% are due to Windows Updates (on fully updated systems)).

 

While I suspect the rdbss.sys driver (and the bug you pointed out), here's a scenario where the wrong driver can get blamed:

A 3rd party driver writes to memory space owned by rdbss.sys

The 3rd party driver then exits.

Later on, rdbss.sys accesses that memory space, finds data there that shouldn't be there (that the 3rd party drive wrote there).

It panics and throws a BSOD to protect the system.

As there's no sign left of the 3rd party driver, the system has no other choice than to blame rdbss.sys for the error (even though it really isn't to blame).

 

Also, some BSOD's are complicated and happen due to interactions between drivers.

As such, if you remove one of the problem drivers, the other problem driver won't have that guy to kick around any more - so that'd appear to fix the BSOD's.
That's (in general) what the suggestions I made in my previous post are for - to help reduce the number of likely BSOD causes.

 

I would suggest trying to see if the BSOD recurs each time you use the same conditions.

If it does, then we'll also try Driver Verifier (hoping to get luck and have it find a 3rd party driver to blame).

 

Finally, the only way to update Windows drivers is through Windows Update.  Rarely can you remove these drivers without going through a lot of contortions.

But with 3rd party drivers, they're relatively easy to uninstall and test


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 Suncatcher

Suncatcher
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Local time:06:02 AM

Posted 12 January 2017 - 01:23 PM

Well, I came across this guide and tun Verifier session as described. I don't fully got the idea what is 

Driver Verifier needs to run for 24 hours minimum - even if the status screen appears clear.

 

What means for 24 hours? Frequently boot the system throughout the 24h or how? 

And what is status screen is clear? What should I search for there? On what values to pay attention?

 

Your UEFI/BIOS (version 1.2.0) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.

 

Unfortunately, this is the latest BIOS they have on Dell site.


Edited by Suncatcher, 12 January 2017 - 01:23 PM.


#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:02 PM

Posted 15 January 2017 - 06:34 AM

Please provide a link to the guide.

I normally suggest running Driver Verifier for 36 hours - that's total amount of time that the system is on in normal use.
I have no idea what they mean by status screen is clear - AFAIK, there's no status screen for verifier.

The "results" of Driver Verifier are a BSOD - and we analyze that memory dump in order to see if a particular driver is blamed while running verifier.

 

There's 3 possibilities here:

- a Driver Verifier enabled memory dump

- a memory dump that isn't Driver Verifier enabled

- no memory dump.

Analysis is different for each situation.

 

Don't worry about the BIOS/UEFI - a 2016 version is likely the best you'll find.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#8 Suncatcher

Suncatcher
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Local time:06:02 AM

Posted 15 January 2017 - 08:59 AM

Please provide a link to the guide.

 

I mean guide that stuck in the top of the section.

 

There's 3 possibilities here:

- a Driver Verifier enabled memory dump

- a memory dump that isn't Driver Verifier enabled

- no memory dump.

 

 

I have a third variant - no dump, but I enabled Verifier only for 10 minutes and made only one reboot. Should this 36 hours include frequent reboots or I just can work in a regular way? Usually I don't reboot for days and my uptime can be a week or more.



#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:11:02 PM

Posted 17 January 2017 - 07:17 AM

I believe that jcgriff2 meant that this is the status screen (in his post/link):

 

To check Driver Verifier status -

 

 

The 24/36 hour estimate is just that, an estimate.

It's not a hard and fast rule, so there's no need to worry about exactly how it's run - as long as it's run long enough to either generate a BSOD or figure that it won't have one.

Most often, if it is going to BSOD, then it will do it faster than it usually BSOD's - but there's just too many variables for us to tell what's going to happen.

 

Use the PC normally. 

If the BSOD's happen during an RDP session, then run the RDP session while Driver Verifier is turned on.

If the system always BSOD's during an RDP session, then you can expect that Driver Verifier will also BSOD during an RDP session IF the BSOD is caused by a driver and if Driver Verifier is set to test the driver with a test that will stress it to failure (a whole lotta "if's")

 

If this is a Windows bug (and no 3rd party drivers are involved), then we might suggest a 2nd Driver Verifier test - running it with the standard settings (which includes Windows drivers)

I'd suggest this if Driver Verifier (using our settings) doesn't produce a Driver Verifier enabled BSOD and memory dump.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users