Memory Management BSOD right after plugging in new external HDD

stg mate to be absolutely honest some of the dump stuff might as well be in Klingon so anything above the absolutely obvious I am really at a disadvantage but if you like I can ask some who are far more informed than me.
Now the only reason I suggested reformatting was because I quite pedantic in what I do and that is would have wiped that drive clean by that I mean the entire disk which would include the partition which I am guessing that WD stuff is installed in and just reformatted it as a plain drive, with no extraneous software to be found. Because as I said before I find it (software) rather irritating and of little use to be honest a bit like bloat ware one gets with store bought machines.
Having said that I know most drives come with some form of control functions / features that take some space up but I take it as just that and not some performance enhancing ware.
Let me know if you want some more opinions mate it is no trouble.

I also don't believe in these add on programs with a new hard drive.
A new hard drive should for just fine with nothing on them form the start.
You never know what is on a new hard drive when you get it.
Any thing could of been installed on the hard drive in its travels from the manufacture to you.
Doing this would make sure your hard drive is clean and fresh before you start using it.

By Brink:
Disk - Clean and Clean All with Diskpart Command

By Bare Foot Kid:
Secure Erase / Wipe : Definition and Methods

I agree with Layback and another one yo can try if you want and it is a but quicker than the clean all stuff is the drive wipe in Partition Wizard http://www.partitionwizard.com/free-partition-manager.html

Pic is just for example make sure the disk is the one you want wiped

Hey guys :) .
I think that the problem is a driver, the telltale signs are also in the dump.

stg07 said:

After I've finished upgrading to the latest version of Western Digital SmartWare, I plugged in my new external HDD. A memory management BSOD appeared immediately.

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80008fa0f0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Code:

2: kd> dt nt!_MMPFN fffffa80008fa0f0
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`400002f0 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`400002f0 Void
   +0x010 Lock             : 0n1073742576
   +0x010 PteLong          : 0xfffff6fb`400002f0
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : 0xffff
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

I would suggest enabling Driver Verifier to help pinpoint the culprit.

Please enable driver verifier
following this TUTORIAL | But using these settings:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
7. Select "Finish" on the next page.

Keep us posted :) .

Hi and thanks for the update seemingly removing the HDD software was the solution
as two days of normal usage with Verifier enabled didn't yield a crash :) .
You can disable verifier now, Driver Verifier - Enable and Disable.

As for your question.

IRP logging and Force Pending I/O are "not suitable" for what we are doing and because it forces
drivers to behave in such a way they weren't developed or intended for.

IRP Logging, takes a great toll on the system and doesn't help us as we are dealing with post-mortem
dump files. IRP logging is a very useful option during a live debug that involves attaching
the said sick machine to an external PC.

Force pending I/O is as I briefly mentioned earlier, "because it forces
drivers to behave in such a way they weren't developed or intended for."
Which most often than not will flag false positives.

"Unknown" drivers are usually the the drivers related to ACPI and the crash dump itself.One example is dump_iaStor.sys.
ACPI = Advanced Configuration and Power Interface.

The Macrovision driver is secdrv.SYS, present in all Windows installations (I believe since Windows XP).
I'm not exactly what it's job is but I think it handles privileges and similar security concerns in Windows.

I hope this helps :).

Hmm YoYo I had it in the back of my mind too about that "software" these drive people put on I nearly always delete the rotten stuff unless one thinks it is something used for controlling the device . I don't like stuff like Bloggs drive utilities, performance enhancing stuff etc etc:)

You were right on it since the beginning :) , which is one reason I didn't interject myself to drive the ball home until you posted for more assistance .
I too very much dislike unnecessary software.