New
#1
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
Quote