Random BSOD, error 0x0000001e

I have a machine that blue screens. No pattern has been identified except that it only does it when plugged into the port replicator. When the user has it at home, there is never a problem.

You'll notice by the minidumps this problem was happening a couple months ago then started again today. The user has been out of the office that whole time. We did not get a chance to fix it back then.

I spent the day upgrading drivers. There is a video card driver update left to do and it's highly possible that is the one. However, out internet comes to a screeching slow in the afternoon.

I've tried using Microsoft's debugging tools but was not getting very far when I ran across your site.

I've attached the zip as indicated in your instruction set for submitting to the BSOD board. The affected machine is a Windows 7 Professional x64 Sony Viao model number VPCZ212GX.

Thanks for all you guys do! Any help is greatly appreciated.
--
Quintin

Code:

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff800034621f0, the pool entry being checked.
Arg3: 0000000000000000, the read back flink freelist value (should be the same as 2).
Arg4: fffff800034621f0, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

Having a check for any solutions now, bear in mind, I am new to BSOD analysis.

Try running Driver Verifier, may need to check for any misconfiguration of drivers:

Driver Verifier - Enable and Disable

Create a Backup and System Restore beforehand.

Thank you for your prompt assistance with this. Unfortunately, I can't just set this driver verifyer and wait for more, and possibly more frequent, BSODs. You see, this is the CEO's laptop and he is already beyond frustrated with it. To subject him to that could constitute career suicide.

If you have any other suggestion, I'm open to them. If not, I completely understand.

I may have to just move on to getting him a replacement and then I can work this one as if it were my own and then run the verifier.

The Driver Verifier would be the best option in this case unfortunately, maybe you should get him a replacement, so we can work on resolving this issue.