Random BSODs, problem with minidump file but not with kernel mem dump

Page 1 of 2 12 LastLast

  1. Posts : 8
    Win 7 (64)
       #1

    Random BSODs, problem with minidump file but not with kernel mem dump


    Hey, guys

    I have been having some odd behavior with my Win 7 (64) OS. First, I experienced several BSODs but no files were written to my windows\minidump directory. I made sure to have the Startup and Recovery settings selected (ie., Write an Event checkbox was selected and small memory dump was selected). But no memory dump file was ever created. I switched to kernel memory dump, and I think one was written, and should be reflected in the SF Diagnostic Tool report.

    Anyway, I simply want know what is causing the BSOD and how to fix it. And guidance will be greatly appreciated.

    OS Name Microsoft Windows 7 Home Premium
    Version 6.1.7601 Service Pack 1 Build 7601
    System Manufacturer ASUSTeK Computer Inc.
    System Model G74Sx
    System Type x64-based PC
    Processor Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, 2001 Mhz, 4 Core(s), 8 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. G74Sx.201, 4/27/2011
    SMBIOS Version 2.6
    Installed Physical Memory (RAM) 12.0 GB
    Total Physical Memory 12.0 GB
    Available Physical Memory 9.98 GB
    Total Virtual Memory 29.9 GB
    Available Virtual Memory 27.7 GB
    Page File Space 18.0 GB
    Page File C:\pagefile.sys


    Thanks!
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    There is no dump file in the zip you uploaded.

    Follow the tutorial Dump Files - Configure Windows to Create on BSOD, make windows create dumps at the subsequent crashes.

    At the same time, search in C:\Windows\Minidump manually. If there is any, upload those.
      My Computer


  3. Posts : 8
    Win 7 (64)
    Thread Starter
       #3

    Arc

    Thanks for the speedy reply. Here's the thing: I have followed the instructions to have the minidump file created. It never gets created. It's never in windows/minidump. Really odd. The path in the settings dialog box is also correct. I have the checkbox to create the file, and I have small memory dump selected. The odd thing: I changed the settings last night to have it create a kernel memory dump. When I saw the bluescreen, it said the kernel memory dump was created. Now that you've told me it wasn't in the zip file I sent, I ran searches for *.dmp on my machine and nothing. I am at a loss as to how to get these reports created. Any idea what's stopping them from being created and where to go from here?

    Thanks!
      My Computer


  4. Posts : 1,454
    Windows 7 ultimate x64
       #4

    1. The posted system logs are only till 3rd July 2012.
    Please go to event viewer directly and right click on the system logs and application logs and save it as .evtx file and upload here.

    2. Once you did the above .... clear the logs so that new event can be seen clearly.

    3. Disable the below from the startup.. Some version of this is known to cause BSOD.

    AirVideoServer c:\program files (x86)\airvideoserver\airvideoserver.exe
    4. Based on the uploaded logs .. i can see you had a bsod in 13th June 2012... Bugcheck 1a... which is a memory management error.. Though this may not be related to the recent BSOD's... its a good idea to do a memtest of each of your rams for each slot to rule out the possibility of bad RAM... one you upload the logs again ... i will check and advice accordingly.

    5. Though your paging files are in the system drive... its better to check if the setting on the virtual memory is set to system managed and point to system drive...( i know this is silly and you have already done it ..)

    6. Use this program and post a snapshot of the SMART value of your HDD's

    7. Disable or remove these network drive from Network connections for the time being (you can reenable it later once we finish troubleshooting)

    X: \\mybooklive\redcloud111
    Z: \\Base-station\wd 500

    Do these and let me know..so i can advice you the next steps.
      My Computer


  5. Posts : 8
    Win 7 (64)
    Thread Starter
       #5

    Centaur

    Thanks for the detailed instructions!

    1. Uploaded .evtx files
    2. okay, done
    3. okay, done
    4. memtest is good
    5. I verified it's set to system managed (it wasn't before. this is something i changed a few days ago in hopes my memory dump files would be written. i haven't had a bsod in a few days, though. weird)
    6. Uploaded a snapshot
    7. Disabled
      My Computer


  6. Posts : 1,454
    Windows 7 ultimate x64
       #6

    Memtest needs to be done for atleast 6 to 8 passes.... not just 1 pass

    Well just as i feared... look at those reading....your Current pending sector count and Uncorrectable sector counts both are above the threshold... which means you are having problem with you disk... if you also check your logs you can see lots of disk i/o errors... though these values are not very high ... thats an impending sign of danger... that also explain why you are not able to create the dumps...

    If its under warranty... get it replaced...

    Current Pending sector count means Count of "unstable" sectors (waiting to be remapped, because of read errors). If an unstable sector is subsequently read successfully, this value is decreased and the sector is not remapped. Read errors on a sector will not remap the sector (since it might be readable later); instead, the drive firmware should remember that the sector needs to be remapped, and remap it the next time it's written.[29] However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good. This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors.
    Uncorrectable sector counts means The total count of uncorrectable errors when reading/writing a sector. A rise in the value of this attribute indicates defects of the disk surface and/or problems in the mechanical subsystem.
      My Computer


  7. Posts : 8
    Win 7 (64)
    Thread Starter
       #7

    Centaur

    Damn! That sux. Thanks, though, for the head's up. I live over seas, and my Asus laptop just went past the year warranty.

    Anyway, it's a 750 gig drive with four partitions. I use one for the OS, and the others for my media server.

    Also, it looks like the errors are just in the C and D partitions. Would reformatting the partitions help, or even the entire drive? Is there any sort of utility I can run on it? If I can repair the drive it will be less of a headache than trying to get one sent here.

    Also, if the problem is just with C and D, would moving my media to E and F keep them safe, even if the drive fails?
      My Computer


  8. Posts : 1,454
    Windows 7 ultimate x64
       #8

    Red

    I presume you have 2 drives in your laptop... Since the drive that hold E and F is good... try installing windows 7 on that and using it. Try doing this and see if you still get any BSOD... as far as i can tell ... the problem should be resolved when you do this.

    You can try doing Chkdsk on the drive and look for errors.. and it should probably remap the sectors as Bad sectors.. when you check SMART values after this ... you would probably see the "Reallocated sector counts" showing some value.

    You could still use the problem drive... its just that ... there is no guarantee when this drive would give up on you, it might take weeks or maybe months before it happens...
      My Computer


  9. Posts : 8
    Win 7 (64)
    Thread Starter
       #9

    Centaur

    You are, in fact, correct. I have two 750 gig drives. It seems the damaged sectors are on the C: drive, which also has the D: partition. I have moved my media off D: to E:

    I have run memtest several times (so no RAM errors).

    Also, I have run chkdsk /f /r on both C: and D: and was told the drives are fine. This seems odd to me.

    Are there any tools for me to use to try to repair C: (and if not repair, at least format it or something to avoid the damage sectors)? I'd love to avoid the yellow warning sign in Crystaldisk.

    Thanks for the advice.
      My Computer


  10. Posts : 1,454
    Windows 7 ultimate x64
       #10

    there are tools like Spinrite, MHDD, and the like that are known to resolve problem with bad sectors.. again these are only helpful if you have surface errors where these programs write to bad sectors ... if the error is more physical ... then these tools are not good as well...

    As far as i Know...as soon as you see values in "Current Pending sector count" .. they are usually remapped and the values shown in "Reallocated Sector Counts"....But in your hdd this is not the case... the "Uncorrectable sector counts" are showing the same value as "Current Pending sector count" which is a sign of mechanical problem.

    Like you said the chkdsk is showing no errors... as the current pending sector count is zero. then how is windows going to know where the error lies ??


    hmm ok... since you backed up everything.... lets do some experimenting .....do a full format on the problem drive and then install windows on them... try using the system for a while and keep lookin at the SMART values as well as your logs... if you start seeing disk i/o errors... and again not able to produce dumps. etc then you have problems with the drive physically .. there is nothing much you can do abt it ...other than buying a new one .

    Let me Know
      My Computer


 
Page 1 of 2 12 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 06:16.
Find Us