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: Blue Screen Crash On Win 7 x86

19 Apr 2010   #21
Blackhawk131

 
 

How are you able to view these logs? Also how did you narrow that down? I have not had that connected the last 2 days, but the first time it started I was configuring an Enterasys switch and that usb to serial adapter was connected. So just because the driver is on the system it is causing the system to crash? I cannot view the driver in device manager unless the cable is installed, should I plug in the cable an un-install the driver?


My System SpecsSystem Spec
.
19 Apr 2010   #22
Blackhawk131

 
 

Is this the driver that you want me to remove?


Attached Images
Blue Screen Crash On Win 7 x86-usb2serial.png 
My System SpecsSystem Spec
19 Apr 2010   #23
Jonathan_King

Windows 7 Professional x64
 
 

This is the driver you need to remove: ser2pl64.sys

Go to C:\Windows\System32\Drivers\ and delete ser2pl64.sys.

I use Microsoft's Debugging Tools for Windows. See this page if you are interested in learning to debug yourself: https://www.sevenforums.com/crash-loc...ing-tools.html
My System SpecsSystem Spec
.

19 Apr 2010   #24
Blackhawk131

 
 

Can this driver cause the problem even though the cable is not in use?
My System SpecsSystem Spec
19 Apr 2010   #25
Tews

64-bit Windows 8.1 Pro
 
 

Yes... just because the cable is not plugged in does not mean that the driver is not being loaded...Follow Jonathans excellent advise, and let us know what happes..
My System SpecsSystem Spec
26 Apr 2010   #26
Blackhawk131

 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
This is the driver you need to remove: ser2pl64.sys

Go to C:\Windows\System32\Drivers\ and delete ser2pl64.sys.

I use Microsoft's Debugging Tools for Windows. See this page if you are interested in learning to debug yourself: https://www.sevenforums.com/crash-loc...ing-tools.html

I went 10 days without a crash and then it did it again. I tried to find a updated driver for my usb2serial connector, but maybe this one is the problem also. I have attahced the dump.


Attached Files
File Type: rar 042610-26816-01.rar (27.2 KB, 11 views)
My System SpecsSystem Spec
27 Apr 2010   #27
Jonathan_King

Windows 7 Professional x64
 
 

Pretty straightforward, Novell is causing the problem. Uninstall that completely using Revo Uninstaller.

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


Loading Dump File [C:\Users\Jonathan\Desktop\042610-26816-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e89e50
Debug session time: Mon Apr 26 21:16:29.831 2010 (GMT-4)
System Uptime: 4 days 10:34:00.782
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image \??\C:\Program Files\Novell\Client\XTier\Drivers\ncpl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ncpl.sys
*** ERROR: Module load completed but symbols could not be loaded for ncpl.sys
Unable to load image \??\C:\Program Files\Novell\Client\XTier\Drivers\nccache.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nccache.sys
*** ERROR: Module load completed but symbols could not be loaded for nccache.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003d53c2b, fffff8800e1e82c8, fffff8800e1e7b30}

