Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD when trying to load drivers for blood meters on one touch sofware

24 Dec 2014   #1
Triggerman770

win 7 home premium 64 bit
 
 
BSOD when trying to load drivers for blood meters on one touch sofware

I get BCC: code 135 and have uploaded the file made by the downloaded program
I have a gateway with 7 home premium 64 bit not sure Intel processor. not sure of those details. the uploaded files are still zipped as I didn't see anything telling me to unzip.
This software loads it drivers to the very end before the bsod. it did it from their website and from the disk they sent.


My System SpecsSystem Spec
.
25 Dec 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Welcome to the forum.

Please remove the software(s) below:

Code:
Start Menu\Programs\Advanced SystemCare Ultimate 7	Public:Start Menu\Programs\Advanced SystemCare Ultimate 7	Public
Start Menu\Programs\Driver Booster 2	Public:Start Menu\Programs\Driver Booster 2	Public
Start Menu\Programs\IObit Malware Fighter	Public:Start Menu\Programs\IObit Malware Fighter	Public
Start Menu\Programs\IObit Uninstaller	Public:Start Menu\Programs\IObit Uninstaller	Public
Start Menu\Programs\Smart Defrag 3	Public:Start Menu\Programs\Smart Defrag 3	Public
Revo Uninstaller:

Use Revo Uninstaller to uninstall stubborn software.



 Clean boot
Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
  • Click on the
  • Type CMD on Search
  • Left click and Run as Administrator
  • Type SFC /scannow
Full tutorial here:
The BSOD was caused by BitDefender. Please remove it and use MSE.

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\HOME-Wed_12_24_2014_175135_71\122414-27268-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325c890
Debug session time: Thu Dec 25 04:21:54.863 2014 (UTC + 6:00)
System Uptime: 0 days 6:53:31.034
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 135, {ffffffffc0000005, fffff880082b05e0, fffff88002686b00, fffff8a00132b010}

*** WARNING: Unable to verify timestamp for bdfsfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfsfltr.sys
Probably caused by : bdfsfltr.sys ( bdfsfltr+41983 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REGISTRY_FILTER_DRIVER_EXCEPTION (135)
This bugcheck is caused by an unhandled exception in a registry filtering driver.
This bugcheck indicates that a registry filtering driver didn't handle exception inside
its notification routine. One can identify the driver by the 3rd parameter.
Arguments:
Arg1: ffffffffc0000005, ExceptionCode
Arg2: fffff880082b05e0, Address of the context record for the exception that caused the bugcheck
Arg3: fffff88002686b00, The driver's callback routine address
Arg4: fffff8a00132b010, Internal

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x135

PROCESS_NAME:  CP210xVCPInsta

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff880082b0d88 -- (.exr 0xfffff880082b0d88)
ExceptionAddress: fffff880026ba983 (bdfsfltr+0x0000000000041983)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000001234567b
Attempt to read from address 000000001234567b

TRAP_FRAME:  fffff880082b0e30 -- (.trap 0xfffff880082b0e30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000084 rbx=0000000000000000 rcx=fffffa8007c96b2d
rdx=000005800a6aeb4e rsi=0000000000000000 rdi=0000000000000000
rip=fffff880026ba983 rsp=fffff880082b0fc8 rbp=0000000000000001
 r8=0000000000000004  r9=0000000000000000 r10=0052005400530049
r11=fffffa8007c96b2a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
bdfsfltr+0x41983:
fffff880`026ba983 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034057e4 to fffff8000308ebc0

STACK_TEXT:  
fffff880`082afdb8 fffff800`034057e4 : 00000000`00000135 ffffffff`c0000005 fffff880`082b05e0 fffff880`02686b00 : nt!KeBugCheckEx
fffff880`082afdc0 fffff800`0343a4ed : 00000000`00000000 00000001`00000001 00000000`00000001 fffff880`082b01e0 : nt!CmpFatalFilter+0x24
fffff880`082afe00 fffff800`030b9cdc : 00000000`00000010 fffff960`000c7794 fffff960`00327170 fffff800`032c9ac0 : nt!CmpCallCallBacks+0x556
fffff880`082afe30 fffff800`030b975d : fffff800`031f9cc4 fffff880`082b1230 00000000`00000000 fffff800`03019000 : nt!_C_specific_handler+0x8c
fffff880`082afea0 fffff800`030b8535 : fffff800`031f9cc4 fffff880`082aff18 fffff880`082b0d88 fffff800`03019000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`082afed0 fffff800`030c94c1 : fffff880`082b0d88 fffff880`082b05e0 fffff880`00000000 fffffa80`07c969c0 : nt!RtlDispatchException+0x415
fffff880`082b05b0 fffff800`0308e242 : fffff880`082b0d88 00000000`00000000 fffff880`082b0e30 fffffa80`07c969c0 : nt!KiDispatchException+0x135
fffff880`082b0c50 fffff800`0308cdba : 00000000`00000000 00000000`1234567b fffff880`082b1100 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`082b0e30 fffff880`026ba983 : fffff880`026aaf94 00000000`00000000 00000000`00000001 fffffa80`07c969c0 : nt!KiPageFault+0x23a
fffff880`082b0fc8 fffff880`026aaf94 : 00000000`00000000 00000000`00000001 fffffa80`07c969c0 fffffa80`07c969c0 : bdfsfltr+0x41983
fffff880`082b0fd0 00000000`00000000 : 00000000`00000001 fffffa80`07c969c0 fffffa80`07c969c0 fffff8a0`056dd800 : bdfsfltr+0x31f94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bdfsfltr+41983
fffff880`026ba983 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  bdfsfltr+41983

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bdfsfltr

IMAGE_NAME:  bdfsfltr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d89fb21

FAILURE_BUCKET_ID:  X64_0x135_bdfsfltr+41983

BUCKET_ID:  X64_0x135_bdfsfltr+41983

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

0: kd> lmvm bdfsfltr
start             end                 module name
fffff880`02679000 fffff880`026e9000   bdfsfltr T (no symbols)           
    Loaded symbol image file: bdfsfltr.sys
    Image path: \??\C:\Windows\system32\Drivers\bdfsfltr.sys
    Image name: bdfsfltr.sys
    Timestamp:        Wed Mar 23 19:52:33 2011 (4D89FB21)
    CheckSum:         0006B11C
    ImageSize:        00070000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

warning   Warning
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.



Make scans with the following:

Kaspersky TDSSKillerESET online scanner:
Temp Monitoring

Check for heating issues using Speccy or HWMonitor.


Upload a screen shot with either of the tools: Screenshots and Files - Upload and Post in Seven Forums
My System SpecsSystem Spec
25 Dec 2014   #3
Triggerman770

win 7 home premium 64 bit
 
 

didn't know I had Bit Defender. I didn't download it. will remove it. now to the other programs are you saying remove them as your personal preference? I have had those for years and never had a problem?
My System SpecsSystem Spec
.

25 Dec 2014   #4
Triggerman770

win 7 home premium 64 bit
 
 
BSOD solved

was corrupted driver on software disk and download site
My System SpecsSystem Spec
25 Dec 2014   #5
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Observe for sometime and then mark this thread as solved
My System SpecsSystem Spec
Reply

 BSOD when trying to load drivers for blood meters on one touch sofware




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Elo 55" Interactive Digital Signage Touch Computer touch problem
This has a built in CPU (i5) with Win7 32bit installed. The IDS touch screen was working fine, the it stopped working. The thing is, the Touch screen calibrates fine using Elo calibration software for spotting the corners of the screen but when you do the mouse check, it does not recognize...
Hardware & Devices
BSOD while playing Far Cry 3 Blood Dragon. Can't remember error number
Hello, I've been blue screening with a frequency that I don't really care for. The dump file is attached. Please take a look. Thanks
BSOD Help and Support
my touch screen dont work .... bad drivers
hello i heave a nettop mini pc and i have a 7" super sk-8802-a touch screen monitor. when i purhcased it from ebay the seller told me the drivers support windows 7 . i got it and it supports everything below xp and as well as xp. i rather see if i can get it to work rather than sending it back i...
Drivers
1525 touch pad drivers
i had the same problem with no win7 drivers for my inspiron 1525 dell download vista 32 drivers didn't work either so i downloaded touch pad drivers for the 1545 option win 7 64 bit and it worked perfect just thought i would share this with you :)
Drivers
N-Trig Releases Multi-Touch Drivers for Windows 7 RC
N-Trig Releases Multi-Touch Drivers (Beta) for Windows 7 RC ...
Drivers


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:55.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App