DAZ Loader brings blue screen of death. help please

Discussion in 'Windows 7' started by pamadhilwankalan, Dec 10, 2013.

  1. pamadhilwankalan

    pamadhilwankalan MDL Junior Member

    Nov 16, 2013
    92
    2
    0
    #1 pamadhilwankalan, Dec 10, 2013
    Last edited: Dec 10, 2013
    I have an assembled (non branded) pc. specifications are:
    motherboard: Intel
    processor: i3 3.10Gh
    BIOS VERSION: INTEL CORP. BEH6110H.86A.0016.2011.0118.1128
    SMBIOS VERSION: 2.6

    I downloaded a fresh win7 sp1 ultimate iso with 1 month trial. I installed and successfully updated windows7 through automatic mode. after that I applied daz loader. it activated my os with asus cert and asus slic table. now my pc often shows blue screen of death. mozila firefox crashes every time. internet explorer also crashes. pc starts and shuts down with BSOD. sometimes computer runs nicely for a long time i.e. 3 hours. please help
     
  2. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,577
    15,392
    340
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. pamadhilwankalan

    pamadhilwankalan MDL Junior Member

    Nov 16, 2013
    92
    2
    0
    I tried it 3 times. BSOD happens only after applying DAZ loader. windows runs nicely in trial mode
     
  4. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,577
    15,392
    340
    What are the errors shown in the dumps?? Btw, what is the exact mobo model (like DH61WW)??
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. pamadhilwankalan

    pamadhilwankalan MDL Junior Member

    Nov 16, 2013
    92
    2
    0
    mobo model is DH61WW_
     
  6. OldMX

    OldMX MDL Senior Member

    Jul 30, 2009
    421
    141
    10
    Attach the minidumps in a .zip file
     
  7. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,505
    300
    If the loader isn't actually installed and it's using your systems existing SLIC then it wouldn't ask you to reboot. If that's the case then it's not the loader that's causing the BSOD's since a certificate and key wouldn't cause such a problem.

    If the loader was installed then you'd select to disable type 4 memory or enable the legacy memory mode from the advanced tab.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. pamadhilwankalan

    pamadhilwankalan MDL Junior Member

    Nov 16, 2013
    92
    2
    0
    #8 pamadhilwankalan, Dec 11, 2013
    Last edited: Dec 11, 2013
    (OP)
    i don't know how to do mini dump. but here is txt file that tells the main 4 selected entries about the BSOD. now i think BSOD may be due to directX 10 i installed. not due to daz loader i think. i ran blue screen view program that showed the main upper 4 entries as below. please DAZ.....please Tito.....help.
    ==================================================
    File name : dxgkrnl.sys
    Address In Stack : dxgkrnl.sys+87bf9f4
    From Address : 0x8d8d8000
    To Address : 0x8d990000
    Size : 0x000b8000
    Time Stamp : 0x51fa113c
    Time String : 8/1/2013 1:11:48 PM
    Product Name : Microsoft® Windows® Operating System
    File Description : DirectX Graphics Kernel
    File Version : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
    Company : Microsoft Corporation
    Full Path : C:\Windows\system32\drivers\dxgkrnl.sys
    ==================================================

    ==================================================
    Filename : dxgmms1.sys
    Address In Stack : dxgmms1.sys+38df904
    From Address : 0x927b8000
    To Address : 0x927f1000
    Size : 0x00039000
    Time Stamp : 0x5164d8b5
    Time String : 4/10/2013 8:42:53 AM
    Product Name : Microsoft® Windows® Operating System
    File Description : DirectX Graphics MMS
    File Version : 6.1.7601.18126 (win7sp1_gdr.130409-1534)
    Company : Microsoft Corporation
    Full Path : C:\Windows\system32\drivers\dxgmms1.sys
    ==================================================

    ==================================================
    Filename : ntkrnlpa.exe
    Address In Stack : ntkrnlpa.exe+378ec
    From Address : 0x82a37000
    To Address : 0x82e4a000
    Size : 0x00413000
    Time Stamp : 0x521e9cb6
    Time String : 8/29/2013 6:28:30 AM
    Product Name : Microsoft® Windows® Operating System
    File Description : NT Kernel & System
    File Version : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
    Company : Microsoft Corporation
    Full Path : C:\Windows\system32\ntkrnlpa.exe
    ==================================================

    ==================================================
    Filename : win32k.sys
    Address In Stack : win32k.sys+1437af4
    From Address : 0x94c60000
    To Address : 0x94eb1000
    Size : 0x00251000
    Time Stamp : 0x521d4c8d
    Time String : 8/28/2013 6:34:13 AM
    Product Name : Microsoft® Windows® Operating System
    File Description : Multi-User Win32 Driver
    File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
    Company : Microsoft Corporation
    Full Path : C:\Windows\system32\win32k.sys
    ==================================================
     

    Attached Files:

  9. pamadhilwankalan

    pamadhilwankalan MDL Junior Member

    Nov 16, 2013
    92
    2
    0
    And Here Is Dump File
     

    Attached Files:

  10. oldpro21

    oldpro21 MDL Novice

    Sep 3, 2014
    1
    0
    0
    Hello all,

    I know this thread is old but I was having the same problem and I finally figured it out. I was having the problem on a Toshiba Laptop, a Satellite L355D-S7815. I had to update the bios to solve the issue. I noticed this in the bios update details:

    Description:
    Change History
    • Version 1.80 - 2009-09-17
      • Updated: SLP2.1 for Windows 7.

    I hope this helps someone. :)
     
  11. urie

    urie Moderator
    Staff Member

    May 21, 2007
    8,709
    3,066
    300
    @ oldpro21, no that would have nothing to do with the problem you had if you had not updated your bios at the time then you should have went to Advanced options tab and selected ignore existing SLIC since that would have been for Vista i,e SLIC 2.0 and when you updated your bios to SLIC 2.1 loader would not even install all it would do is install Toshiba certificate and OEM:SLP serial number. :rolleyes: