Constant BSOD error.

[Kiuzuki]

I am searching for solutions all over the internet. I hope the experts reading my thread will solve my problem.
I am using
Processor : Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
2.79GHz
Installed memory (RAM) : 4.00 GB ( 2 sticks of 2 GB DDR3 )
OS : Windows 7 Home Basic 64 bit.
Graphic Card : MSI N210 1 GB (Nvidia)

I am suffering from Blue Screen Of Death.
I already replaced both the ram sticks, cleaned the fans etc.
I tried running my pc on XP , Windwos 7 Basic , Ultimate etc.
I updated each and every driver.
I had following BSOD errors
1.Memory_Management
2.win32.sys
3.Bad pool header
4.ntfs ( don't know the exact name of the error )

before making a new thread i read many threads here, i did everything i.e memtest , update drivers , disable avast , memtest on single sticks , every single thing I did but still I have the problem of bsod. I have this problem when I connect any pendrive or portable hardisk , webcam which are compatible with the OS.

I have formatted with many times , I have installed a genuine windows 7 still I have this bsod problem, all my applications like Photoshop , Autodesk Maya , flashplayer etc also crashed many times. I thought photoshop , maya etc softwares may be the cause so i installed them in other pc which was intel i3 and still that intel i3 never had any problem like bsod.

i don't understand though having a i5 i am having a problem like bsod. i know it happened with many reason but almost every single part has been replaced.
Help me
I have attached the minidump files

 

[zigzag3143]

The two DMPs files you have uploaded are related to memory management and your Avast is the cause. You cant disable Avant (or most other malware apps) because they still load the drivers when disabled.

One other item of note is the NokiaMServer.exe. I would remove it at leas to test as it is known to cause them as well.



Unable to load image \??\C:\Windows\system32\drivers\aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )




I notice your avast which is often at least a contributing cause of BSOD'S . Please remove and replace your Avast with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/

 

[Kiuzuki]

Thank You. I will try this and report if any bsod error comes in my pc. please reply me if i report any problems thanks.

 

[zigzag3143]

Thank You. I will try this and report if any bsod error comes in my pc. please reply me if i report any problems thanks.

good luck

 

[Kiuzuki]

zigzag3143
i got two more BSOD error. I have attached a zip file of it. please tell the what thing caused the BSOD error.
the error occured when I was playing World Of Warcraft Cataclysm
the error name is something " dxgmss " i am not sure about the name. but i hope you can find out the error name by the dump files i have attached.
Processor : Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
2.79GHz
Installed memory (RAM) : 4.00 GB ( 2 sticks of 2 GB DDR3 )
OS : Windows 7 Ultimate 64 bit.
Graphic Card : MSI N210 1 GB (Nvidia)


the files are zipped in .zip format with iZarc

 

[Kiuzuki]

Can some one help me, I already posted the BSOD error above ^

 

[Kiuzuki]

Thank You. I will try this and report if any bsod error comes in my pc. please reply me if i report any problems thanks.

good luck

help me please !
no one has replied here

 

[writhziden]

Loading Dump File [K:\BSODDmpFiles\Kiuzuki\012712-27066-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Fri Jan 27 10:48:32.502 2012 (GMT-7)
System Uptime: 0 days 2:18:55.595
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800fe20d90, fffff88004a266a8, fffff88004a25f10}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800fe20d90, The address that the exception occurred at
Arg3: fffff88004a266a8, Exception Record Address
Arg4: fffff88004a25f10, Context Record Address

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


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

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`0fe20d90 8b4810          mov     ecx,dword ptr [rax+10h]

EXCEPTION_RECORD:  fffff88004a266a8 -- (.exr 0xfffff88004a266a8)
ExceptionAddress: fffff8800fe20d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88004a25f10 -- (.cxr 0xfffff88004a25f10)
rax=0004000000000000 rbx=fffff8a003785260 rcx=fffffa8005dca000
rdx=fffffa800494ba90 rsi=fffffa8005dca000 rdi=fffffa8005dca000
rip=fffff8800fe20d90 rsp=fffff88004a268e0 rbp=fffffa8004d05550
 r8=fffffa800471ec01  r9=0000000000000000 r10=0000000000000000
r11=0000000000000176 r12=fffffa800494ba90 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`0fe20d90 8b4810          mov     ecx,dword ptr [rax+10h] ds:002b:00040000`00000010=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec10e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`0fe20d90 8b4810          mov     ecx,dword ptr [rax+10h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800fe1ded3 to fffff8800fe20d90

STACK_TEXT:  
fffff880`04a268e0 fffff880`0fe1ded3 : 00000000`00000000 fffffa80`04e34718 00000000`00000093 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`04a26910 fffff880`0fe3865d : 00000000`00000000 fffff8a0`0a704b50 fffffa80`00000000 fffffa80`0471ece0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`04a26ae0 fffff880`0fe38398 : fffff800`03fd3080 fffff880`0fe37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04a26cd0 fffff880`0fe37e96 : 00000000`00000000 fffffa80`046fe600 00000000`00000080 fffffa80`05cbd010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04a26d00 fffff800`02f2dc06 : 00000000`02c5eb91 fffffa80`05bcf2b0 fffffa80`03cd3040 fffffa80`05bcf2b0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04a26d40 fffff800`02c67c26 : fffff800`02e03e80 fffffa80`05bcf2b0 fffff800`02e11c40 fffff880`0124d534 : nt!PspSystemThreadStartup+0x5a
fffff880`04a26d80 00000000`00000000 : fffff880`04a27000 fffff880`04a21000 fffff880`04a26690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

STACK_COMMAND:  .cxr 0xfffff88004a25f10 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

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

Caused by DirectX or your display card drivers. Other possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

 

[Kiuzuki]

Thanks for your solution. I will report back if I get any BSOD error again.

 

[writhziden]

You're welcome. Thanks for keeping us updated. Best wishes!