BSoD Locale ID 3081 BC Code c8

Question

Hi guys,

I'm not overly savvy when it comes to PCs and have been scouring the net for help on how to solve a BSoD issue.

OS:

Intel Core 2 Quad CPU Q6600 @ 2.40GHz  2.40GHz

4GB RAM

Vista 32 bit Service pack 2

GPU:

ASUS GeForce GTX560Ti

BSoD occurred on load up after logging into Windows and waiting for general starup of applications to occur; so approx 2 mins after my desktop had opened. Since this time, i ahve restarted PC numerous times and more often than not, it will get to same point before BSoD displays. I have unplugged my seagate external, my headphones and restarted after both. Sometimes I can enter safe mode and sometimes not. i.e. my keyboard works at that point intermittently. The details of BSoD are as follows:

Locale ID: 3081

BCCode: C8

BCP1: 00000000

BCP2: 00000002

BCP3: 00000000

BCP4: 00000000

O.S Version: 6_0_6002

Service Pack: 2_0

Product: 768_1

OS version: 6.0.6002.2.2.0.768.3

The only software i can think that has been updated recently is as follows:

Avast

Nvidia

Windows updates

Plain English would really be appreicated here as I truly am a layman when it comes to computer stuff. Thanks in advance.

Answer 1

Thanks for the dumps!

All of the attached DMP files are of the IRQL_UNEXPECTED_VALUE (C8) bug check.

This indicates that the processor's IRQL is not what it should be at this time.

This error is usually caused by a device driver or another lower-level program that changed the IRQL for some period and did not restore the original IRQL at the end of that period. For example, the routine may have acquired a spin lock and failed to release it.

If we take a look at the call stack:

3: kd> kv

ChildEBP RetAddr  Args to Child              

b9f0b740 83cb2cb0 000000c8 00000000 00000002 nt!KeBugCheckEx+0x1e

b9f0b790 8d460b89 8d460ba4 b9f0b7b4 00000000 nt!KeExpandKernelStackAndCalloutEx+0x2a

b9f0b7c0 931d4d86 87094228 b9f0b7dc 870f5810 tcpip!UdpTlProviderSendMessages+0x5e (FPO: [Non-Fpo])

b9f0b808 931dca52 86e34de0 870f5800 899f6c10 tdx!TdxSendDatagramTransportAddress+0x206 (FPO: [Non-Fpo])

b9f0b824 83c4497a 88eae030 870f5810 870f58c0 tdx!TdxTdiDispatchInternalDeviceControl+0x5c (FPO: [Non-Fpo])

b9f0b83c 8d385a5c 886cc000 00000000 86fa74c0 nt!IofCallDriver+0x63

b9f0b850 8d38cac0 88eae030 870f5810 00000000 aswNdis2+0x6a5c

b9f0b9e0 8d37f61b 88ea4e50 870f5810 88eb3cb4 aswNdis2+0xdac0

b9f0b9f4 8d387496 88ea4e50 870f5810 b9f0ba1c aswNdis2+0x61b

b9f0ba04 83c4497a 88ea4e50 870f5810 88eb3cb0 aswNdis2+0x8496

b9f0ba1c 931e76fc 2aee4ffb 86e35ee0 88eb3bc8 nt!IofCallDriver+0x63

b9f0ba58 83c4497a 88ea4e50 870f5810 870f5980 aswTdi+0x6fc

b9f0ba70 93a2c914 2a514c86 00000001 056ef610 nt!IofCallDriver+0x63

b9f0bad8 93a213d0 056ef666 00000003 93a213d0 afd!AfdFastDatagramSend+0x5ba (FPO: [Non-Fpo])

b9f0bc58 83e471ce 8990ec01 00000001 056ef5d8 afd!AfdFastIoDeviceControl+0x3c1 (FPO: [Non-Fpo])

b9f0bd00 83e48694 88eb1ca8 0000104c 00000000 nt!IopXxxControlFile+0x2cf

b9f0bd34 83c4ac96 00001024 0000104c 00000000 nt!NtDeviceIoControlFile+0x2a

b9f0bd34 77255d14 00001024 0000104c 00000000 nt!KiSystemServicePostCall (FPO: [0,3] TrapFrame @ b9f0bd64)

056ef690 00000000 00000000 00000000 00000000 0x77255d14

^^ aswNdis2/aswTdi are avast! drivers, and seem to be the driver causing the improper IRQL.

IRQL << 16 <--- IRQL at the time of the crash.

IRQL << 8 <--- This was the expected IRQL (what it should have lowered to).

---------------------

Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes as it appears to be causing conflicts:

avast! removal - http://www.avast.com/uninstall-utility

MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

Regards,

Patrick

Answer 2

Hi,

In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

If you don't know where .DMP files are located, here's how to get to them:

1. Navigate to the %systemroot%\Minidump folder.

2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

If you are going to use Onedrive but don't know how to upload to it, please visit the following:

Upload photos and files to Onedrive.

Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick

Answer 3

Hello Patrick,

Please view the minidump link below that i zipped and uploaded to Skydrive. i hope i've done this correctly.

Sorry for the delay but today is the first time in quite a while since i've been able to turn on my PC in normal mode and not have it crash. as i was starting up my PC i unplugged keyboard and Microsoft VX 1000 camera. i am currently using my wireless/optical keyboard that came with my mouse. I have been using a plug in keyboard up until this point. Not sure if that is of any value... I appreciate your prompt reply and hope we can work this issue out.

Regards,

Graeme

https://onedrive.live.com/redir.aspx?cid=9a31bf3ff8d88ee6&resid=9A31BF3FF8D88EE6!143&parid=9A31BF3FF8D88EE6!136&authkey=!ADHLZD05Huq2EeM&ithint=file,.zip

Hi,

In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

If you don't know where .DMP files are located, here's how to get to them:

1. Navigate to the %systemroot%\Minidump folder.

2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

If you are going to use Onedrive but don't know how to upload to it, please visit the following:

Upload photos and files to Onedrive.

Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick

Answer 4

Thank you very much for your help Patrick. It worked a treat! Now I guess I have to decide on what to do re a virus protection program. I have downloaded mse but is it enough to protect my PC? What would u recommend?

Answer 5

Very glad to hear, thanks for the update.

Well, you have many options as far as that goes. I actually tend to use Microsoft Security Essentials + Malwarebytes on Windows 7 systems. On Windows 8 systems, instead of MSE I will use Windows Defender. I don't generally use a 3rd party antivirus on any home systems, only in business environments.

As far as 3rd party goes, I really like ESET.

Regards,

Patrick