Please read this and tell me what you think!

I'm putting this in Software section because I think it's software-related.
As I explain the problem, I hope you'll be able to help me and decide the source
of the problem.

I installed an ISDN modem (Siemens SANTIS) with (USB Datakit) on a new computer.
Here are the components of this computer:

Main Board: Asus P945-E
H.D.D: Two Samsung SATA Hard Disks (200 GB each)
Display Adapter: NVidia GeForce 7100GS 128M DDR2 PCI-E
Processor: Intel 3.0GHz (LGA) // I don't remeber full details
RAM: 512 X 2 = 1024MB


Anyway, the installation and configuration went fine and I created the connection after registering with an ISP and everything was cool.

But after I connect to the Internet, the system restarts suddenly, when logging on, I get the "System has recovered from a serious error" message.

http://img73.imageshack.us/img73/1452/errorwp8.gif

Here is the Error Signature:

http://img114.imageshack.us/img114/6886/errorsigtr4.gif

It's not neccesarily after connecting, I may be online for half an hour or more, but in the end, the system will restsart.

when examining the System Error Log, I get the following:

http://img69.imageshack.us/img69/953/1003uy9.gif

I sent the report to Microsoft but I didn't find something useful in the related topics that they suggested.

Anyway, is this a driver problem? The CD that came with the Modem doesn't have XP drivers, so I installed Windows 2000 drivers, is this the problem?

Is it a security issue? The system doesn't have the latest security patches and hotfixes that Microsoft publishes.

Please tell me what you think as soon as possible.


Amjad!

 

If the above links don't fix the problem, I'd go to the Siemens (or whoever) web site and find an XP driver or check out the tech support pages and/or the FAQ's. It could very well be a driver problem...

hd2k

 

post the memory dump created in C:\windows\minidump.

I can debug it and see what the culprit is most likely.

Or if you wish to find out yourself:

http://forums.majorgeeks.com/showthread.php?t=35246

Im on a mac today, so it will be a while before I can get to it.

Even without looking at it, I am pretty sure its the driver you installed.

Very few 2000 drivers ever worked properly on XP.

 

Thanks for the links, but they won't apply here.

This isnt happening because of an upgrade, and the first problem was fixed with SP1.

 

Thank you for your suggestions, but as Adrynalyne mentioned, they didn't help me, the problem is more complicated than the situations mentioned in the KB articles.

 

Thank you very much for your effort. I hope the problem is like you said, in the drivers. I don't have access to that computer right now, so I'll try to post the dump in the coming hours. Even if I was able to debug it myself, but I'll need your opinion.

I'm reading now your valuable article about debugging memory dumps, thanks for the valuable information.

Anyway, I did some search and got a file from driverguide.com saying it is an update for Siemens Santis ISDN Modem, so that it will work with XP.
Here's the link:
http://members.driverguide.com/driver/detail.php?driverid=544230

So, should I update the driver before examining the dump?

 

Well, it certainly can't hurt. Remove the old driver first, and upgrade. If it takes care of it, then problem solved.

The debugging tool is incredibly handy; so if you want to play with it anyway...

Make sure you zip any dump you attach.

 

In the description of the driver, they're saying that old drivers should be present, so that they'd be updated. This means that I shouldn't remove them, doesn't it?

should I use the "Update Driver" button instead?

 

Hi Adrynalyne!
I'm sorry for being such a demanding person, but please can you look at this file while I get the file for the computer we're talking about?

This dump is generated by a computer that keeps restarting (the same problem), it sometimes displays blue screen (before Windows XP starts), snd sometimes it starts normally, logs on to the account, and then restarts.

I think it's the hard disk, but I'm not sure.

I hope you'll be able to diagnose the problem by analyzing the dump file.

Thanks!

 

Program Compatibility Wizard? Just a thought, should be in Accessories, I doubt it will help but... Update Windows for sure.

 

Never, EVER use the wizard for drivers.

Quickest way to destroy your OS.

 

