Many BSODs after playing game, DRIVER_IRQL_NOT_LESS_OR_EQUAL etc

Hi,

This is quite an unusual bugcheck:

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C00002E3, {fffff8a00010dfe0, ffffffffc0000189, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Unknown bugcheck code (c00002e3)

STOP 0xC00002E3: ???STATUS_SAM_INIT_FAILURE???
Usual causes: I suspect encryption software or compatibility issues

Please uninstall Mywinlocker, which is encryption software as it maybe
contributing to your crashes.

From your crash log dated 23/05/2013:

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff8a004aa0000, 80000000a172c101, fffff88007b74ed0, b}
Probably caused by : dxgmms1.sys ( dxgmms1!memset+d4 )

Stop message 0x000000BE Descriptive text: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual cause: A device driver attempted to write to read-only memory. This problem can occur during an upgrade, although it is not limited to upgrades.

This driver has not been updated as advised in my previous post.

Code:

atikmpag.sys
Refers to: ATI Video driver 
Dated: Fri Nov 16 19:39:13 2012

http://support.amd.com/us/Pages/AMDSupportHub.aspx
(Update the driver only)

Cheers
Dave

Yeah using the "automatically detect and install" is fine.

To update any future drivers, you can either go directly to the OEM website
or you can try updating drivers from Device Manager
(also if you scroll down the page there are many tutorials on this)
----------------------------------------------------------------------------------------

See if Revo picks up any left over entries for Mywinlocker:

Download and install Revo Uninstaller free from here:
Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Then see if your BSOD'S have stopped?

Cheers

Dave

Hi,

From your logs:

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880012d9911, fffff88002dc46e8, fffff88002dc3f40}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeallocateRecordsComplete+31 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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.

These video drivers show as not being updated yet:

Code:

atikmpag.sys Fri Nov 16 19:39:13 2012
atikmdag.sys Fri Nov 16 20:18:02 2012

Having re-read the thread I see you stated you had issues updating away from the Automatic detection,
so here is the direct link to the driver you need to install:


Download



Please install the Driver only, as in this guide:
http://www.sysnative.com/forums/windows-tips-tricks/668-ati-video-cards-driver-only-installation-procedure.html

This bugcheck also indicates a problem occurred in ntfs.sys, the driver file that allows the system
to read and write to NTFS drives. One possible cause of this bug check is disk corruption.

Please Re-run chkdsk

Also run a HDD test for your drives manufacturer:

http://carrona.org/hddiag.html

Post back any results.

cheers
Dave

Hi,

Are you able to do a System Restore back to before the AMD chipset driver got uninstalled?

Then if successfully restored, forget the driver for now and run the HDD tests.

cheers

Dave