MS Vista Troubles

[JaseVaughn]

Here is the nitty gritty.

I have recently upgraded my Asus A8N-E motherboard to have 4 Gigs of Ram 3 Corsair and 1 Kingston 1 Gig Sticks 3-3-3-8 DDR400 Mhz Now with 4 Gigs Windows Vista 32 Bit can only see 3 Gigs on my system and I know why that is already. When working in Vista Enterprise Edition I can be doing something and get a blue screen Memory_Management Error and this is annoying as XP Pro 32 Bit didn't do this. Attached is the dump file that was generated. I will tell you what I have tried so far. I have Ran the Windows Vista Memory Test Tool and Memtest 1.70 the newest Version and all 4 Gigs came back fine with no problem. That was the first thing done. Next I tried installing a diff O.S. just to make sure something hasn't gone crazy it worked fine. I have now just recently tried turning off a setting in the motherboard that allows "A 32 Bit OS to use PAE to see the 4 Gigs" which doesn't work anyway and I am not sure if maybe that trigger these events those settings turned on inthe bios since I do have 4 gigs. and So far it's running ok so if that's it GREAT but I dunno I want another opinion.

DUMP FILE

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00061940, A PDE has been unexpectedly invalidated.
Arg2: 00001000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_61940

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_RC

PROCESS_NAME: wmplayer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8182e27b to 818d85c9

STACK_TEXT:
98b7fae0 8182e27b 0000001a 00061940 00001000 nt!KeBugCheckEx+0x1e
98b7fb04 8182e30a 00001201 00000179 00000179 nt!MiExchangeWsle+0x51
98b7fb20 8182b94d 00000179 00001201 00000000 nt!MiSwapWslEntries+0x56
98b7fb54 8182ab37 98b7fb7c 75d22000 84d596c8 nt!MiUpdateWsle+0x170
98b7fb8c 818ae526 c03ae910 835d1e34 00000000 nt!MiAllocateWsle+0x167
98b7fbc4 818ae05c 00000000 84d596c8 75d22374 nt!MiCompleteProtoPteFault+0x1cd
98b7fc08 8182a351 00000000 75d22374 c03ae910 nt!MiResolveProtoPteFault+0x1c8
98b7fcd0 818abe92 75d22374 8d69bcb0 00000000 nt!MiDispatchFault+0x989
98b7fd4c 8188fa74 00000000 75d22374 00000001 nt!MmAccessFault+0x20a0
98b7fd4c 77bdc441 00000000 75d22374 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
039edef0 00000000 00000000 00000000 00000000 0x77bdc441


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiExchangeWsle+51
8182e27b cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiExchangeWsle+51

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4549ae00

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_61940_nt!MiExchangeWsle+51

BUCKET_ID: 0x1a_61940_nt!MiExchangeWsle+51

Followup: MachineOwner
---------

 

[Raffaz]

Have you tried removing your extra stick of RAM, hows it run if you do?

 

[~mr mixx~]

I know that sometimes when running two different types of ram in the same computer results in a conflict...sometimes the computer wont bootup at all. So it's good practice to keep all the ram sticks the same company.