Got any other dumps? believe it or not, this wasnt caused by the modem, it was your video card driver.







Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\Mini052607-02\Mini052607-02.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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sat May 26 05:51:07.221 2007 (GMT-7)
System Uptime: 0 days 0:00:14.791
Loading Kernel Symbols
....................................................................................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image nv4_mini.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f94c8e92, f9c512ec, 0}
Probably caused by : nv4_mini.sys ( nv4_mini+34e92 )
Followup: MachineOwner
---------
kd> !analyize -v
No export analyize found
kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: f94c8e92, The address that the exception occurred at
Arg3: f9c512ec, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nv4_mini+34e92
f94c8e92 8b8104030000 mov eax,[ecx+0x304]
TRAP_FRAME: f9c512ec -- (.trap fffffffff9c512ec)
ErrCode = 00000000
eax=00000004 ebx=f9c51574 ecx=05e00558 edx=81a2c350 esi=00000000 edi=00000080
eip=f94c8e92 esp=f9c51360 ebp=81930000 iopl=0 vif nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00090293
nv4_mini+0x34e92:
f94c8e92 8b8104030000 mov eax,[ecx+0x304] ds:0023:05e0085c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 81a749e0 to f94c8e92
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
81930000 81a749e0 81930000 f97ea5c0 81930034 nv4_mini+0x34e92
81930004 81930000 f97ea5c0 81930034 81930044 0x81a749e0
81930008 f97ea5c0 81930034 81930044 00000000 0x81930000
8193000c 81930034 81930044 00000000 00000000 nv4_mini+0x3565c0
81930010 81930044 00000000 00000000 03110148 0x81930034
81930034 04000000 00000002 03fcffff 00000001 0x81930044
81930038 00000000 03fcffff 00000001 00000001 0x4000000

STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nv4_mini+34e92
f94c8e92 8b8104030000 mov eax,[ecx+0x304]
FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nv4_mini+34e92
MODULE_NAME: nv4_mini
IMAGE_NAME: nv4_mini.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4410cb0a
FAILURE_BUCKET_ID: 0x8E_nv4_mini+34e92
BUCKET_ID: 0x8E_nv4_mini+34e92
Followup: MachineOwner
---------

 

THANK YOU very much, Adrynalyne!
The dump file I attached wasn't from the computer with the ISDN modem, because till this moment, I can't get my hands on that computer (geographical reasons)

Anyway, while I get that dump, I'm really surprised to know that the problem of the "second" computer is video card driver!

Listen up, I'm sending an older dump, which was created two days ago, when the problem started to appear, I hope you could confirm that it is a video card driver.

Highly appreciated!

Amjad!

 

Here are other dumps...

 

Both of these read as

Could not read faulting driver name
Probably caused by : win32k.sys

However, win32k.sys is rarely the problem, instead its another driver usually. I'd still bank on the video driver being an issue.

 

OK!

At last, here are the dumps from the computer with ISDN problem.

By the way, the update didn't work, I mean it didn't accept to be updated because "some components were messing".

 

Sorry!
Here are the files.

 

Try again

 

OK!
Here are three dumps.
Two dumps are still to come...

I'm putting 5 to make sure the analysis is 100% accurate...

C'mon Adrynalyne, I'm counting on you...

Thanks!

 

The other two dumps...

I hope the problem is in the ISDN driver...

At least I'll know where to start...

 

Probably caused by : capifw.sys
Probably caused by : ndiswan.sys

First one is your modem driver.
Second one is a Microsoft networking driver, but its used in conjunction with the modem driver I'm sure. The modem is still the culprit.

 

Thank you my friend!
Not only did I get help from you, but I also got new information.

Anyway, you won't believe what happened with me, I've been searching for XP drivers for 3 days without finding one.

The full name of the modem is:
SANTIS USB Datakit S1610-Z2000-B10-1

The closest XP update I could find:
SANTIS USB Datakit S1610-Z2000-C10-s

I've tried to locate it in siemens.com or siemens.ch or even usa.siemens.com but I wasn't lucky.

What do you recommend?

 

Or should I put it in the Drivers thread?

OK, I'll post a request there, hopefully I'll find some help.


Thank you all my friends!

 

Hi folks!

Siemens has replied me and after a few e-mail they sent me the XP drivers.

Thank you all for your help!

Love from Amjad!

 

Awesome.