Windows 8 and 8.1 Forums

every cold start BSODs

  1. #1


    Posts : 4
    Windows 8.1

    every cold start BSODs


    Hi.
    I'm getting BSOD on every cold start. it never happens on reboot or during the work. It happens once, reboots and starts fine. Only few times there is a dump file created, most times it reboots before the creation of the file.
    I really need help with that.

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1


    A few dumpfiles point to memory corruption.

    According to the specification of your mainboard Asrock A770DE+

    Dual Channel DDR2 memory technology
    - 4 x DDR2 DIMM slots
    - Supports DDR2 1066*/800/667/533 non-ECC, un-buffered memory
    But your runnng 333 mhz memory.
    Also your system.txt mention you have Memory: 6144MB RAM installed.
    But the analyze shows only Dimm 0 1024 mb Dimm 1 1024 mb Dimm 2 2048 mb Dimm 3 not populated
    Conclusion:
    One of memory modules is broken or not installed properly
    The memory is not compatible with your mainboard.
    Check your manual if the memorymodule are inserted in the right Banks
    Change your memory with the right modules.

    Code:
    Memory Device (Type 17) - Length 27 - Handle 0014h]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    72 bits
      Size                          1024MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM0
      Bank Locator                  BANK0
      Memory Type                   13h - Specification Reserved
      Type Detail                   0080h - Synchronous
      Speed                         333MHz
      Manufacturer                  Manufacturer0
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum0
    [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0015h]
      Starting Address              00000000h
      Ending Address                000fffffh
      Memory Device Handle          0014h
      Mem Array Mapped Adr Handle   0013h
      Partition Row Position        01
      Interleave Position           [None]
      Interleave Data Depth         [None]
    [Memory Device (Type 17) - Length 27 - Handle 0016h]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    72 bits
      Size                          1024MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM1
      Bank Locator                  BANK1
      Memory Type                   13h - Specification Reserved
      Type Detail                   0080h - Synchronous
      Speed                         333MHz
      Manufacturer                  Manufacturer1
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum1
    [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0017h]
      Starting Address              00100000h
      Ending Address                001fffffh
      Memory Device Handle          0016h
      Mem Array Mapped Adr Handle   0013h
      Partition Row Position        01
      Interleave Position           [None]
      Interleave Data Depth         [None]
    [Memory Device (Type 17) - Length 27 - Handle 0018h]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    72 bits
      Size                          2048MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM2
      Bank Locator                  BANK2
      Memory Type                   13h - Specification Reserved
      Type Detail                   0080h - Synchronous
      Speed                         333MHz
      Manufacturer                  Manufacturer2
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum2
    [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0019h]
      Starting Address              00200000h
      Ending Address                003fffffh
      Memory Device Handle          0018h
      Mem Array Mapped Adr Handle   0013h
      Partition Row Position        01
      Interleave Position           [None]
      Interleave Data Depth         [None]
    [Memory Device (Type 17) - Length 27 - Handle 001ah]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   [Unknown]
      Data Width                    64 bits
      Size                          [Not Populated]
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM3
      Bank Locator                  BANK3
      Memory Type                   02h - Unknown
      Type Detail                   0004h - Unknown
      Speed                         0MHz
      Manufacturer                  Manufacturer3
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum3
    Also your Bios is from 2010 and this is the latest version and it only has supports for windows 7 drivers.
    see ASRock > Products > Motherboard > A770DE+ > Download
    Last edited by lifetec; 04 Apr 2014 at 08:34.
      My System SpecsSystem Spec

  3. #3


    Posts : 4
    Windows 8.1


    thank you. memory in slot 4 I had out for some days and put it back a while ago (testing if that was the issue). Is it possible that this is the reason it is not shown above? also all this memory modules are supposed to be 667mhz. I'll check it in the afternoon and also try to leave only one memory module to rule out the others. W8.1 should boot with 1GB of ram?
    With mobo drivers I guess there is nothing I could do...
      My System SpecsSystem Spec

  4. #4


    Posts : 660
    windows 8.1


    =eksces;363389]thank you. memory in slot 4 I had out for some days and put it back a while ago (testing if that was the issue). Is it possible that this is the reason it is not shown above? also all this memory modules are supposed to be 667mhz. I'll check it in the afternoon and also try to leave only one memory module to rule out the others. W8.1 should boot with 1GB of ram?
    With mobo drivers I guess there is nothing I could do...
    Your latest dumpfile from Sun Mar 30 20:03:05.503 2014 (UTC + 2:00) shows all 4 of the modules but now they are running only at 266MHz.
    See if you can set the good 667MHZ in your BIOS settings or reset your BIOS to default.

    Code:
    Memory Device (Type 17) - Length 27 - Handle 0014h]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    72 bits
      Size                          1024MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM0
      Bank Locator                  BANK0
      Memory Type                   13h - Specification Reserved
      Type Detail                   0080h - Synchronous
      Speed                         266MHz
      Manufacturer                  Manufacturer0
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum0
    [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0015h]
      Starting Address              00000000h
      Ending Address                000fffffh
      Memory Device Handle          0014h
      Mem Array Mapped Adr Handle   0013h
      Partition Row Position        01
      Interleave Position           [None]
      Interleave Data Depth         [None]
    [Memory Device (Type 17) - Length 27 - Handle 0016h]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    72 bits
      Size                          1024MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM1
      Bank Locator                  BANK1
      Memory Type                   13h - Specification Reserved
      Type Detail                   0080h - Synchronous
      Speed                         266MHz
      Manufacturer                  Manufacturer1
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum1
    [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0017h]
      Starting Address              00100000h
      Ending Address                001fffffh
      Memory Device Handle          0016h
      Mem Array Mapped Adr Handle   0013h
      Partition Row Position        01
      Interleave Position           [None]
      Interleave Data Depth         [None]
    [Memory Device (Type 17) - Length 27 - Handle 0018h]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    72 bits
      Size                          2048MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM2
      Bank Locator                  BANK2
      Memory Type                   13h - Specification Reserved
      Type Detail                   0080h - Synchronous
      Speed                         266MHz
      Manufacturer                  Manufacturer2
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum2
    [Memory Device Mapped Address (Type 20) - Length 19 - Handle 0019h]
      Starting Address              00200000h
      Ending Address                003fffffh
      Memory Device Handle          0018h
      Mem Array Mapped Adr Handle   0013h
      Partition Row Position        01
      Interleave Position           [None]
      Interleave Data Depth         [None]
    [Memory Device (Type 17) - Length 27 - Handle 001ah]
      Physical Memory Array Handle  0012h
      Memory Error Info Handle      [Not Provided]
      Total Width                   64 bits
      Data Width                    72 bits
      Size                          2048MB
      Form Factor                   09h - DIMM
      Device Set                    [None]
      Device Locator                DIMM3
      Bank Locator                  BANK3
      Memory Type                   13h - Specification Reserved
      Type Detail                   0080h - Synchronous
      Speed                         266MHz
      Manufacturer                  Manufacturer3
      Serial Number                        
      Asset Tag Number                          
      Part Number                   PartNum3
      My System SpecsSystem Spec

  5. #5


    Posts : 4
    Windows 8.1


    the 333Mhz is in fact DDR2 667. so the memory modules had good speed before. right?
      My System SpecsSystem Spec

  6. #6


    Posts : 4
    Windows 8.1


    I took two 2GB modules out. Now I have dual 2x1GB DDR2 667 and still get bsods. Don't have new dump files because it reboots before one is created.
      My System SpecsSystem Spec

  7. #7


    Posts : 660
    windows 8.1


    Here you can download the manual for your mainboard ASRock > Products > A770DE+ > Manual

    According to the manual you must have 4 identical memory modules.
    So you can not use your current set of 2 x 1gb and 2x 2gb at the same time.

    Dual Channel Memory Configurations
    DDRII_1 DDRII_2 DDRII_3 DDRII_4
    (Yellow) (Yellow ) (Orange) (Orange)
    (1) Populated Populated None None
    (2) None None Populated Populated
    (3)* Populated Populated Populated Populated
    *
    For the configuration (3), please install identical DDR2 DIMMs in all four slots


    So my advice would be to install your 2 2048 mb modules in the Yellow slot 1 and Yellow slot2.

    Because some of your dumpfiles mentioned memory corrption check your memory with memtest 86. for corruption. Download and info Memory Diagnostics.
    When after testing your memory has no errors and the system still has bsod , please post a new SF.zip.


    Please also remove Daemon tools from your computer.
    canned speech of John Carrona
    Daemon Tools (Alcohol %) removal:
    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ
    Analyse dumpfiles:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1E, {ffffffffc0000005, fffff8000047e88a, 0, ffffffffffffffff}
    *** WARNING: Unable to verify timestamp for PCIIDEX.SYS
    *** ERROR: Module load completed but symbols could not be loaded for PCIIDEX.SYS
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : PCIIDEX.SYS ( PCIIDEX+388a )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8000047e88a, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, 0, ffffd0002b86f6f8, ffffd0002b86ef00}
    Probably caused by : cdrom.sys ( cdrom!RequestSend+b2 )
    Followup: MachineOwner
    ---------
    1: 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: 0000000000000000, The address that the exception occurred at
    Arg3: ffffd0002b86f6f8, Exception Record Address
    Arg4: ffffd0002b86ef00, Context Record Address
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1E, {ffffffffc0000005, fffff8000026158b, 0, ffffffffffffffff}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    Followup: memory_corruption
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8000026158b, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff8029f861aaf, ffffd0002a407e60, 0}
    Probably caused by : ntkrnlmp.exe ( nt!KeAbPreAcquire+6f )
    Followup: MachineOwner
    ---------
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8029f861aaf, Address of the instruction which caused the bugcheck
    Arg3: ffffd0002a407e60, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    *******************************************************************************
    *                                                                             *
    *                        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: fffff80000207b3d, The address that the exception occurred at
    Arg3: ffffd00020832738, Exception Record Address
    Arg4: ffffd00020831f40, Context Record Address
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck C5, {8, 2, 0, fffff8010d312ffe}
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1ce )
    Followup: Pool_corruption
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is
    caused by drivers that have corrupted the system pool.  Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8010d312ffe, address which referenced memory
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0xC5_2
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!ExDeferredFreePool+1ce
    fffff801`0d312ffe 49394208        cmp     qword ptr [r10+8],rax
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME:  ffffd00029600540 -- (.trap 0xffffd00029600540)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe0000121a010 rbx=0000000000000000 rcx=ffffe0000121a000
    rdx=ffffe00002902010 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8010d312ffe rsp=ffffd000296006d0 rbp=0000000000000016
     r8=ffffe0000121a730  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!ExDeferredFreePool+0x1ce:
    fffff801`0d312ffe 49394208        cmp     qword ptr [r10+8],rax ds:00000000`00000008=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff8010d1db7e9 to fffff8010d1cfca0
    STACK_TEXT:  
    ffffd000`296003f8 fffff801`0d1db7e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`29600400 fffff801`0d1da03a : 00000000`00000000 00000000`00000000 fffffff6`00000000 ffffd000`29600540 : nt!KiBugCheckDispatch+0x69
    ffffd000`29600540 fffff801`0d312ffe : fffff801`0d359f80 fffff801`0d359f88 00000000`00140000 00000000`00000001 : nt!KiPageFault+0x23a
    ffffd000`296006d0 fffff801`0d313a03 : ffffe000`036aa800 ffffe000`034055f0 00000000`00000000 00000000`00000002 : nt!ExDeferredFreePool+0x1ce
    ffffd000`29600750 fffff800`0081c154 : ffffe000`02b9b1e0 ffffd000`296008c9 00000000`00011021 ffffe000`48706657 : nt!ExFreePoolWithTag+0x733
    ffffd000`29600820 fffff800`0081af46 : ffffe000`00e142d8 ffffe000`000f0032 00000000`0000000a fffff801`0d00ff00 : NETIO!KfdCommitTransaction+0x494
    ffffd000`29600930 fffff800`00c1df18 : 00000000`00000000 ffffe000`00b78640 00000000`0000ff00 ffffe000`03129908 : NETIO!IoctlKfdCommitTransaction+0x6e
    ffffd000`29600960 fffff801`0d42d3e5 : ffffe000`031298d0 ffffd000`29600cc0 00000000`00000001 ffffd000`00000001 : tcpip!KfdDispatchDevCtl+0xd8
    ffffd000`296009b0 fffff801`0d42dd7a : e00002b9`fffffffe ffffe000`ffffffff 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x845
    ffffd000`29600b60 fffff801`0d1db4b3 : 00000000`00000000 00000000`00000008 fffff6fb`7dbed008 fffff6fb`7da01088 : nt!NtDeviceIoControlFile+0x56
    ffffd000`29600bd0 00007ff9`cbec65ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000084`0098f518 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`cbec65ea
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+1ce
    fffff801`0d312ffe 49394208        cmp     qword ptr [r10+8],rax
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!ExDeferredFreePool+1ce
    FOLLOWUP_NAME:  Pool_corruption
    IMAGE_NAME:  Pool_Corruption
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  6.3.9600.16452
    MODULE_NAME: Pool_Corruption
    BUCKET_ID_FUNC_OFFSET:  1ce
    FAILURE_BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool
    BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0xc5_2_nt!exdeferredfreepool
    FAILURE_ID_HASH:  {0e971f5b-bd0d-a80e-a2c0-cd331176cf49}
    Analyse based on canned speech of John carrona;

    Out of 8 memory dumps there were 6different BSOD error codes. The differing error codes are usually symptomaticof a lower level problem within the system.
    They are usually caused by one of these things:

    - borked (broken) hardware (several different procedures used to isolate the problem device)

    - BIOS issues (check for updates at the motherboard manufacturer's website)

    - overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.

    - compatibility issues (3rd party hardware/drivers)

    - low-level driver problems


    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).





    Pleaseupdate these older drivers. Links are included to assist in looking up thesource of the drivers. If unable to find an update, please removinstall)the program responsible for that driver. DO NOT manually delete/rename thedriver as it may make the system unbootable.

    FNETURPX Sat Oct 04 04:27:02 2008 (48e6d476) 00010f39 FNETURPX.SYS
    Driver Description: FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package
    ASRock XFast USB

    AsrRamDisk Fri Jan 13 05:52:38 2012 (4f0fb896) 00016937 AsrRamDisk.sys
    Driver Description: ASRock RAM Disk Driver
    Driver Update Site: Download Files form ASRock Inc.


    viahduaa Mon Oct 22 10:11:15 2012 (5084ffa3) 0022503f viahduaa.sys
    Driver Description: VIA High Definition Audio Function Driver
    Driver Update Site: VIA Drivers Download - VIA Technologies, Inc.

    Rt630x64 Fri May 10 11:59:08 2013 (518cc4ec) 0009d8fe Rt630x64.sys

    Driver Description: Realtek PCI/PCIe Adapters
    Driver Update Site: Realtek

    dtsoftbus01 Thu Jun 20 09:22:51 2013 (51c2adcb) 00050ad5 dtsoftbus01.sys
    Driver Description: Daemon Tools driver
    Possible BSOD issues in Win7and windows 8 Please remove see above
      My System SpecsSystem Spec

