locked
Dell Desktop with BSOD issues RRS feed

  • Question

  • Windows 7 Pro

    i5 Dell Desktop couple years old

    I've been trying to figure out this issue. I've used driver verifier but it's still doing it. It BSOD intermittently. Sometimes twice a day and sometimes it goes for weeks with nothing. A constant player is ntkrnlpa.exe with other sometimes partners being aswSnx.sys (completely removed avast and installed latest version), halmacpi.dll, iaStor.sys (might be avast, removed it completely). Mostly it's just ntkrnlpa.exe though. I've ran memtest on it with no errors as well as the Dell checks. I'm thinking it may be something hardware that heats up at random times and causes a glitch.

    I've got several dmp files loaded in BlueScreenView

    <title>Crash List</title>

    Crash List


    Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time
    030514-16146-01.dmp 3/5/2014 12:47:25 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x094ae708 0x00000002 0x00000000 0x8bef2e28 NETIO.SYS NETIO.SYS+4e28         32-bit ntkrnlpa.exe+40b7f NETIO.SYS+4e28 NETIO.SYS+89d4 NETIO.SYS+8a4a   C:\Users\Walter\Desktop\bsod-arden\030514-16146-01.dmp 4 15 7601 159,920 3/5/2014 2:33:48 PM
    031814-14679-01.dmp 3/18/2014 4:08:54 PM DRIVER_CORRUPTED_EXPOOL 0x000000c5 0x09e8e284 0x00000002 0x00000001 0x833674c1 ntkrnlpa.exe ntkrnlpa.exe+40b7f         32-bit ntkrnlpa.exe+40b7f ntkrnlpa.exe+1204c1 iaStor.sys+20736 iaStor.sys+1fc2c   C:\Users\Walter\Desktop\bsod-arden\031814-14679-01.dmp 4 15 7601 159,968 3/18/2014 4:17:02 PM
    031914-12573-01.dmp 3/19/2014 11:42:29 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x83288415 0xabf03aac 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+41415         32-bit ntkrnlpa.exe+41415         C:\Users\Walter\Desktop\bsod-arden\031914-12573-01.dmp 4 15 7601 159,920 3/19/2014 12:13:16 PM
    031914-13416-01.dmp 3/18/2014 7:02:55 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e 0xc0000005 0x8329ebe4 0x8df9371c 0x8df93300 ntkrnlpa.exe ntkrnlpa.exe+9ebe4         32-bit ntkrnlpa.exe+9ebe4 ntkrnlpa.exe+19ccfd ntkrnlpa.exe+19d16a ntkrnlpa.exe+19cb49   C:\Users\Walter\Desktop\bsod-arden\031914-13416-01.dmp 4 15 7601 159,968 3/19/2014 12:13:16 PM
    041014-20186-01.dmp 4/10/2014 8:48:29 AM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x8347d415 0xa436baac 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+41415         32-bit ntkrnlpa.exe+41415         C:\Users\Walter\Desktop\bsod-arden\041014-20186-01.dmp 4 15 7601 159,920 4/21/2014 1:46:00 PM
    041014-53071-01.dmp 4/10/2014 12:54:39 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x834acc27 0xa141bc34 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+9ec27         32-bit ntkrnlpa.exe+9ec27 ntkrnlpa.exe+265a0f ntkrnlpa.exe+3d8c6     C:\Users\Walter\Desktop\bsod-arden\041014-53071-01.dmp 4 15 7601 159,968 4/21/2014 1:46:00 PM
    042114-26598-01.dmp 4/21/2014 12:58:13 PM DRIVER_CORRUPTED_EXPOOL 0x000000c5 0x00000004 0x00000002 0x00000001 0x835594c1 ntkrnlpa.exe ntkrnlpa.exe+40b7f         32-bit ntkrnlpa.exe+40b7f ntkrnlpa.exe+1204c1 ntkrnlpa.exe+2256e8 ntkrnlpa.exe+22553c   C:\Users\Walter\Desktop\bsod-arden\042114-26598-01.dmp 4 15 7601 159,920 4/21/2014 1:46:00 PM
    042314-17128-01.dmp 4/23/2014 2:11:18 AM DRIVER_CORRUPTED_EXPOOL 0x000000c5 0x4459454f 0x00000002 0x00000001 0x835614c1 ntkrnlpa.exe ntkrnlpa.exe+40b7f         32-bit ntkrnlpa.exe+40b7f ntkrnlpa.exe+1204c1 ntkrnlpa.exe+249ebf ntkrnlpa.exe+246fca   C:\Users\Walter\Desktop\bsod-arden\042314-17128-01.dmp 4 15 7601 159,920 4/23/2014 9:16:47 AM
    <title>Crash List</title>

    Crash List


    Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path
    ntkrnlpa.exe ntkrnlpa.exe+1204c1 0x83441000 0x83854000 0x00413000 0x521e9cb6 8/28/2013 5:58:30 PM          
    Wednesday, April 23, 2014 4:55 PM

Answers

  • GF

    4 different error codes relating to memory corruption.  Please run verifier


    Please run this test to find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.


    Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Thursday, May 8, 2014 6:46 PM
    Wednesday, April 23, 2014 6:25 PM

All replies

  • We do need the actual DMP file as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask

    If you are using Blue screen view, who crashed, or a similar application, don't.  They are wrong at least as often as they are correct

    Wanikiya and Dyami--Team Zigzag

    Wednesday, April 23, 2014 5:31 PM
  • Hope I did this right. Uploaded it to our webserver:

    http://64.142.127.158/bsod-arden.zip

    Wednesday, April 23, 2014 6:10 PM
  • GF

    4 different error codes relating to memory corruption.  Please run verifier


    Please run this test to find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.


    Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Thursday, May 8, 2014 6:46 PM
    Wednesday, April 23, 2014 6:25 PM
  • Verifier is currently running on all but MS drivers. I did do another BSOD after setting it up, but didn't produce a crash report. I should go check the settings. I think I just set everything on the first page. Verifier was enabled for several of these crashes, probably the 3/18-3/19 ones, but didn't seem to give any more clue.

    Wednesday, April 23, 2014 6:32 PM
  • GF

    I checked all the DMP files from April 21-April 23 and none were with verifier enabled.  You can check to see that it is by typing verifier /query from an elevated command prompt.  It should yield a list of drivers (we dont care witch atm)  You can change the drivers being examined to all, but this will slow the computer down a bit.

    On more detailed examination 2 of the 5 I examined were blames on Avast.  I would remove it and use the built in defender at least until the problem is resolved.


    Wanikiya and Dyami--Team Zigzag

    Wednesday, April 23, 2014 7:22 PM
  • I uninstalled Avast. Rebooted. Downloaded the avast clean remover from their webiste. Ran it, it went to safe mode, ran and then rebooted again. Should be all gone now. Didn't check the registry.  I checked the settings on windows defender and set it to do a full scan. Unfortunately she is on vacation and I'm not really using her computer, just checking email and such. I will be running some other software on it later, but probably not as hard as use as she'd give it. I'll see what happens. Oh I did check after all that and verifier still responds to the the query showing dozens of drivers it's checking. Didn't bother to remove the avast ones as it should catch them if they weren't successfully uninstalled.

    Wednesday, April 23, 2014 8:25 PM
  • GF

    Fingers crossed here and continue to stay subscribed.  Yell if you have problems


    Wanikiya and Dyami--Team Zigzag

    Wednesday, April 23, 2014 8:51 PM
  • It BSODed on Monday at boot. It did not write a dump file. Perhaps it was before everything got started.

    Tuesday, April 29, 2014 7:36 PM