Computer shutdown running as server

[tropicaltanning]

Compter is a Sony Vaio PCV-V300G.
Next is what tech at Helio wanted, they have to send off for diagnostic work, this is the results of Marx on the Helios CD:
Report started:
Fri, Jul 29, 2005, at 12:6:6
Report generated by MarxProbe ver 3.0.2.521
Processor architecture synopsis:
Manufacturer: Intel
family = 15, model = 2, stepping = 9
Type: OEM
Processor family ID: 199
Processor name: Intel(R) Pentium(R) 4 CPU 2.80GHz
Clock speed: 2809.00 MHz
System BIOS:
Identifier: AT/AT COMPATIBLE
Date: 07/02/04
Version: ASUS - 42302e31
Ports detected in the system:
RadioShack USB to Serial Cable (COM4) 0...0
Operating system synopsis:
Windows XP (5.1) build: 2600, product type: Workstation service pack ver. 1.0
MARX software analysis:
C:\WINDOWS\System32\mpiwin32.dll, ver. 3.2.3.1124
C:\WINDOWS\System32\cbndll.dll, ver. 2.2.0.1
C:\WINDOWS\system32\drivers\cbusb.sys, ver. 1.2.3.1029, registered. The service is running.
MARX hardware: detected CBU at USB
Firmware version : 1.7
---- Copyright (c) 2001,2002 MARX Datentechnik GmbH;
---- parts Copyright by MARX Software Security AG, Luxembourg
Running Helios 11.3.7

Can't get Helios techs to understand my complete problem. When used as a Helios server my computer shuts down intermittently (we never know when its going to happen) and goes to a blue screen with a counter starting at 1 and rebooting at 99 . Last message I got on the blue screen with alot of other things was Corrupt_Driver_MMPOOL at the top. When removed as a server and made as a client it works perfect. My USB ports being used are a barcode scanner, T Max manager (connected with the radio shack serial to USB adapter) and Helios hardware key. Hardware key in in one set of USB ports on the side of my computer with scanner and t-Max on back side. This was done to try to eliminate a priority to one of the devices always running since the scanner is only use at times. I did tell techs I have the extended warranty on my computer and they said it wasn't Helios problem. Can't send out to diagnose without making it a helios server (they won't send me a key so the computer tech can diagnose)and can't diagnose in house and shut down salon. Already replaced key and updated drivers for the USB ports and key still no luck.
This same hardware key and software installed on a different computer work 100% no problem.
What next.

[jlb1484]

Are your virus definitions up to date? At my real job we had a handfull of PC's get a virus that give's you the blue screen of death and then starts counting down. If not sounds like you have a hardware problem.

[tropicaltanning]

I constantly run norton internet antivirus. I would look into a virus more if I had the problem with the computer running as a client. Only does this as a server.

[jlb1484]

When you say changed from a client to a server. Where exactly are you making that change and why?

[jlb1484]

Nevermind I found the change that you are making. Sorry don't know what to tell you. Hopefully Helios can firgure it out.

[Sunfixer]

Don't know if you got your problem solved, but a quick search online points to a couple things, one that keeps coming up is diabling fast user switching. Also it sounds like a problem with windows and not a hardware problem , if you have the recovery disk from sony you could backup helios and reinstall windows, a bit drastic but if nothing else works it might be your only option.

[TheBeachStop]

Tropicaltanning, I am not familiar with Helios. I run Sun Touch, however, for the sake of discussion, please induldge me.

Sun Touch said they require a server in order to run the app on different desktops. Now, I am an MSCP and MY definition of server and theirs are different. Their definition is where the DB resides. My definition is NT/Server, WINDOWS 2K Server, etc. I just run XP as a client like you run as a client. I just map my other PC on the network to point to the PC that retains the DB for Sun Touch and life is good. Basically the same way you run as a client. I would believe you could run your app. and map another PC to use the DB also.

If Helios in fact requires you to run a true server version, I would seriously reconsider software vendors. Kinda expensive to run a little tanning salon app. May want to ask Helios techs. if it is truly a SERVER based app. or just an app. requiring a PC to house their database!?!

Hope this helps in some way. If it doesn't, sorry for the waste of bytes... Good luck.

[Andy]

It will be an issue related to your USB ports on that system ... if you are running XP Pro SP2 I understand the problem gets worse (thanks Microsoft). If Helios have already had you install the updated SP2 drivers for USB then maybe try adding a USB HUB to the environment and plug the Dongle into the hub (just a shot in the dark) ... see if that helps.

Try all the USB ports (including the ones on the front if any)

[h20skibumn]

Is this your problem???

The DRIVER_CORRUPTED_MMPOOL bug check has a value of 0x000000D0. This indicates that the system attempted to access invalid memory at a process IRQL that was too high.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory referenced
2 IRQL at time of reference
3 0: Read
1: Write

4 Address that referenced memory


Cause
The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.

In most cases, this bug check results if a driver corrupts a large allocation (PAGE_SIZE or larger). Smaller allocations result in bug check 0xC5 (DRIVER_CORRUPTED_EXPOOL).

Resolving the Problem
If you have recently installed any new software, check to see if it is properly installed. Check for updated drivers on the manufacturer's website.

To debug this error, use the special pool option of Driver Verifier. If this fails to reveal the driver that caused the error, use the Global Flags utility to enable the special pool by pool tag.

For information about the special pool, see Driver Verifier.

An alternate method is to open the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentContr olSet\Control\Session Manager\Memory Management registry key. In this key, create or edit the ProtectNonPagedPool value, and set it equal to DWORD 1. Then reboot. Then the system will unmap all freed nonpaged pool. This will prevent drivers from corrupting the pool. (This does not protect the pool from DMA hardware, however.)