Constant BSoD 0x3B and afd.sys

Hello there,

This is my very first forum post, so please, excuse me if I do something wrong.

I have a little background story which might be important. I had some serious BSoD issues with my notebook (Acer Aspire 5755G). I sent it to the Acer Repair Center and they replaced the motherboard. I just got it back last friday.

Old Issues: (NO LONGER APPLIES, but it might be related)

BSoD Bug Check Strings, Codes, and the files that caused it:

- SYSTEM SERVICE EXCEPTION; 0x0000003b; dxgmms1.sys, ntoskrnl.exe
- KMODE_EXCEPTION_NOT_HANDLED; 0x0000001e; ntoskrnl.exe
- SYSTE_THREAD_EXCEPTION_NOT_HANDLED; 0x1000007e; nvlddmkm.sys
- DRIVER_POWER STATE_FAILURE; 0x0000009f; ntoskrnl.exe
- DRIVER_IRQL_NOT_LESS_OR_EQUAL; 0x000000d1; ntoskrnl.exe

notebook specs:

Intel Core i7-2670QM 2.2Ghz
Intel HD 3000 VGA
nVidia 540M VGA 1GB VRAM (N12P-GS, dedicated)
Nanya 4GB DDR3-1066 SO-DIMM RAM (Nany is a manufacturer)
Toshiba 750 GB HDD
North bridge: Intel Sandy Bridge-MB IMC
South bridge: Intel Cougar Point HM65

So these were the old issues, but since I got the notebook back which was 2 days ago, I have new problems with it. I got 4 BSoD since I got it back. 2 of them were about afd.sys and 2 were about 0x3B.
Funny thing is that after the OS recovers from the BSoD, no panel comes up saying Windows recovered and also there is no dump file under C:\Windows\Minidump\ .

After some research I found out that afd.sys BSoD can be caused by PunkBuster, which might explain why I started to get the afd.sys BSoDs after isntalling CoD4. Anyways I installed a fresh NIC driver and I also used cmd "netsh winsock reset", since then I haven't got such error and I hope I won't.

The 0x3B errors. In the old case there were some programs causing this BSoD, as you can see they were dxgmms1.sys and ntoskrnl.exe .
Right now only the 0x3B comes up and no file is named.

So this is the case, please tell me if I missed something out. I cannot post minidump, because as I said Windows does not create any dumpfiles to Minidump folder.

Thank you for your help in advance.

Also pardon my english.

Hello Minimalis and welcome.

Your English is great first of.

To be able to help you, we need more information, including what we call a dump file. A file that is created during your BSoD. The tutorial below will give you a very good insight.

Crash and lockup debug 'How To'

If my English is confusing you or didn't understand something just raise your hand. :)
Fred.

Minimalis91 said:

Thank you for your reply, Fred.

I haven't attached minidump files, because Windows haven't created one. I have the data of the last BSoD in my MEMORY.DMP file which is almost 400MB. I cannot upload that it would take ages for me as I have poor upload brandwidth.

I followed the link you posted and I changed the settings so right now it should save the logs into a small memory dump under the Minidump folder.

The strange thing is I've never changed debugging info to small memory dump on any of my previous Windows 7 installs/machines and still it always created a minidump and also after a BSoD a panel always came up about that the 'Windows has recovered from a ...' (or something like that) but now I do not get these messages.

Anyways I will post the content of the Minidump folder as soon as I recieve another BSoD.

Sounds great!

- Hello again.

Thanks for posting the dump file.

Code:

4: kd> lmvm dxgmms1
start             end                 module name
fffff880`04600000 fffff880`04646000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symcache\dxgmms1.sys\4CE799C146000\dxgmms1.sys
    Image path: dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Sat Nov 20 10:49:53 2010 (4CE799C1)
    CheckSum:         00047A89
    ImageSize:        00046000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Please update your DirectX.

Download Details - Microsoft Download Center - DirectX End-User Runtime

Fred.

Minimalis91 said:

It is up 2 date. When I installed Windows I used the same DirectX installer you posted.

Right now if I try to update DirectX via the webupdater, it just quits as it is up 2 date.

Also I ran a Memtest86+ 4.20. I got 13 passes without errors.

Edit:

I tried to update via: Download Details - Microsoft Download Center - DirectX End-User Runtimes (June 2010)

It haven't quited and it seems like it installed something. I will post back if BSoD happens again.

DirextX can be broken and it can happen quite fast.

Fred.

Code:

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa7f857bc554, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa80057815e7, address which referenced memory

Likely memory referenced. Follow this tutorial up and post back your results.

Fred.