Hello, For sometime, I've been experiencing one of the stranger BSODs I've come across. I receive a BAD_POOL_HEADER x19 after using Eclipse. It doesn't always happen - it only appears to happen when working on certain source code files and with certain types of editors within Eclipse. I've reinstalled/upgraded Eclipse and the PHP Developer Tools that I use, and have upgraded/reinstalled the JavaSE, and while it seems to fix it for a while, it always comes back. It's somewhat predictable to reproduce, once a problematic source code file is found. When typing (and especially cutting/pasting code) Eclipse starts to pause, and then suddenly there's the BSOD. Again, only certain files cause it, and if I use a plain-text editor within Eclipse, it doesn't appear to happen. It also appears to build on itself. A few weeks back, it suddenly started happening frequently when working on a handful of files. I had a feeling it was video card related (I have the ATI Radeon HD 5700 with 3 monitors connected) so I completely uninstalled/installed the drivers, directly from ATI's site. It appeared to clear up for a couple of weeks, during which time I also reinstalled Eclipse/Java for an unrelated reason. However recently it's come back - at first when working on a single file, and now more frequently when working on other files. I have 6 minidumps: https://skydrive.live.com/redir.aspx?cid=e6be9afb51fefce4&resid=E6BE9AFB51FEFCE4!155 Three in Oct. prior to the video card reinstall, and three in Nov. now when it's started to happen again. Mind you that in between that time, I've worked on hundreds of source code files within Eclipse, but only now has the BSODs started to happen again. I can provide any additional details (and as I said, can pretty easily recreate the BSOD) and would appreciate someone taking a looking at this. Please let me know what else would be needed. Thank you, Han

Sir, According to your DMP files i got : ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 0000000000000020, a pool block header size is corrupt. Arg2: fffffa8009d23000, The pool entry we were looking for within the page. Arg3: fffffa8009d23410, The next pool entry. Arg4: 0000000004410000, (reserved) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d100 fffffa8009d23000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003008cae to fffff80002edac40 STACK_TEXT: fffff880`03338948 fffff800`03008cae : 00000000`00000019 00000000`00000020 fffffa80`09d23000 fffffa80`09d23410 : nt!KeBugCheckEx fffff880`03338950 fffff880`0710784b : fffffa80`0c09cfb0 fffff880`071078a0 00000000`44424557 00000000`00000000 : nt!ExDeferredFreePool+0x12da fffff880`03338a00 fffffa80`0c09cfb0 : fffff880`071078a0 00000000`44424557 00000000`00000000 00000000`00000000 : wdfsd+0x1984b fffff880`03338a08 fffff880`071078a0 : 00000000`44424557 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0c09cfb0 fffff880`03338a10 00000000`44424557 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0c9de8c0 : wdfsd+0x198a0 fffff880`03338a18 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0c9de8c0 fffff880`070f1e37 : 0x44424557 STACK_COMMAND: kb FOLLOWUP_IP: wdfsd+1984b fffff880`0710784b ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: wdfsd+1984b FOLLOWUP_NAME: MachineOwner MODULE_NAME: wdfsd IMAGE_NAME: wdfsd.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4de80c91 FAILURE_BUCKET_ID: X64_0x19_20_wdfsd+1984b BUCKET_ID: X64_0x19_20_wdfsd+1984b Followup: MachineOwner ------------------------------------------------------------------------------------------------------- --> File (wdfsd.sys) is Responsible for the Blue screen . wdfsd.sys = South River Technologies - VeriSign Time Stamping Services Signer - G2 so try to Update your Driver to the latest Version , it solve your Blue screen. Regards, MCP | MCTS | MCITP

Hi Zaune, Thanks for the dumps, they indicate that two files are at fault: wdfsd.sys & ntoskrnl.exe wdfsd.sys: Is a driver included in your Eclipse software and is signed by South River Technologies (creaters of Eclipse) ntoskrnl.exe: which wdfsd.sys runs inside (so we can discount that as if wdfsd.sys has an issue it will cause ntoskrnl.exe to crash) If you do have an application called Webdrive installed you can try and reinstall it as wdfsd.sys is one of the main system files of this program (http://download.cnet.com/WebDrive/3000-2160_4-10017919.html). It may however also be integrated into Eclipse.If that is the case then I would totally uninstall Eclipse and all it's components restart the machine and then reinstall it. Hope this helps

Thanks all. The new version of Webdrive did cross my mind as the culprit, but because of the screen flickering during the BSOD, I had figured it was a video issue. Eclipse and Webdrive are two different pieces of software. Eclipse is the IDE and Webdrive can mount a SFTP server to make it appear as a drive, so that Eclipse can work with it's files as if they are local. I'm going to contact Webdrive support in regards to why their software is causing this.