every cold start BSODs
Related Threads
Random BSODs, some occure at start up, 7e,3b in BSOD Crashes and Debugging
I have been having blue screen problems for a while now. I originally thought it was RAM related but I tested with memtest and found no errors after 5+ passes on each stick on my old motherboard. Then I thought it was motherboard. So I got a new motherboard and reinstalled Windows. My PC has...
Hello! I cannot use programm as you recommended, because my windows gives bsod on start. I was playing DOTA2 (Steam) , then i got BSOD. I got bsods again and again after restarting computer, and trying to restore system. I have second system on this computer and can access any files on...
Hey There, I am new to this forum and I though this would be the best place to get some feedback with my problem im having, if anyone could give me some feedback that would be great! I have had Windows 8.1 64 bit in my computer for about two months now and everything was working fine..ive...
BSOD on cold start in BSOD Crashes and Debugging
Hi all, I'm wondering if any of you experts might have an idea why I'm experiencing BSOD on cold start. I had issues with Windows7 but experience the same after upgrading to Win8 Pro. Do you think a more general issue like insufficient power could be reason for those issues? Thanks in...
BSOD on Cold Boot (Please Help) in BSOD Crashes and Debugging
Hi I have built my own pc last week-(I5 3750k, Cm 212 Plus EVO, Gigabyte GA-Z77X-UD4H, Corsair 8Gb Vengeance LP, Corsair AX 850w, Windows 8 x64) It has been working fine until the last few days. :cry: I get BSOD dpc watchdog violation on start up. If i restart the system it some time goes to...
Hello i was trying to search for solution for few days now. Every time i start PC after giving him some rest it gives me a DRIVER_POWER_STATE_FAILURE. After that PC always works normal would be really glad if someone can explain me what is causing the error:huh:
Solved ...Memory cold not be read in General Support
Why when i try to shut down or restart sometimes appears ...memory could not be read?. And it stops the process. Thank You.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook