BSOD on pc startup

luffy3san · Jun 18, 2012

Recently I built a new pc and I've been getting random BSOD's while on startup or soon after my desktop loads and also during shutdown sometimes. Any help is appreciated.

Here's my recent crash info from WhoCrashed:

Bug Check Name: IRQL NOT LESS OR EQUAL
Bug Check Code: 0xA
Parameter 1: 0x28
Parameter 2: 0x2
Parameter 3: 0x0
Parameter 4: 0xFFFFF80002F233D8
Probably Caused by: ntoskrnl.exe / ntkrnlmp.exe

My PC Specs:
- Asrock z77 extreme4
- i5 3570k
- Corsair Vengeance Low Profile (2 x 4GB)
- Sapphire Radeon HD 7850
- Windows 7 Home Premium 64 bit OEM
- Antec 620M PSU
- Cooler Master Hyper 212 Evo

usasma · Jun 19, 2012

Please provide this info: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

While waiting for a reply, please run Driver Verifier according to these instructions: Driver Verifier Settings

luffy3san · Jun 19, 2012

usasma said:
Please provide this info: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

While waiting for a reply, please run Driver Verifier according to these instructions: Driver Verifier Settings

I've attached the PERFMON HTML & Windows_NT6_BSOD_jcgriff2 files. Thanks!

usasma · Jun 19, 2012

High Definition Audio device is disabled. Is this deliberate? If so, why?

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

