Hi,
Results verified by WinDBG, DumpCHK, and BlueScreenView.
The Bug_Check were 0A, 1A, 34, 3B, 50, and DE.
**When there are that many different Bug_Check hardware is almost always involved.**Common CAUSE of those is memory_corruption so check the memory very thoroughly.
0A CAUSE memory_corruption.
BugCheck A, {fffffa802bee8180, 2, 1, fffff80002b90fe6}
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
1A CAUSE ntkrnlmp.exe which is a Windows component which means something else
drove it into Fault.
BugCheck 1A, {41284, fffff9800b1bd001, 0, fffff780c0000000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
IMAGE_NAME: ntkrnlmp.exe
34 CAUSE memory_corruption.
BugCheck 34, {50853, fffff88006a4d508, fffff88006a4cd60, fffff800028a07b1}
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+d1 )
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x34_nt!MmUnmapViewInSystemCache+d1
BUCKET_ID: X64_0x34_nt!MmUnmapViewInSystemCache+d1
3B CAUSE ntkrnlmp.exe which is a Windows component which means something else
drove it into Fault.
BugCheck 3B, {c0000005, fffff80002c07007, fffff8800b30be80, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+277 )
IMAGE_NAME: ntkrnlmp.exe
50 CAUSE memory_corruption.
BugCheck 50, {fffffa846d30281b, 0, fffff80002a834cf, 5}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+425
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+425
DE CAUSE ntkrnlmp.exe which is a Windows component which means something else
drove it into Fault.
BugCheck DE, {2, fffff8a00a78d550, fffff8a00bc12d41, 180948c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d8a1 )
IMAGE_NAME: ntkrnlmp.exe
1. Check the memory very thoroughly using the methods in the troubleshooters below.
2. Check with ASUStek Support, their on-line documentation and drivers, and ask in their forums
for knowns issuyes. Check ASUStek for updates to BIOS, low level chipset drivers, and the
major on-board drivers. Also check for updates to the major separate device drivers - run
DriverView - set VIEW to Hide Microsoft drivers - update those without Dump in their name.
BiosVersion = 1701
BiosReleaseDate = 09/19/2011 <- BIOS is very current however there may be newer versions.
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = Rampage II GENE
BaseBoardVersion = Rev 2.xx
ASUStek Support
http://support.asus.com/
ASUStek Forums
http://vip.asus.com/forum/default.aspx?SLanguage=en-us
ASUStek Drivers
http://support.asus.com/download/download.aspx?SLanguage=en-us
3. Use the other methods in the troubleshooters below.
==================================================================
To see how to use BlueScreenView and MyEventViewer to troubleshoot Bluescreens see the
methods indicated in this thread - top 3 answers (+1 other).
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990
==================================================================
BCCode: 0A 0x0000000A
Check these KB's
Error message on a blue screen on a computer that is running Windows 7 or Windows Server
2008 R2: "STOP: 0x0000000A"
http://support.microsoft.com/kb/979444
Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2 and
that has iSCSI storage: "0x0000000A"
http://support.microsoft.com/kb/979711
Those and 5 other KB Articles are available
http://support.microsoft.com/search/default.aspx?mode=a&query=0x0000000A&spid=14019&catalog=LCID%3D1033&1033comm=1&res=10
BCCode: 0A 0x0000000A
Drivers could be at fault however disk issues or antivirus/antispyware/security products are
just as likely to be the root cause as they can force a driver to corrupt or go out of bounds.
The video driver or something affecting it would be very suspect.
Be sure the drivers, BIOS, and low level chipset drivers are all updated by manually checking
at the System maker and device makers's sites.
Below I will post a generic bluescreen troubleshooter and in the next message how to update
drivers and BIOS as well as do memory checks.
BCCode: 0A 0x0000000A
Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Resolving the Problem
If a kernel debugger is available, obtain a stack trace.
To resolve an error caused by a faulty device driver, system service, or BIOS
- Restart your computer.
- Press F8 at the character-based menu that displays the operating system choices.
- Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool
- Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
- Try disabling memory caching of the BIOS.
- Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
- Make sure the latest Service Pack is installed.
- If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming
proper termination.
- For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.
If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.
Comments
Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.
BCCode: 0A 0x0000000A <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/IRQL-NOT-LESS-OR-EQUAL-0x0000000A-\*1025.html
==================================================================
BCCode: 1a 0x0000001aRemove ALL power and reseat all cards, memory, and cables (both ends when possible) -
actually remove and replace - do not just snug. Make sure the vents are clear and that the
fans are working. Even though the temp is OK do not assume heat can't affect the video,
sound or other system functions it those get to hot. Try adding a small fan blowing into
the vents as a test. (Those are mostly for a PC not a laptop.)
Have you added any hardware lately? Have you updated any driver just before these started?
(Check Control Panel - Windows Updates to see if any drivers were updated there about the
time this started) Main likely culprits are Video driver, other major drivers, memory, and
antivirus/antispyware/security products could be at fault as well as drive issues.
Use the troubleshooter below and refer to the next message for drivers and memory when
you get to those sections and then return back to the troubleshooter as needed.
BCCode: 1a 0x0000001a <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/MEMORY-MANAGEMENT-0x0000001A-\*1041.html?order=votes
==================================================================
BCCode: 34 0x00000034The most common cause of this Bug_Check is lack of System Memory. Possibly some of the system
memory is not being recognized - such as 4 GB showing as 3 GB as 2 GB or 2 GB as 1 GB and other
possible combinations. Added there could be memory controller and other hardware issues which
are affecting the memory pool. If you just do not have much memory then you will need to add more
or replace some as a test.
Bug Check 0x34: CACHE_MANAGER
The CACHE_MANAGER bug check has a value of 0x00000034. This indicates that a problem occurred in the file system's cache manager.
Important Information If You Have Received a STOP CodeIf you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer,
call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer Contact
Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue
Screen) Errors in Windows.
The following actions might prevent an error like this from happening again:
1.Download and install updates and device drivers for your computer from Windows Update.
2.Scan your computer for computer viruses.
3.Check your hard disk for errors.
CACHE_MANAGER ParametersThe following parameters are displayed on the blue screen.
Parameter Description
1 Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. The low 16 bits identify the source line in the file where the bug check occurred.
2, 3, & 4 Reserved
Cause
One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low,
another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Resolution
To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.
BCCode: 34 0x00000034 <-- read this linkhttp://www.faultwire.com/solutions-fatal_error/CACHE-MANAGER-0x00000034-*1067.html
==================================================================
BCCode: 3b 0x0000003bBug Check 0x3B: SYSTEM_SERVICE_EXCEPTIONTry removing and reseating all cards, memory, and cables (both ends when possible) - actually
remove and replace - do not just snug (on a PC) and clean out the dust bunnies and vents. On
a laptop about all that can be done is reseat the memory and clean the vents. (Of course remove
ALL power prior to opening the case.)
3b is usually a graphic's driver (display adapter/video driver), other possibilities includebut are not limited to antivirus/antispyware/security programs and even memory (mapping).BCCode: 3b 0x0000003bCause
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
BCCode: 3b 0x0000003b <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/SYSTEM-SERVICE-EXCEPTION-0x0000003B-\*1074.html
==================================================================
**BCCode: 50 0x00000050References to Vista also apply to Windows 7.**Have you added any hardware lately? Have you updated any driver just before these started? (Check
Control Panel - Windows Updates to see if any drivers were updated there about the time this started)
Main likely culprits are Video driver, other major drivers, memory, and antivirus/antispyware/security
products could be at fault as well as drive issues.
Use the troubleshooter below and refer to the next message for drivers and memory when you get to
those sections and then return back to the troubleshooter as needed.
BCCode: 50 0x00000050
Cause
The BCCode 50 usually occurs after the installation of faulty hardware or in the event of failure
of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or
video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
Resolving the Problem
Resolving a faulty hardware problem: If hardware has been added to the system recently,
remove it to see if the error recurs. If existing hardware has failed, remove or replace
the faulty component. You should run hardware diagnostics supplied by the system manufacturer.
For details on these procedures, see the owner's manual for your computer.
Resolving a faulty system service problem: Disable the service and confirm that this
resolves the error. If so, contact the manufacturer of the system service about a possible
update. If the error occurs during system startup, restart your computer, and press F8 at
the character-mode menu that displays the operating system choices. At the resulting
Windows Advanced Options menu, choose theLast Known Good Configuration option.
This option is most effective when only one driver or service is added at a time.
Resolving an antivirus software problem: Disable the program and confirm that this resolves
the error. If it does, contact the manufacturer of the program about a possible update.
Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk
errors. You must restart the system before the disk scan begins on a system partition. If
the hard disk is SCSI, check for problems between the SCSI controller and the disk.
Finally, check the System Log in Event Viewer for additional error messages that might help
pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS
might also resolve it.
BCCode: 50 0x00000050 <-- read this link
http://www.faultwire.com/solutions-fatal\_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-\*1095.html?order=votes
==================================================================
BCCode: DE 0x000000DEThis is usually a driver issue so run DriverVerifier and check the drivers using the methods
in the troubleshooters below. Also thoroughly check the memory using the methods below.
BCCode: DE 0x000000DE Bug Check 0xDE: POOL_CORRUPTION_IN_FILE_AREA
The POOL_CORRUPTION_IN_FILE_AREA bug check has a value of 0x000000DE. This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
Important Information If You Have Received a STOP Code
If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer,
call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer,
Contact Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article
Resolving STOP (Blue Screen) Errors in Windows.
The following actions might prevent an error like this from happening again:
- Download and install updates and device drivers for your computer from Windows Update.
- Scan your computer for computer viruses.
- Check your hard disk for errors.
POOL_CORRUPTION_IN_FILE_AREA Parameters
None
Cause
When the Memory Manager dereferenced the file, it discovered this corruption in pool memory.
BCCode: DE 0x000000DE <-- read this linkhttp://www.faultwire.com/solutions-fatal_error/A-driver-corrupted-pool-memory-used-for-holding-pages-0x000000DE-*1221.html
==================================================================
Look in the Event Viewer to see if anything is reported about those.
http://www.computerperformance.co.uk/vista/vista\_event\_viewer.htm
MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.
http://www.nirsoft.net/utils/my\_event\_viewer.html
Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info
that would help. Such as the BCC and the other 4 entries on the lower left. And any other error
information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.
As examples :
BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002
or in this format :
Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000
This is an excellent tool for posting Blue Screen Error InformationBlueScreenView scans all your minidump files created during 'blue screen of death'crashes, and displays the information about all crashes in one table - Freehttp://www.nirsoft.net/utils/blue\_screen\_view.html
Many BlueScreens are caused by old or corrupted drivers, especially video drivers however
there are other causes.
You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or
Recovery Options if your system has that installed by the maker.
How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html
You can try a System Restore back to a point before the problem started if there is one.
How to Do a System Restore in Windows 7
http://www.sevenforums.com/tutorials/700-system-restore.html
Start - type this in Search Box -> COMMAND find at top and RIGHT CLICK - RUN AS ADMIN
Enter this at the prompt - sfc /scannow
How to Repair Windows 7 System Files with System File Checker
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log (and Windows 7)
http://support.microsoft.com/kb/928228
The log might give you the answer if there was a corrupted driver. (Does not tell all the possible
driver issues).
Also run CheckDisk so we can rule out corruption as much as possible.
How to Run Check Disk at Startup in Windows 7
http://www.sevenforums.com/tutorials/433-disk-check.html
Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.
Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm
Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
is preferred to ensure the latest drivers from System maker and Device makers are found)
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html
Stop Windows 7 from Automatically Installing Device Drivers
http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/
How To Disable Automatic Driver Installation In Windows 7 / Vista
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for Professional,
Ultimate, and Enterprise)
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
unexpectedly
http://support.microsoft.com/kb/958233
Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)
http://www.chicagotech.net/vista/vistabluescreen.htm
Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692
Windows - Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033
In some cases this might be required.
StartUp Repair from Recovery Options or Windows 7 disk
How to Run a Startup Repair in Windows 7
http://www.sevenforums.com/tutorials/681-startup-repair.html
How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html
How to Create a Windows 7 System Repair Disc
http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html
How to Do a Repair Install to Fix Windows 7
http://www.sevenforums.com/tutorials/3413-repair-install.html
Hope this helps.
Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.