New
#1
BSOD - Physical Memory Dump
guys, its been about 5 days that i have been receiving physical memory dump errors..
also, this error comes atleast 5 times a day, can any1 help me find a cure or atleast know the problem!
guys, its been about 5 days that i have been receiving physical memory dump errors..
also, this error comes atleast 5 times a day, can any1 help me find a cure or atleast know the problem!
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.
The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
To ensure minidumps are enabled:
Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.
there is no "SMALL MEMORY DUMP (256 KB)"
look at this pic..
btw~ here are the 2 files located in the minidump folder
>> dump files.rar
Memory management caused by dump_wmimmc.sys (Gameguard)
I would remove it and run memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Memory management caused by dump_wmimmc.sys (Gameguard)
I would remove it and run memtest
how to remove this?
leave it running for at least 5 or 6 passes.
what is the meaning of passes?
is it possible this error comes from a certain application? like if i open application A, after 20 mins there will be a BSOD?
is it possible this error comes from a certain application? like if i open application A, after 20 mins there will be a BSOD?
^
so i guess my "that" application is causing this, its been 150 mins. and i havent opened that application, and there is no BSOD yet!