Windows 8 and 8.1 Forums


  1. #1

    Posts : 1
    Windows Developer Preview


    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


      My System SpecsSystem Spec

  2. #2

    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:

    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


    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
    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".
    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
    8a921b95 3944f904        cmp     dword ptr [ecx+edi*8+4],eax ds:0023:214ec074=????????
    Resetting default scope
    PROCESS_NAME:  System
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
    READ_ADDRESS: GetPointerFromAddress: unable to read from 81232484
    Unable to read MiSystemVaType memory at 8121a060
    8a921b95 3944f904        cmp     dword ptr [ecx+edi*8+4],eax
    LAST_CONTROL_TRANSFER:  from 8a91fb1e to 8a921b95
    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_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+9b
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dxgmms1
    IMAGE_NAME:  dxgmms1.sys
    STACK_COMMAND:  .cxr 0xffffffff8adde5d0 ; kb
    FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+9b
    BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+9b
    Followup: MachineOwner
      My System SpecsSystem Spec

  3. #3

    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.

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

    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.
    Driver Verifier - Enable and Disable - Windows 7 Forums
      My System SpecsSystem Spec


Similar Threads
Thread Forum
Random BSOD 0x00000124 Hall.dll (Bsod is distorted/static
I have been getting a ton of bsods I have re installed video drivers, updated and reinstalled windows 8. Did countless hardware test(Video ram, check memory, Cpu test) all passed temperatures stay around 25-35 c. Recently uninstalled all video drivers and re installed. The bsods sometimes go away...
BSOD Crashes and Debugging
BSOD When playing games random Bsod messages
Hey I have a problem with my pc I got a few weeks ago It keeps getting the bsod and turning on and off randomly at times I use it mostly to play games and watch youtube , twitch ext. also internet can sometimes crash pointing this out Bsod can happen when playing a game and when on the web...
BSOD Crashes and Debugging
Windows 8 BSOD 0xc0000034 and BSOD 0xc0000001 (Laptop)
I have a clients Laptop (Asus X550C) running Windows 8 and the first error I had was 0xc0000034, having a look around I tried some fixes but none worked, eventually I was left with the following error: 0xc0000001. As of now I am stuck here, I have a backup of the main files the client needs but do...
BSOD Crashes and Debugging
BSOD - Hard lock turning into BSOD: DPC_WATCHDOG_VIOLATION
Hi, I've been getting hard locks where the audio continues to work while everything else becomes unresponsive that eventually degenerate into a BSOD with a DPC_Watchdog_Violation. Having looked at some of the events, I think it's probably some kind of SSD driver issue but I wanted to see if...
BSOD Crashes and Debugging
BSoD on Windows 8 & Sudddenly Restart without display BSoD
Hi, my problem with my laptop is Windows 8 BlueScreen and also Restart my laptop Without display BlueScreen and sometime this happened for more than 1 time regularly. this problem is happend Sometimes more than twice a day, when i'm doing regular things like reading a .pdf or watching a movie...
BSOD Crashes and Debugging
BSOD IRQL not less or equal. Random BSOD crashes?
Hi, i'm new to this forum and i hope you guy can help me :) So my laptop is relatively new, it's not even a month old. I guess i've been downloading a lot of stuff that caused this error. Now, i'm not a computer expert or any type of expert, so please bear with me :D Before i go on, here are...
BSOD Crashes and Debugging
BSOD on a cold boot! After BSOD works fine!
Since getting my custom built PC, I have a BSOD that occurs after about 2 minutes of getting past the welcome screen and I only have this BSOD on a cold boot. If you could please help me and give me some advice on what i should do I would be extremely grateful! I originally posted this BSOD on...
BSOD Crashes and Debugging

Eight Forums Android App Eight Forums IOS App Follow us on Facebook