random BSOD brand new g73jw win 7 ultimate 64bit fresh install

Page 1 of 7 123 ... LastLast

  1. Posts : 64
    windows 7
       #1

    random BSOD brand new g73jw win 7 ultimate 64bit fresh install


    i have only had the asus g73jw for 3 days now. i have gotten 2 BSOD since yesterday. first when i tried to rotate display (as soon as i clicked apply) then today when i was just browsing. im kind of worried now.

    attached are the dump file and xml file with the logs. below is what windows says is the issue after the restart.

    is it a hardware or driver issue? i hate BSODs, i used to get so many with my G1s. why do i keep buying Asus laptops?!

    anyone else having the similar issues?

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: d1
    BCP1: 0000000000000558
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF88004201120
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    The single dump file doesn't tell us much, but it does hint at network involvement.
    As such I'd suggest updating your wired and wireless networking drivers.

    Also, please update your webcam drivers to one that's more current (yours are from 2008)
    Please remove the ISODrive program as it's from 2007.

    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    http://www.carrona.org/memdiag.html (read the details at the link)
    http://www.carrona.org/hddiag.html (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)
    Beyond that, should the BSOD's continue, please run Driver Verifier according to these instructions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

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

    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"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - 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).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    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.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    Also, please provide us with this information: https://www.sevenforums.com/crashes-d...tructions.html

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Oct 20 16:48:30.745 2010 (UTC - 4:00)
    System Uptime: 0 days 15:20:43.807
    BugCheck D1, {558, 2, 0, fffff88004201120}
    *** 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
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    Bugcheck code 000000D1
    Arguments 00000000`00000558 00000000`00000002 00000000`00000000 fffff880`04201120
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  3. Posts : 64
    windows 7
    Thread Starter
       #3

    thanks for the reply, will follow your steps and post back. im gnna go ahead and update as many drivers as i can find. if bsod proceed. ill continue through the process.

    regards
      My Computer


  4. Posts : 64
    windows 7
    Thread Starter
       #4

    it happened again! will follow the steps to correctly post BSOD files. why is this happening with a new system!
      My Computer


  5. Posts : 64
    windows 7
    Thread Starter
       #5

    win 7 ultimate 64bit fresh install on new hardware (asus g73jw)
    BSOD happens randomly.

    attached are the files relating to the BSOD based on the steps in the link Usasma provided.

    thanks in advance!

    i doubt this is related , but it is very weird and has never happened to me. the computer randomly froze today, i had to forcefully shut it down for it to work.


    thanks in advance
    Last edited by homamkeh; 23 Oct 2010 at 17:41. Reason: added note about the freeze
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #6

    The BSOD's aren't Driver Verifier enabled (as I requested in my previous post).
    Please enable Driver Verifier and follow the directions above.

    Your webcam drivers are still outdated - as is the ISODrive program. Please uninstall it immediately!

    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 23 17:29:33.632 2010 (UTC - 4:00)
    System Uptime: 0 days 2:38:10.694
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
    BUGCHECK_STR:  0x1a_41201
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  VistaStartMenu
    Bugcheck code 0000001A
    Arguments 00000000`00041201 fffff680`00018478 a5a00001`a6b89847 fffffa80`14cf2570
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Oct 20 16:48:30.745 2010 (UTC - 4:00)
    System Uptime: 0 days 15:20:43.807
    BugCheck D1, {558, 2, 0, fffff88004201120}
    *** 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
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    Bugcheck code 000000D1
    Arguments 00000000`00000558 00000000`00000002 00000000`00000000 fffff880`04201120
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  7. Posts : 64
    windows 7
    Thread Starter
       #7

    could not find an update for the webcam driver.

    i uninstalled the iso program (after the above mentioned BSOD) , i am upgrading to a new one now.

    i updated the wireless, and intel chipset.

    i thought the driver verifier was to test for something wrong not that i had to have it enabled for the BSOD report to be meaningful. i will do it now.

    if i do it now, will it matter the the BSOD was before i enabled it?

    regards,
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    Yes it does matter. The Driver Verifier will stress your drivers. When it does this it will cause a BSOD that will (hopefully) identify the driver that's at fault. You have to upload that memory dump in order for us to see what it says (as there's several different possibilities).

    The possibilities are:
    - the BSOD identifies a 3rd party driver that's at fault
    - the BSOD identifies a Windows drivers that's at fault
    - the BSOD identifies another component as being at fault
    - it doesn't generate a BSOD
    - it generates a BSOD, but doesn't save a dump file

    But we're only stressing the 3rd party drivers, so any other result has to be interpreted.
      My Computer


  9. Posts : 64
    windows 7
    Thread Starter
       #9

    ok i followed the steps and enabled the verifier. i then restarted, got a BSOD on startup: "IRQL_NOT_LESS_OR_EQUAL". it said "Collecting data for crash dump" & "Initializing disk for crash dump" but it never started. so i shut it off, unplugged my external sound card (which i am suspicious of) and started windows normally. It actually made it in this time. windows started i see my desktop. i wait a couple of min as it is sloowww. I plug in the sound card, im using the lappy normally for a couple of min then all of a sudden another BSOD, it says "Ksaud.sys - address blah blah blah. it is stuck at initializing disk for cash dump

    so i shut it down forcefully, start windows normally while sound card plugged in. Same BSOD happened.

    so i shut it down forcefully, took out the sound card, and it makes it to my desktop again. the verifier is still enabled, i will keep it running for a while and see if i get the "ksaud" BSOD. although i think the ksaud is actually caused from the sound card. i will check the sound card driver. although i am sure it is updated.

    while the verifier was enabled, i ran "process explorer" and it caused a BSOD.

    i am now following the bsod posting steps and will upload the files when done

    does it matter how many BSOD i get, do they all show on the logs i will provide? or just the last one?



    please tell me what i should do next

    regards
    Last edited by homamkeh; 23 Oct 2010 at 20:04.
      My Computer


  10. Posts : 64
    windows 7
    Thread Starter
       #10

    here it is
      My Computer


 
Page 1 of 7 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 00:09.
Find Us