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 logging in Windows Error: 0xD1

23 Jul 2014   #1
david21094

Windows 7 Home Premium 64-bit
 
 
BSoD when logging in Windows Error: 0xD1

Hi this is what i have here and this is what I get System Information (local)
--------------------------------------------------------------------------------

computer name: INTERN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Inspiron 660, Dell Inc., 084J0R
CPU: GenuineIntel Intel(R) Pentium(R) CPU G2030 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4160258048 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 7/23/2014 2:17:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072314-11965-01.dmp
This was probably caused by the following module: monblanking.sys (0xFFFFF880039E1700)
Bugcheck code: 0xD1 (0xFFFFF9804754AFE0, 0x2, 0x0, 0xFFFFF880039E1700)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\monblanking.sys
product: Citrix ICA Host
company: Citrix Systems, Inc.
description: Citrix HDX 3D for Pro Graphics Monitor Blanking Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: monblanking.sys (Citrix HDX 3D for Pro Graphics Monitor Blanking Driver, Citrix Systems, Inc.).
Google query: Citrix Systems, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 7/23/2014 2:17:04 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: monblanking.sys (monblanking+0x1700)
Bugcheck code: 0xD1 (0xFFFFF9804754AFE0, 0x2, 0x0, 0xFFFFF880039E1700)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\monblanking.sys
product: Citrix ICA Host
company: Citrix Systems, Inc.
description: Citrix HDX 3D for Pro Graphics Monitor Blanking Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: monblanking.sys (Citrix HDX 3D for Pro Graphics Monitor Blanking Driver, Citrix Systems, Inc.).
Google query: Citrix Systems, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 7/23/2014 2:15:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072314-24741-01.dmp
This was probably caused by the following module: monblanking.sys (0xFFFFF88003C9A700)
Bugcheck code: 0xD1 (0xFFFFF980478C0FE0, 0x2, 0x0, 0xFFFFF88003C9A700)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\monblanking.sys
product: Citrix ICA Host
company: Citrix Systems, Inc.
description: Citrix HDX 3D for Pro Graphics Monitor Blanking Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: monblanking.sys (Citrix HDX 3D for Pro Graphics Monitor Blanking Driver, Citrix Systems, Inc.).
Google query: Citrix Systems, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 7/21/2014 9:46:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072314-11622-01.dmp
This was probably caused by the following module: monblanking.sys (0xFFFFF88003847700)
Bugcheck code: 0xD1 (0xFFFFF98047764FE0, 0x2, 0x0, 0xFFFFF88003847700)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\monblanking.sys
product: Citrix ICA Host
company: Citrix Systems, Inc.
description: Citrix HDX 3D for Pro Graphics Monitor Blanking Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: monblanking.sys (Citrix HDX 3D for Pro Graphics Monitor Blanking Driver, Citrix Systems, Inc.).
Google query: Citrix Systems, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 7/21/2014 9:36:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072114-12355-01.dmp
This was probably caused by the following module: monblanking.sys (0xFFFFF88004C6E700)
Bugcheck code: 0xD1 (0xFFFFF98043B26FE0, 0x2, 0x0, 0xFFFFF88004C6E700)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\monblanking.sys
product: Citrix ICA Host
company: Citrix Systems, Inc.
description: Citrix HDX 3D for Pro Graphics Monitor Blanking Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: monblanking.sys (Citrix HDX 3D for Pro Graphics Monitor Blanking Driver, Citrix Systems, Inc.).
Google query: Citrix Systems, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 7/17/2014 1:38:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071714-22432-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Fri 7/11/2014 3:32:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071114-31652-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD4362)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001CD4362, 0xFFFFF8800AE37C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/9/2014 5:48:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070914-29406-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD4362)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001ED5362, 0xFFFFF88007DD5C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 7/8/2014 9:26:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070814-31247-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD4362)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001CD4362, 0xFFFFF880231F9C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 7/3/2014 8:37:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070314-20560-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD4362)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001CD5362, 0xFFFFF880089D8C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

10 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

monblanking.sys (Citrix HDX 3D for Pro Graphics Monitor Blanking Driver, Citrix Systems, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

I have the file here for you guys to check out


My System SpecsSystem Spec
.
23 Jul 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The BSODs are caused by Citrix HDX 3D for Pro Graphics Monitor Blanking Driver.
Code:
BugCheck D1, {fffff9804754afe0, 2, 0, fffff880039e1700}

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

Followup: MachineOwner
---------
Either you may uninstall Critix
Code:
Start Menu\Programs\Citrix
Or you may contract Critix for a feasible solution for it.

If it is not a work computer and VPN etc is not a must, I would go for uninstalling critix.
My System SpecsSystem Spec
23 Jul 2014   #3
david21094

Windows 7 Home Premium 64-bit
 
 

Thank you very much. I wanted to make sure of there was anything else causing the BSoD.
My System SpecsSystem Spec
.

24 Jul 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

OK, let us know for any further issue.
My System SpecsSystem Spec
Reply

 BSoD when logging in Windows Error: 0xD1




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD several times a day during general use, error 0xd1
IRQL Not Less or Equal error 2-3 times a day, has occured while playing League of Legends, Smite, watching Youtube videos, and chatting on Skype. I've been having some trouble with the log collector software (it constantly spits out a .zip file that contains either nothing or only 2 minidump...
BSOD Help and Support
BSOD, while gaming and just web browsing, error 0xd1
Hi guys, On the first day I experienced this BSOD issue, it was while gaming. On the 2nd day, I experienced it while playing League of Legends first, and then 2 more times while just using Skype video chat and web browsing. On the second day, it happened 3 times in a span of about 45 mins, all...
BSOD Help and Support
Too many BSOD error, 0x124, 0xD1,0x1E and many more
I just experienced different BSOD error number everytime it freezes. At first it was just 0x124 but after restoring to factory settings my Toshiba satellite U500 18-L eventually encountered more BSOD errors. Below is the file generated by SF Tools
BSOD Help and Support
Numerous BSOD playing games, recently error 0xd1
Whenever I play games (diablo, amnesia dark descent) my computer will crash after awhile. Sometimes it takes over an hour, other times in 5 mins. I used bluescreenview and it seems like each bsod is slightly different. I'm very overwhelmed with all the possibilities with what could be going wrong,...
BSOD Help and Support
BSOD after run Windows XP mode, error 0xd1
After run any virtual computer (Windows XP mode) Windows Virtual PC crashes to BSOD 0x000000d1. In safe mode I can't run virtul PC (can't run virtualpc server), after diagnostic startup (msconfig) system crashes too. I tried almost everything. Please help me.
BSOD Help and Support
BSOD playing GTA IV Multiplayer, error 0xd1 0xe1.
Is Windows 7 . . . - x86 (32-bit) or x64 ? x64. - the original installed OS on the system? Yes, I built this system. - an OEM or full retail version? Its an OEM. It didnt come with since I built this. - OEM = came pre-installed on system - Full Retail = you purchased it from retailer -...
BSOD Help and Support


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 07:12.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App