BSOD on Startup or Wake-Up

[elsongs]

Since Jan 29 I've suddenly been getting a BSOD on Startup of my computer, which also happens when it wakes up from a Sleep state. This is the first time I've EVER gotten a BSOD in Windows 7!!!!

I have not installed any new software recently.

I get one of two kinds of BSODs:

"DRIVER_IRQL_NOT_LESS_OR_EQUAL"

or

"A clock interrupt was not received on a secondary processor within the allocated time interval"

It points to "ataport.sys" as the problem driver, most of the time. Other times it points to a .DLL file (forgot which one).

I read that the "not less or equal" errors were mostly due to bad memory, so I sunk over $100 in 4GB RAM (there was 2GB originally when the problem started, the old RAM sticks removed and replaced with the new ones) yesterday, but the BSODs still persist.

I *AM* able to get the computer up and running, about 30-60% of the time. If the computer has been running for a while, the chances are better and I will avoid the BSOD on startup (I'm typing on this computer right now). Otherwise, if it's from a cold start, the BSODs happen.

I ran the "Fix Startup Errors" utility but it couldn't find any solution for me.

The BSOD only happens during startup or wakeup, but when I tried to do a system scan on my Anti-Virus program (Eset NOD32), at some point it BSODs. But I haven't noticed it happening while doing my usual activities on the computer.

- x86 (32-bit) or x64 ?
32-bit
- the original installed OS on the system?
Installed
- an OEM or full retail version?
Full Retail

- What is the age of system (hardware)?
System built Nov 2005
PSU Installed Dec 2011
New RAM Installed Feb 2012

- What is the age of OS installation (have you re-installed the OS?)
OS Installed Feb 2010; No reinstalls.

 

[zigzag3143]

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.


If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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/Win7 Startup Repair feature).

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 "Special Pool", "Force Pending I/O Requests" and "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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Dave76]

Welcome to Seven Forums, good job on the system specs, thanks.


STOP 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
A hardware device, its driver, or related software might have caused this error.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82cc19ae, The address that the exception occurred at
Arg3: 807dda63, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpWorkerThread+50
82cc19ae 8b0f            mov     ecx,dword ptr [edi]

TRAP_FRAME:  807dda63 -- (.trap 0xffffffff807dda63)
ErrCode = 00000000
eax=053b109c ebx=bcafd810 ecx=807ddae0 edx=00010000 esi=807c6800 edi=bcafd848
eip=82cc19ae esp=807ddad7 ebp=807ddb14 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!ExpWorkerThread+0x50:
82cc19ae 8b0f            mov     ecx,dword ptr [edi]  ds:0023:bcafd848=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  System

CURRENT_IRQL:  1f

UNALIGNED_STACK_POINTER:  807ddad7

LAST_CONTROL_TRANSFER:  from 8afa8876 to 82cc19ae

STACK_TEXT:  
807ddb14 8afa8876 853b109c 00000000 00000000 nt!ExpWorkerThread+0x50
807ddb28 8afa8e77 853b10e0 8774b9d0 807ddb68 ataport!ProxyRequestDpc+0x22
807ddb38 8afa11dc 853b23f0 807ddb48 00000000 ataport!IdeProcessPortNotification+0x99
807ddb68 8af95fc2 853b23f4 8774b9d0 853b23f4 ataport!AtaPortCompleteRequest+0x22
807ddb84 8af961e0 853b23f4 8774b9d0 017ddc50 atapi!AtapiCompleteRequest+0x122
807ddbac 8af962df 853b2300 8774b9d0 807ddc50 atapi!AtapiProcessInterrupt+0x1d0
807ddbd4 8afa5f10 853b2350 807ddbec 8afa649a atapi!AtapiHwInterrupt+0xf3
807ddbe0 8afa649a 853b10e0 00000000 82c7e54c ataport!CallMiniPortHwInterrupt+0x14
807ddbec 82c7e54c 85c7c780 853b1028 807ddc0c ataport!IdePortInterrupt+0x10
807ddc18 82c7e499 00000002 000000a3 807ddd20 nt!KiChainedDispatch2ndLvl+0x60
807ddc18 8f548bb6 00000002 000000a3 807ddd20 nt!KiChainedDispatch+0x29
807ddc98 82cc437f 86dcad48 807c6800 807c1000 amdk8!C1Halt+0x4
807ddd20 82cbbe0d 00000000 0000000e 00000000 nt!PoIdle+0x524
807ddd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!ProxyRequestDpc+22
8afa8876 5d              pop     ebp

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ataport!ProxyRequestDpc+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce788e8

FAILURE_BUCKET_ID:  0x8E_ataport!ProxyRequestDpc+22

BUCKET_ID:  0x8E_ataport!ProxyRequestDpc+22

Followup: MachineOwner
---------

Update or remove the below drivers/apps, this may be what is causing your crashes.


Out of date or problematic drivers:

ASACPI.sys   Fri Aug 13 10:52:52 2004 - Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities

Motherboard utilities are known to cause crashes, uninstall all the Asus utilities. This driver is also out of date.

GEARAspiWDM.sys Mon May 18 20:16:53 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes

iTunes is known for causing crashes on Windows 7, uninstall for testing purposes.

nvmpu401.sys Thu Apr 14 03:34:22 2005 - nVidia nForce MPU401 Driver

Check your motherboard support site for an updated driver.

RimSerial.sys Tue Nov 25 01:02:13 2008 - RIM Virtual Driver (probably associated with a Blackberry)

Uninstall this program. Check their website for a newer version.

 

[elsongs]

UPDATE: I ran Memtest86+ and it passed 10 times, so I guess it wasn't the memory after all.

- I was able to boot up Windows 7, but I soon got a BSOD after trying to get on to this website.
- Next attempt at booting up to Windows 7: BSOD.
- I was able to successfully boot up to my Windows XP partition though. The XP Partition contains specialized programs (music production) and is actually more important than my Windows 7 partition. Now crashes in Win 7 are getting more frequent.
- I do get BSODs on the XP partition when booting up cold. But after the computer has been on for a while, I can boot up XP successfully.
- I have not gotten crashes after successfully booting up the XP partition.

 

[zigzag3143]

Might want to update your 2009 ESET as well.

 

[Dave76]

Your description sounds like a hardware issue.

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.

 

[elsongs]

Thanks, I'll try that... but how its it able to boot in the WinXP partition and not Windows 7?
I did update my NOD32 antvirus program the last time I was able to successfully boot into Windows 7, but since then I can not boot up.

 

[elsongs]

Your description sounds like a hardware issue.

Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.

This is what I got:

Vcore voltage: 1.32V
3.3V Voltage: 3.34V
5V Voltage: 4.94V
12V Voltage: 11.77V

 

[writhziden]

Please follow the rest of the steps in post #6 to provide us with the information Dave76 requested.

 

[elsongs]

Please follow the rest of the steps in post #6 to provide us with the information Dave76 requested.

I'm afraid I am unable to do that since my computer is getting more and more unstable. I was able to boot to myWindows XP partition, but I am now experiencing BSODs there more often. Thus, I am unable to load and install the programs you mentioned.

I opened up my computer and found one of the capacitors close to the CPU had busted its cap and is leaking electrolytes. This leads me to conclude that it's my motherboard that's the culprit here and not any issue with Windows 7.

I have some music projects I need to finish on that computer...I need to go find a replacement motherboard of an identical model now.

 

[Dave76]

Definitely your motherboard.
At least you found the cause.

Thanks for letting us know the status.

Let us know how the new motherboard is working.