Quote: Originally Posted by Jubacca
Please help me!
My 1.5 year old HP laptop is freaking out, and I don't know how to fix it. I have Windows 7 Home Premium, but i dont know how to tell if it is the 64 bit or 32 bit version.
The last couple days my computer has been either randomly shutting down and coming up with a BSOD saying "IRQL not less than equal" or something about a "page in non-paged area" - it happens fast, so I cant really read it too well. It has gotten super bad yesterday and today, as it takes probably 10-12 BSODs before I can actually even get to use the computer for longer than a minute.
I have attached the minidump files from the last two days - I just have no idea what to do.
These crashes point to multiple causes but all are memory exceptions. Usually that is a driver
but memory itself cant yet be ruled out.
1-run memtest to verify your memory
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
2-Update all the old drivers
These are drivers that are way too old and need updating
iirsp.sys 12/13/2005 05:47:54 PM fffff880`015ca000 fffff880`015db000 0x00011000 0x439f418a
nfrd960.sys 6/6/2006 05:11:48 PM fffff880`01714000 fffff880`01724000 0x00010000 0x4485ef94
mdmxsdk.sys 6/19/2006 05:27:26 PM fffff880`02e9e000 fffff880`02ea2280 0x00004280 0x449716be
adpu320.sys 2/27/2007 08:04:15 PM fffff880`0107b000 fffff880`010aa000 0x0002f000 0x45e4c6ff
adpahci.sys 5/1/2007 01:30:09 PM fffff880`01200000 fffff880`01256000 0x00056000 0x46377921
arc.sys 5/24/2007 05:27:55 PM fffff880`0150f000 fffff880`01528000 0x00019000 0x4656035b
SiSRaid2.sys 9/24/2008 02:28:20 PM fffff880`019bb000 fffff880`019c9000 0x0000e000 0x48da86c4
sisraid4.sys 10/1/2008 05:56:04 PM fffff880`019c9000 fffff880`019e1000 0x00018000 0x48e3f1f4
adp94xx.sys 12/5/2008 07:54:42 PM fffff880`01000000 fffff880`0107b000 0x0007b000 0x4939bf42
lsi_fc.sys 12/9/2008 06:46:09 PM fffff880`015db000 fffff880`015fa000 0x0001f000 0x493ef531
arcsas.sys 1/14/2009 03:27:37 PM fffff880`01528000 fffff880`01543000 0x0001b000 0x496e3ca9
ql2300.sys 1/22/2009 07:05:06 PM fffff880`01817000 fffff880`019bb000 0x001a4000 0x4978fba2
vsmraid.sys 1/30/2009 09:18:57 PM fffff880`017ae000 fffff880`017d8000 0x0002a000 0x4983a701
elxstor.sys 2/3/2009 06:52:11 PM fffff880`01543000 fffff880`015ca000 0x00087000 0x4988ca9b
CAX_CNXT.sys 2/13/2009 05:19:32 PM fffff880`080bc000 fffff880`08187000 0x000cb000 0x4995e3e4
CAXHWAZL.sys 2/13/2009 05:20:54 PM fffff880`0806a000 fffff880`080bc000 0x00052000 0x4995e436
CAX_DPV.sys 2/13/2009 05:24:50 PM fffff880`08221000 fffff880`08395000 0x00174000 0x4995e522
stexstor.sys 2/17/2009 07:03:36 PM fffff880`019e1000 fffff880`019eb000 0x0000a000 0x499b4248
amdsbs.sys 3/20/2009 02:36:03 PM fffff880`014bd000 fffff880`01504000 0x00047000 0x49c3e213
iaStorV.sys 4/8/2009 12:57:17 PM fffff880`0125c000 fffff880`0137a000 0x0011e000 0x49dcd76d
lsi_scsi.sys 4/16/2009 06:13:50 PM fffff880`01413000 fffff880`01432000 0x0001f000 0x49e7ad9e
HpqKbFiltr.sys 4/29/2009 09:48:30 AM fffff880`04400000 fffff880`0440c000 0x0000c000 0x49f85aae
XAudio64.sys 4/29/2009 02:21:07 PM fffff880`03db3000 fffff880`03dbb000 0x00008000 0x49f89a93
spldr.sys 5/11/2009 12:56:27 PM fffff880`01f48000 fffff880`01f50000 0x00008000 0x4a0858bb
GEARAspiWDM.sys 5/18/2009 08:17:04 AM fffff880`05bec000 fffff880`05bf9000 0x0000d000 0x4a1151c0
HpSAMD.sys 5/18/2009 07:43:49 PM fffff880`013d5000 fffff880`013ec000 0x00017000 0x4a11f2b5
lsi_sas.sys 5/18/2009 08:20:23 PM fffff880`013ad000 fffff880`013ca000 0x0001d000 0x4a11fb47
lsi_sas2.sys 5/18/2009 08:31:48 PM fffff880`01400000 fffff880`01413000 0x00013000 0x4a11fdf4
megasas.sys 5/18/2009 09:09:46 PM fffff880`01432000 fffff880`0143e000 0x0000c000 0x4a1206da
ql40xx.sys 5/18/2009 09:18:11 PM fffff880`0174f000 fffff880`017ae000 0x0005f000 0x4a1208d3
MegaSR.sys 5/18/2009 09:25:54 PM fffff880`01670000 fffff880`01714000 0x000a4000 0x4a120aa2
amdsata.sys 5/19/2009 01:53:21 PM fffff880`011a4000 fffff880`011c2000 0x0001e000 0x4a12f211
amdxata.sys 5/19/2009 01:56:59 PM fffff880`01504000 fffff880`0150f000 0x0000b000 0x4a12f2eb
nvraid.sys 5/20/2009 02:39:40 AM fffff880`010da000 fffff880`01103000 0x00029000 0x4a13a5ac
nvstor.sys 5/20/2009 02:45:37 AM fffff880`01724000 fffff880`0174f000 0x0002b000 0x4a13a711
Rt64win7.sys 5/22/2009 10:52:30 AM fffff880`04352000 fffff880`0438b000 0x00039000 0x4a16bc2e
IntcHdmi.sys 5/26/2009 07:13:09 AM fffff880`083a4000 fffff880`083cb000 0x00027000 0x4a1bcec5
SynTP.sys 6/18/2009 10:33:58 PM fffff880`0441b000 fffff880`04464000 0x00049000 0x4a3af916
CHDRT64.sys 6/23/2009 07:28:17 PM fffff880`05f1f000 fffff880`05fcb000 0x000ac000 0x4a416511
How To Find Drivers:
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
3- Run Driver verifier to find out which driver is the cause
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.