Windows 8 BSOD Citing Memory_Management

arhartm58

New Member
Joined
Dec 29, 2012
For Christmas I rebuilt my computer and since I am a college student and qualify for Dreamspark, formally known as MSDN Academic Alliance, I had access to a free copy of Windows 8 Pro I decided to take the great leap forward.

Build went smoothly, no problems until today when I had two BSODs within minutes of each other. The first while playing Bastion, and the second time while watching a youtube video. In both cases memory_management was cited.

All the requested files are attached, thank you for the assistance!
 

Attachments

  • W7F_29-12-2012.zip
    459.5 KB · Views: 1,056
  • CPU-Z.png
    CPU-Z.png
    160.6 KB · Views: 542
  • RAMMon - SPD Info.txt
    29.2 KB · Views: 298
Just an update, I've had two more BSODs. I've attached the .dmps.

In addition, I'm having web pages and programs randomly crash.
 

Attachments

  • 122912-14687-01.dmp
    277.5 KB · Views: 346
  • 122912-15671-01.dmp
    277.5 KB · Views: 326
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 50, {fffff680403b2850, 0, fffff8038106ea73, 2}




Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+134 )


Followup: MachineOwner

Please run memtest to check for RAM errors:
Memtest86+ - Advanced Memory Diagnostic Tool
Run for 7/8 passes and on one stick at a time so errors aren't confused.

Checking your moBo's manufacturer's page I notice you have bios updates.
Also please update the following:

Broadcom Lan driver: ASRock > Z77 Extreme4

Realtek HiDef driver: Realtek

You also have running a Xconnex or ViXs network hub or similar? I notice the drivers are from 2008 and really should be updated if possible.
 
Back
Top Bottom