Win7 BSOD

Joined
Feb 13, 2012
Messages
1
Reaction score
0
I have started getting some BSODs today, I have attached the most recent minidump file. Can someone please read and tell me what the problem is.

Thanks!
 

Attachments

Elmer BeFuddled

Resident eejit
Joined
Jun 12, 2010
Messages
1,050
Reaction score
251
Hi Jared872 and Welcome to The Forum.

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:
Device driver

Your latest dump file lists ahcix64s.sys as the probable cause.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.
Random stop codes can often indicate hardware issues.


As a Priority:

ahcix64s.sys Wed Oct 21 14:40:52 2009 AMD AHCI Compatible RAID Controller. See if there's an update for this?

RTCore64.sys Wed May 25 07:39:12 2005 RivaTuner or EVGA Precision. Has known issues with Windows 7. Uninstall

lmimirr.sys Tue Apr 10 23:32:45 2007
LMIRfsDriver.sys Mon Jul 14 17:26:56 2008
RaInfo.sys Fri Jan 04 18:57:14 2008 LogMeIn/RemotelyAnywhere. Has known issues with Windows 7. Update or Uninstall this software!


Drivers that pre-date Windows 7. Update:

GEARAspiWDM.sys Mon May 18 13:17:04 2009 Gear Software CD-ROM Class Filter Driver v4.019.1 (Oct 2011). Also loads with iTunes


Drivers with Updates:

nusb3xhc.sys Fri Jan 22 03:22:21 2010 Go to your Motherboard Mfr. Support website (or NEC/Renesas) and update your USB 3.0 drivers. A June 2011 set are available Here.


Bugcheck Analysis:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 6, 8, 0}

*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
Probably caused by : ahcix64s.sys ( ahcix64s+4955 )

Followup: MachineOwner
Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.

HTH.
 
Last edited:

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top