The one BSOD visible in the WER section of MSINFO32 blames your Norton/Symantec protection.
Please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Nothing else significant. Let's see what Driver Verifier turns up (from my previous post).

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
AtihdW76.sys     Thu Feb 23 07:30:12 2012 (4F463154)
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
ISCTD64.sys      Tue Aug 23 13:32:39 2011 (4E53E437)
MBfilt64.sys     Thu Jul 30 23:40:32 2009 (4A7267B0)
MpFilter.sys     Fri Mar 09 06:05:26 2012 (4F59E3F6)
RTKVHD64.sys     Tue Jan 31 05:55:06 2012 (4F27C88A)
VKbms.sys        Thu Sep 30 12:16:33 2010 (4CA4B7E1)
WPRO_41_2001.sys Mon Nov 07 16:04:48 2011 (4EB847F0)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asmthub3.sys     Fri Mar 04 02:55:10 2011 (4D709ADE)
asmtxhci.sys     Fri Mar 04 02:54:59 2011 (4D709AD3)
athrx.sys        Tue Feb 22 15:17:31 2011 (4D6419DB)
atikmdag.sys     Thu Apr 05 21:48:25 2012 (4F7E4B69)
atikmpag.sys     Thu Apr 05 21:10:44 2012 (4F7E4294)
cpuz135_x64.sys  Wed Sep 21 04:23:41 2011 (4E799F0D)
iaStor.sys       Wed Feb 01 19:15:24 2012 (4F29D59C)
igdkmd64.sys     Mon Mar 19 19:31:54 2012 (4F67C1EA)
ikbevent.sys     Tue Jan 03 19:35:09 2012 (4F039EBD)
imsevent.sys     Tue Jan 03 19:35:31 2012 (4F039ED3)
iusb3hcs.sys     Mon Feb 27 05:58:49 2012 (4F4B61E9)
iusb3hub.sys     Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys     Mon Feb 27 05:56:53 2012 (4F4B6175)
k57nd60a.sys     Tue May 10 00:42:30 2011 (4DC8C236)
mshidkmdf.sys    Mon Jul 13 20:06:24 2009 (4A5BCC00)
rzdaendpt.sys    Mon May 07 22:46:03 2012 (4FA888EB)
rzudd.sys        Mon May 14 22:50:16 2012 (4FB1C468)
rzvkeyboard.sys  Mon May 14 22:50:36 2012 (4FB1C47C)
speedfan.sys     Fri Mar 18 12:08:46 2011 (4D83838E)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061912-7254-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jun 19 15:30:03.606 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:14.418
BugCheck 24, {1904fb, fffff88002545af8, fffff88002545350, fffff80002e7d10f}
Probably caused by : ntkrnlmp.exe ( nt!CcFindBcb+37 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_nt!CcFindBcb+37
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`02545af8 fffff880`02545350 fffff800`02e7d10f
BiosVersion = P1.70
BiosReleaseDate = 06/06/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061912-8970-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jun 19 15:26:36.549 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:09.361
BugCheck 3B, {c0000005, fffff88000dab1d1, fffff88006cb8770, 0}
Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkMulti+51 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  winlogon.exe
FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!TreeUnlinkMulti+51
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`00dab1d1 fffff880`06cb8770 00000000`00000000
BiosVersion = P1.70
BiosReleaseDate = 06/06/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

luffy3san · Jun 19, 2012

usasma said:
High Definition Audio device is disabled. Is this deliberate? If so, why?

I did disable this myself because I thought it wasn't necessary. It displayed a big list under audio playback devices which I don't use. Should I turn it back on?

usasma said:
The one BSOD visible in the WER section of MSINFO32 blames your Norton/Symantec protection.
Please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.
Nothing else significant. Let's see what Driver Verifier turns up (from my previous post).

I used to have Norton but I uninstalled it because it kept causing bsod in the middle of updating Norton AV. Right now, I only have the Microsoft Security Essentials installed. I'll try the tool to try completely removing Norton remnants if they are there.

Btw, I followed the steps for the driver verifier and restarted the pc, but it didn't do anything... There was just a normal startup. Is something supposed to happen?

Thanks for the quick response.

usasma · Jun 20, 2012

I ask because sometimes people either don't know that it's disabled - or they were having sound problems and disabled it because of them.
Please turn it back on and then update the drivers.
Then feel free to disable it again.

Run the Norton Removal Tool anyway - there's remnants of Norton still on your system.
Here's the link: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Driver Verifier is supposed to cause a BSOD if any selected driver fails the tests that were selected. Let Driver Verifier run for at least 36 hours of normal use.

luffy3san · Jun 20, 2012

usasma said:
I ask because sometimes people either don't know that it's disabled - or they were having sound problems and disabled it because of them.
Please turn it back on and then update the drivers.
Then feel free to disable it again.

Run the Norton Removal Tool anyway - there's remnants of Norton still on your system.
Here's the link: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Driver Verifier is supposed to cause a BSOD if any selected driver fails the tests that were selected. Let Driver Verifier run for at least 36 hours of normal use.

So far I've had 1x BSOD said caused by atikmdag.sys which i read is related to the video card. I've attached the .dmp file. Thanks for the help!

usasma · Jun 20, 2012

This is a Driver Verifier enabled memory dump. What it means is that the crash happened while Driver Verifier was enabled and it blames the video driver for failing the Driver Verifier enabled tests (it's possible to get a regular memory dump when Driver Verifier is enabled, but it's not very common).

So, the most likely scenario here is that the video drivers are corrupted. But it can also point to problems with the video card itself (hardware problems).

So, unplug the system from the wall and open up the case.
Hold onto the metal of the case while gently removing the video card from it's slot.
Blow out the slot with a bit of canned air, and then wipe the gold contacts on the card with a lint free cloth.
Gently and carefully reinsert the card making sure that it's completely seated in the slot.
Reconnect the power to the card, making sure that the plug is securely and firmly seated in it's socket
Make sure that the fan turns freely and that the cooler isn't clogged or obstructed by other equipment.
Then plug it back into the wall (leaving the side off temporarily).

When you turn it on, see if the fan is working on the card.
If it is, put the side case back on.

Then, uninstall the video drivers using Control Panel...Programs...Uninstall a program.
Then use this guide to get rid of any remnants - BUT DON'T INSTALL THE DRIVERS!!!: how to properly uninstall ATI/AMD Software Drivers for Graphics Cards.
Then install the DRIVERS ONLY using this guide: ATI video cards - DRIVER ONLY installation procedure This will ensure that it's not some of the other ATI components that are causing the problems.

Leave Driver Verifier on and see if it causes a BSOD over the next 36 hours of operation.
If it does, and if it blames the video drivers - then it's time to try another video card.

BE SURE to turn Driver Verifier off when we're done testing (select the "Delete existing settings" in it's interface).

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
AtihdW76.sys     Thu Feb 23 07:30:12 2012 (4F463154)
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
ISCTD64.sys      Tue Aug 23 13:32:39 2011 (4E53E437)
MBfilt64.sys     Thu Jul 30 23:40:32 2009 (4A7267B0)
MpFilter.sys     Fri Mar 09 06:05:26 2012 (4F59E3F6)
RTKVHD64.sys     Thu May 31 05:21:30 2012 (4FC7381A)
VKbms.sys        Thu Sep 30 12:16:33 2010 (4CA4B7E1)
WPRO_41_2001.sys Mon Nov 07 16:04:48 2011 (4EB847F0)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asmthub3.sys     Fri Mar 04 02:55:10 2011 (4D709ADE)
asmtxhci.sys     Fri Mar 04 02:54:59 2011 (4D709AD3)
athrx.sys        Tue Feb 22 15:17:31 2011 (4D6419DB)
atikmdag.sys     Thu Apr 05 21:48:25 2012 (4F7E4B69)
atikmpag.sys     Thu Apr 05 21:10:44 2012 (4F7E4294)
cpuz135_x64.sys  Wed Sep 21 04:23:41 2011 (4E799F0D)
iaStor.sys       Wed Feb 01 19:15:24 2012 (4F29D59C)
igdkmd64.sys     Mon Mar 19 19:31:54 2012 (4F67C1EA)
ikbevent.sys     Tue Jan 03 19:35:09 2012 (4F039EBD)
imsevent.sys     Tue Jan 03 19:35:31 2012 (4F039ED3)
iusb3hcs.sys     Mon Feb 27 05:58:49 2012 (4F4B61E9)
iusb3hub.sys     Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys     Mon Feb 27 05:56:53 2012 (4F4B6175)
k57nd60a.sys     Tue May 10 00:42:30 2011 (4DC8C236)
rzdaendpt.sys    Mon May 07 22:46:03 2012 (4FA888EB)
rzudd.sys        Mon May 14 22:50:16 2012 (4FB1C468)
rzvkeyboard.sys  Mon May 14 22:50:36 2012 (4FB1C47C)
speedfan.sys     Fri Mar 18 12:08:46 2011 (4D83838E)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062012-8143-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jun 20 10:46:30.227 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:32.023
BugCheck 3B, {c000001d, fffff88004e52b51, fffff8800afc6350, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+171b51 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_0x3B_VRF_atikmdag+171b51
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`04e52b51 fffff880`0afc6350 00000000`00000000
BiosVersion = P1.70
BiosReleaseDate = 06/06/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

luffy3san · Jun 21, 2012

Hi, I followed those steps and re-installed the driver manually. But, when I was trying to shut down pc, I got a BSOD, said "athrx.sys" "page fault in non paged area" What does this mean? Thanks.

usasma · Jun 22, 2012

Well, part of the reason is that Driver Verifier is still running. The purpose of Driver Verifier is to cause BSOD's.
Please turn it off. To do this, open up Driver Verifier and select "Delete existing settings" and click on "Finish". Then reboot to clear the settings.

Once that's done, update your TP-LINK 450Mbps Wireless N Adapter drivers (that's what athrx.sys belongs to).

The Driver Verifier enabled memory dump blames this driver - but we don't know if it's a condition that will only occur during Driver Verifier tests, or if it occurs during normal operation.

Leave the system without Driver Verifier. Then, if there are certain types of memory dumps, we can use Driver Verifier if it's needed.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
ISCTD64.sys      Tue Aug 23 13:32:39 2011 (4E53E437)
MBfilt64.sys     Thu Jul 30 23:40:32 2009 (4A7267B0)
MpFilter.sys     Fri Mar 09 06:05:26 2012 (4F59E3F6)
RTKVHD64.sys     Thu May 31 05:21:30 2012 (4FC7381A)
VKbms.sys        Thu Sep 30 12:16:33 2010 (4CA4B7E1)
WPRO_41_2001.sys Mon Nov 07 16:04:48 2011 (4EB847F0)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asmthub3.sys     Fri Mar 04 02:55:10 2011 (4D709ADE)
asmtxhci.sys     Fri Mar 04 02:54:59 2011 (4D709AD3)
athrx.sys        Tue Feb 22 15:17:31 2011 (4D6419DB)
atikmdag.sys     Thu Apr 05 21:48:25 2012 (4F7E4B69)
atikmpag.sys     Thu Apr 05 21:10:44 2012 (4F7E4294)
cpuz135_x64.sys  Wed Sep 21 04:23:41 2011 (4E799F0D)
iaStor.sys       Wed Feb 01 19:15:24 2012 (4F29D59C)
igdkmd64.sys     Mon Mar 19 19:31:54 2012 (4F67C1EA)
ikbevent.sys     Tue Jan 03 19:35:09 2012 (4F039EBD)
imsevent.sys     Tue Jan 03 19:35:31 2012 (4F039ED3)
iusb3hcs.sys     Mon Feb 27 05:58:49 2012 (4F4B61E9)
iusb3hub.sys     Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys     Mon Feb 27 05:56:53 2012 (4F4B6175)
k57nd60a.sys     Tue May 10 00:42:30 2011 (4DC8C236)
rzdaendpt.sys    Mon May 07 22:46:03 2012 (4FA888EB)
rzudd.sys        Mon May 14 22:50:16 2012 (4FB1C468)
rzvkeyboard.sys  Mon May 14 22:50:36 2012 (4FB1C47C)
speedfan.sys     Fri Mar 18 12:08:46 2011 (4D83838E)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062112-11278-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jun 21 09:05:06.343 2012 (UTC - 4:00)
System Uptime: 0 days 0:56:30.139
BugCheck 50, {fffff0800a5a5be8, 0, fffff880045e4b47, 7}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : athrx.sys ( athrx+fcb47 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_VRF_athrx+fcb47
Bugcheck code 00000050
Arguments fffff080`0a5a5be8 00000000`00000000 fffff880`045e4b47 00000000`00000007
BiosVersion = P1.70
BiosReleaseDate = 06/06/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

BSOD on pc startup

luffy3san

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

luffy3san

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

luffy3san

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

luffy3san

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

luffy3san

New member

My Computer

usasma

Mr. Cranky Pants

My Computer