BSOD

shyam · Nov 27, 2011

This bsod comes at first start after the power is on , also cpu makes grilling sound a loud one , after that it sucessfully restarts and works fine....

Please help.....dump files are attached below

Thanks

Capt.Jack Sparrow · Nov 29, 2011

Hello and Welcome!

Reinstall your display drivers because I saw stack trace for display drivers and Direct X. Then updated your Motherboard chip drivers. I found ASACPI.sys it's dated 2004 which is notorious for BSOD. To remove it go to C:\WINDOWS\system32\drivers and locate the file and rename ASACPI.sys to ASACPI.old and reboot the system.

Update the Following Drivers:

Code:

igdkmd32.sys Thu Sep 24 00:48:09 2009
AsUpIO.sys   Mon Jul 06 07:51:27 2009
AsIO.sys     Mon Aug 03 12:32:32 2009
SRS_HDAL_i386.sys Fri Jul 02 23:36:51 2010

Check this article How to Update Drivers on Windows 7 | Captain Debugger

Bugcheck:

Code:

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: c0000005, The exception code that was not handled
Arg2: 8a921b95, The address that the exception occurred at
Arg3: 8addea04, Exception Record Address
Arg4: 8adde5d0, 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::ReferenceAllocationForSubmission+9b
8a921b95 3944f904        cmp     dword ptr [ecx+edi*8+4],eax

EXCEPTION_RECORD:  8addea04 -- (.exr 0xffffffff8addea04)
ExceptionAddress: 8a921b95 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x0000009b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 214ec074
Attempt to read from address 214ec074

CONTEXT:  8adde5d0 -- (.cxr 0xffffffff8adde5d0)
eax=00000000 ebx=ab5d4eb8 ecx=214ec070 edx=00000000 esi=83ffa000 edi=00000000
eip=8a921b95 esp=8addeacc ebp=8addead8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x9b:
8a921b95 3944f904        cmp     dword ptr [ecx+edi*8+4],eax ds:0023:214ec074=????????
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:  00000000

EXCEPTION_PARAMETER2:  214ec074

READ_ADDRESS: GetPointerFromAddress: unable to read from 81232484
Unable to read MiSystemVaType memory at 8121a060
 214ec074 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+9b
8a921b95 3944f904        cmp     dword ptr [ecx+edi*8+4],eax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 8a91fb1e to 8a921b95

STACK_TEXT:  
8addead8 8a91fb1e 00000000 0001835e 00000000 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x9b
8addebb4 8a9354c9 00000000 84a19008 00000c4c dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x123e
8addecf8 8a93524b 83b73780 841e2568 84064cb0 dxgmms1!VidSchiSubmitRenderCommand+0x199
8added10 8a934f3e 83b734c0 00000000 8293ad00 dxgmms1!VidSchiSubmitQueueCommand+0x59
8added2c 81350c70 83b73780 749fabb5 00000000 dxgmms1!VidSchiWorkerThread+0xa2
8added70 811859c1 8a934e9c 83b73780 00000000 nt!PspSystemThreadStartup+0xa1
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+9b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e5462df

STACK_COMMAND:  .cxr 0xffffffff8adde5d0 ; kb

FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+9b

BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+9b

Followup: MachineOwner

zigzag3143 · Nov 29, 2011

AFTER doing what capt Jack suggests IF you are continuing to have BSOD's run these two tests.

These were related to a memory exception.

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

Click to expand...

RAM - Test with Memtest86+ - Windows 7 Forums

2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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).

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.

Click to expand...

Driver Verifier - Enable and Disable - Windows 7 Forums

BSOD

shyam

New Member

My Computer

System One

Capt.Jack Sparrow

BSOD Kernel Dump Analyst

My Computer

System One

zigzag3143

Banned

My Computer

System One