Solved BSOD with a variety of bug check ids at random times.

[JD80]

I am helping a friend repair his laptop and have been getting a bunch of BSODs. The machine is an Acer Extensa 5620 that came with windows xp but hes had another person upgrade it to win7.

I thought initially it was mccaffee av but it keeps doing it. Specifically, I have been getting a lot of IRQL_NOT_LESS_OR_EQUAL, DRIVER_IRQL_NOT_LESS_OR_EQUAL, kERNEL_MODE_EXCEPTION_NOT_HANDLED, DRIVER VERIFIER DETECTED_VIOLATION, UNEXPECTED_KERNEL_MODE_TRAP, and more (as told through bluescreenviewer)

I have already done a memtest but am redoing it, ran a chkdsk, updated the drivers both through windows 7 and independently via the vendors websites. Device manager shows now errors or problems and declares every device and driver to be operating properly. Seems the errors are most common when accessing the web, but that could be coincidence.

I have been contemplating updating the BIOS, but that kinda freaks me out, as it not my machine and don't know that that will solve the problem. Please Please help.

I realize that I haven't posted the minidumps and will tomorrow as soon as the second memtest is done if need be.

 

[koolkat77]

Alright we'll be waiting for the files from the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[JD80]

Thanks man. Much appreciated. The report is uploaded now. It seems there are a couple of drivers according to whocrashed and bluescreenview, most notably directx graphics and the wireless drivers. Thing is, Windows shows its the best driver and both the intel and acer websites are telling me my drivers are up to date and there is nothing available. There is, however, a bios update, but as I mentioned, I want to make sure its necessary cause bios updates freak me out

Thanks for your help again...

 

[koolkat77]

Taking a look now.

 

[JD80]

Oh lord, thank you...

 

[koolkat77]

Do you get BSOD's in safe mode? Start your computer in safe mode - Microsoft Windows Help

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

mdmxsdk.sys Tue Jun 20 03:26:59 2006 (449716A3)
Conexant Modem Diagnostic Interface x86 Driver
Driver Reference Table - mdmxsdk.sys

xaudio.sys Sat Aug 5 06:39:09 2006 (44D3E8AD)
Conexant modem audio driver
Driver Reference Table - xaudio.sys

HSX_CNXT.sys Thu Oct 19 00:08:01 2006 (45366D81)
SoftK56 Modem Driver by Conexant Systems
Driver Reference Table - HSX_CNXT.sys

HSXHWAZL.sys Thu Oct 19 00:08:11 2006 (45366D8B)
SoftK56 Modem Driver by Conexant Systems
Driver Reference Table - HSXHWAZL.sys

HSX_DPV.sys Thu Oct 19 00:09:22 2006 (45366DD2)
SoftK56 Modem Driver by Conexant Systems
Driver Reference Table - HSX_DPV.sys

tifm21.sys Wed May 2 14:51:27 2007 (4638510F)
Texas Instruments PCIxx21/PCIxx12 Integrated FlashMedia Controller
Driver Reference Table - tifm21.sys

netw5v32.sys Thu Mar 26 22:10:37 2009 (49CBA8FD)
Intel Wireless WiFi Link Driver
Driver Reference Table - netw5v32.sys

b57nd60x.sys Sun Apr 26 17:15:34 2009 (49F44256)
Broadcom NetXtreme Gigabit Ethernet NDIS6.0 Driver
Driver Reference Table - b57nd60x.sys

igdkmd32.sys Thu Sep 24 01:18:09 2009 (4ABA7471)
Intel Graphics driver
Driver Reference Table - igdkmd32.sys

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

[FONT="Lucida Console"]Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Sat Jan 18 21:48:32.226 2014 (UTC + 6:00)
System Uptime: 1 days 2:32:02.255
BugCheck A, {56485151, ff, 0, 8288dab9}
Probably caused by : ntkrpamp.exe ( nt!PpmQueryTime+3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Fri Jan 17 04:09:22.512 2014 (UTC + 6:00)
System Uptime: 0 days 0:06:28.541
BugCheck A, {8e7c74cc, ff, 1, 828c8885}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+5bb )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Thu Jan 16 16:15:45.886 2014 (UTC + 6:00)
System Uptime: 0 days 0:15:05.915
BugCheck A, {7f7c74cc, ff, 1, 828c3885}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+5bb )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Thu Jan 16 00:31:04.630 2014 (UTC + 6:00)
System Uptime: 0 days 0:35:48.659
BugCheck A, {1a54, ff, 0, 828cb2dc}
Probably caused by : ntkrpamp.exe ( nt!KiIdleLoop+1c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Tue Jan 14 19:23:08.514 2014 (UTC + 6:00)
System Uptime: 0 days 0:05:54.543
BugCheck A, {8268a654, ff, 0, 828952dc}
Probably caused by : ntkrpamp.exe ( nt!KiIdleLoop+1c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Tue Jan 14 08:24:18.605 2014 (UTC + 6:00)
System Uptime: 0 days 0:14:24.634
BugCheck A, {819700cc, ff, 1, 828c1885}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+5bb )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Sun Jan 12 21:42:23.012 2014 (UTC + 6:00)
System Uptime: 0 days 0:38:50.040
BugCheck 1000008E, {c0000005, 82b5b79a, 8c3b99d8, 0}
Probably caused by : ntkrpamp.exe ( nt!IopCheckDeviceType+17 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Debug session time: Fri Jan 10 20:47:59.171 2014 (UTC + 6:00)
System Uptime: 0 days 0:13:38.200
BugCheck A, {17e5cda5, ff, 0, 82891899}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+5cf )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html


Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Keep us posted.

 

[JD80]

*SOLUTION*

I had a acer extensa 3620 giving random blue screens stating IRQL errors for the most part. This machine had come with XP but was updated to Windows 7. I updated all the drivers, ran memtests, hard drive tests and virus scans but in the end I went to the Acer website, went to support, entered my serial number, downloaded the Bios, ran the EXE file as administrator and rebooted. Immediately following several updates became available, one of which was what I suspected of being the culprit; The card reader. I have yet to encounter another bluescreen and feel this issue has been solved.