BSOD playing wow/skyping, error 1000007e.

[JerryOB]

Recently built a new computer passed 24 hours of prime 95 however today I got this BSOD. Requested files attached below.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC000001D
BCP2: FFFFF8800432FAA6
BCP3: FFFFF8800D02B938
BCP4: FFFFF8800D02B190
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\122312-14180-01.dmp
C:\Users\Jerry\AppData\Local\Temp\WER-22479-0.sysdata.xml

Thanks for your time/help in this matter.

 

[x BlueRobot]

[COLOR="red"]BugCheck 1000007E[/COLOR], {ffffffffc000001d, fffff8800432faa6, fffff8800d02b938, fffff8800d02b190}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR="SandyBrown"][COLOR="Red"]memory_corruption[/COLOR][/COLOR]

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: More Help and Information with Driver Verifier - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.