Probably caused by : ncpl.sys ( ncpl+5c2b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003d53c2b, The address that the exception occurred at
Arg3: fffff8800e1e82c8, Exception Record Address
Arg4: fffff8800e1e7b30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
ncpl+5c2b
fffff880`03d53c2b 48894108        mov     qword ptr [rcx+8],rax

EXCEPTION_RECORD:  fffff8800e1e82c8 -- (.exr 0xfffff8800e1e82c8)
ExceptionAddress: fffff88003d53c2b (ncpl+0x0000000000005c2b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 00000000baadf015
Attempt to write to address 00000000baadf015

CONTEXT:  fffff8800e1e7b30 -- (.cxr 0xfffff8800e1e7b30)
rax=00000000baadf00d rbx=fffffa800af27c48 rcx=00000000baadf00d
rdx=fffffa800ac778a8 rsi=fffffa800ac778d8 rdi=fffffa800ac778a8
rip=fffff88003d53c2b rsp=fffff8800e1e8508 rbp=0000000000000000
 r8=fffff80002c4c000  r9=0000000000000001 r10=0000fffffffff000
r11=0000058000000000 r12=fffff8a0018e6768 r13=0000000000000000
r14=fffffa800b1d9280 r15=00000000c0000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
ncpl+0x5c2b:
fffff880`03d53c2b 48894108        mov     qword ptr [rcx+8],rax ds:002b:00000000`baadf015=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  00000000baadf015

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef40e0
 00000000baadf015 

FOLLOWUP_IP: 
ncpl+5c2b
fffff880`03d53c2b 48894108        mov     qword ptr [rcx+8],rax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880091718d1 to fffff88003d53c2b

STACK_TEXT:  
fffff880`0e1e8508 fffff880`091718d1 : fffffa80`0af27c48 fffffa80`0ac778d8 00000000`00000000 fffffa80`0444ad00 : ncpl+0x5c2b
fffff880`0e1e8510 fffffa80`0af27c48 : fffffa80`0ac778d8 00000000`00000000 fffffa80`0444ad00 00000000`c0000000 : nccache+0x58d1
fffff880`0e1e8518 fffffa80`0ac778d8 : 00000000`00000000 fffffa80`0444ad00 00000000`c0000000 fffffa80`039b53d8 : 0xfffffa80`0af27c48
fffff880`0e1e8520 00000000`00000000 : fffffa80`0444ad00 00000000`c0000000 fffffa80`039b53d8 fffff8a0`018e6768 : 0xfffffa80`0ac778d8


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ncpl+5c2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ncpl

IMAGE_NAME:  ncpl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b2b905c

STACK_COMMAND:  .cxr 0xfffff8800e1e7b30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_ncpl+5c2b

BUCKET_ID:  X64_0x7E_ncpl+5c2b

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

0: kd> lmvm ncpl
start             end                 module name
fffff880`03d4e000 fffff880`03d5e000   ncpl     T (no symbols)           
    Loaded symbol image file: ncpl.sys
    Image path: \??\C:\Program Files\Novell\Client\XTier\Drivers\ncpl.sys
    Image name: ncpl.sys
    Timestamp:        Fri Dec 18 09:23:24 2009 (4B2B905C)
    CheckSum:         000138CA
    ImageSize:        00010000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
27 Apr 2010   #28
Blackhawk131

 
 

Well this is shocking. Anyway, how could I have gone from a usb2serial driver to a novell driver problem? Does this mean that most drivers are not 100% compat for Win 7? If I remove Novell, what problem is going to appear next?
My System SpecsSystem Spec
27 Apr 2010   #29
Jonathan_King

Windows 7 Professional x64
 
 

You never know. Maybe Novell was the problem in the first place, and it only looked like the other things were the problem. All you can do is try stuff until you find the solution.

Now, I know from previous experiences that tools like Novell can cause BSODs. Therefore, it does not seem unlikely that Novell is the cause.
My System SpecsSystem Spec
Reply

 Blue Screen Crash On Win 7 x86




Thread Tools




Similar help and support threads
Thread Forum
blue screen crash
help me with my blue screen problem
BSOD Help and Support
blue screen crash
it been long time since i had a blue screen crash.
BSOD Help and Support
blue screen crash please help
every couple of days i get there blue screen and i dont know why please tell me how to fix this.. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: 19
BSOD Help and Support
Blue Screen Crash
Computer tells me that. I think it might be the webcam because it's done it since I got the computer back from sony and one of the problems they "fixed" was the webcam. It happens when I use the webcam as well.
BSOD Help and Support
Blue Screen Crash
Hi all, Can you please help with a blue screen issue. It happened under Vista and now I upgraded to Windows7 and it just crashed again. I have a suspision that it has something to do with a USB port but I'm not sure. Thanks!
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 14:11.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App