locked
Windows 7 BSOD new system, ntoskrnl.exe RRS feed

  • Question

  • Hi all,

    I have seen similar problems on other posts, but thought I would list my specifics and see if there are any ideas.

     

    I just built the following system, everything is new. I have had BSODs from the beginning.  

    1. WD 500GB SATA (WD5000AVDS)
    2. A-DATA 8GB (4x2GB) (AX3U1600GB2G9-2G)
    3. AMD Athlon II x4 630
    4. Gigabyte HD 4850 (GV-R4850C-1GH)
    5. ASRock M3A770DE AM3 (flash to most recent bios v1.50, released 4-15-10)
    6. Win 7 64 bit Pro
    7. No other software is installed, just what cam on the Win 7 discs. Actually I do have BlueScreenView on there, but that's it.

    The longest stretch I have had without a BSOD was after flashing bios. During that time I did not turn the PC off for ~2wks. Then after a restart I got  BSOD multiiple times until I had to reinstall Win7 because nothing worked. Now the computer is having BSOD every hour or so even after reinstalls.

    Every time the dump file lists ntoskrnl.exe. I've ran the Windows memory diagnostic and it has not found any errors.

    (1)  052610-18531-01.dmp    5/26/2010 10:21:50 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00005005    fffff700`01080000    00000000`000003a4    00000000`000003e5    ntoskrnl.exe    ntoskrnl.exe+70600                    x64            4    15    7600    
    (2)  052610-17375-01.dmp    5/26/2010 8:29:56 AM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`03174a2f    fffff880`078120c0    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+70600                    x64            4    15    7600    
    052610-17156-01.dmp    5/26/2010 9:25:08 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00005003    fffff700`01080000    00000000`00000044    00000046`00000008    ntoskrnl.exe    ntoskrnl.exe+70600                    x64            4    15    7600    
    (3)  052610-16421-01.dmp    5/26/2010 8:49:26 AM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    00000000`00000000    00000000`00000002    00000000`00000001    fffff800`02ebbf0e    ntoskrnl.exe    ntoskrnl.exe+70600                    x64            4    15    7600    
    (4)  052110-26296-01.dmp    5/21/2010 8:51:44 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00005003    fffff700`01080000    00000000`00000044    00000046`00000008    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64            4    15    7600    
    (5)  052110-22156-01.dmp    5/21/2010 8:57:26 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff800`00000008    00000000`00000000    fffff800`02ecb95e    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64            4    15    7600    
    (6)  052110-17296-01.dmp    5/21/2010 9:04:36 PM    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY    0x000000fc    fffff8a0`068f0230    8b500001`f4300963    fffff880`03198e20    00000000`00000002    fltmgr.sys    fltmgr.sys+48ca                    x64            4    15    7600

     

     

    Thanks for any suggestions

    Wednesday, May 26, 2010 6:00 PM

Answers

  • Thanks for the suggestions, I'll try to isolate my memory problems like you suggest.

    Yeah, the memory issue is weird, to me at least. Last night I reset the memory settings to the default settings a (i.e. 9-12-12-30, voltage=auto). I then ran Memtest and the errors dissapeared. I booted up windows and everything ran fine. I turned the computer off for the night, turned it on htis morining and walked away. NOw, 4 hrs later, I login to windows, and I can see it crashed multiple times again, memory issues are back. Weird.

    Also, last night, I updated the Reatek driver like you suggested, and all other drivers available at ASRock's site.

    Latest dump files are below:

    http://cid-82861a01bc6d0e76.skydrive.live.com/browse.aspx/.Public/dump%5E_files

    Wednesday, June 2, 2010 4:50 PM

All replies

  • The details you provided and the characteristics of the bugchecks suggest you are experiencing memory corruption.

     

    This could be due to faulty hardware, or a buggy/incompatible driver.  When did the behavior start - any recent hardware or software changes?

    That you get the MEMORY_MANAGEMENT bugcheck may be an indication that your RAM is faulty, so probably start there first.  Cycle through your RAM modules, using only one or two at a time, to attempt to isolate one that may be faulty.  Double-check BIOS settings with respect to RAM timings and the like.  Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider checking with memtest86, since you already used WMD.

    Can you upload the contents of c:\windows\minidump your SkyDrive, and provide a link?

    For dealing with Blue Screens, general guidance follows:

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    For memory corruption cases such as you seem to be experiencing, it can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of  modules for a while, and see how things go. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're  using the latest BIOS.

    • Proposed as answer by No.Compromise Friday, May 28, 2010 11:03 AM
    Wednesday, May 26, 2010 6:54 PM
  • Thanks for the response.

    The dump files are here:    http://cid-82861a01bc6d0e76.skydrive.live.com/self.aspx/.Public/dmp%5E_files.zip

     

    I will try the suggestions you mentioned and post my results. Also it has been experiencing BSODs as soon as I installed Windows 7. Like I mentioned all the hardware listed above is new and there is no software installed.
    Thursday, May 27, 2010 12:10 AM
  • LUM.sys 2/2/2007 
    Rt64win7.sys 2/26/2009 

    What is LUM.sys?  Disable it, or check for an update. Then test the behavior.
    Also update rt64win7.sys (Realtek NIC driver) - it has been involved in situations similar to what you are experiencing.
    Thursday, May 27, 2010 12:46 AM
  • No.Compromise,

    Thanks for the help. I think I may have found the problem. I ran Memstest like you suggested and it came back with a ton of errors. While the test was running I noticed some of the memory parameters weren't the suggested values ( was 9-12-12-30, changed it to the suggested values of 9-9-9-24). However Memstest still found a lot of errors. So then I changed the voltage to 1.65V(I don't know what it was before) with the memory settings at 9-9-9-12 and then ran Memstest all night with no errors. Win7 has been running for ~5hrs so far with no BSODs. IE crashed once but I think that was because I just installed Adobe reader, and only that window running Adobe crashed.

     

    I'll report back in a few days if it is still stable or not.

     

    Thursday, May 27, 2010 7:01 PM
  • Problems are back again. The dump files can be found below:

    http://cid-82861a01bc6d0e76.skydrive.live.com/self.aspx/.Public/dump%5E_files%5E_31May.zip

    It was working well for quite awhile. I have rebooted it several times with no issues, until this morning. I turned it on before leaving for work, and just connected to it remotely now and noticed it had crashed twice. Any suggestions?

    I'll try Memtest again and see if an error appears this time.

    Monday, May 31, 2010 9:31 PM
  • Hi, you get the following BSOD:

    Bug Check 0x24: NTFS_FILE_SYSTEM

    The NTFS_FILE_SYSTEM bug check has a value of 0x00000024. This indicates a problem occurred in ntfs.sys , the driver file that allows the system to read and write to NTFS drives.

    The following actions might prevent an error like this from happening again:

    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors.

    Cause

    One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

    Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.


    To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.


    Please follow the suggestions. Does it solve the issue? Also make sure, you are using the latest version of your AntiVirus tools and chipset drivers.

    best regards
    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, May 31, 2010 10:02 PM
  • A quick scan of the drivers doesn't suggest any AV software is installed.

    However, the following "stale" drivers are still present:

    LUM.sys 2/2/2007
    Rt64win7.sys 2/26/2009 

    Again...

    What is LUM.sys? Disable it, or check for an update. Then test the behavior. Also update rt64win7.sys (Realtek NIC driver) - it has been involved in situations similar to what you are experiencing.

    Recent 0x24 bugchecks (NTFS_FILE_SYSTEM) that I've seen, have more likely been attributable to memory corruption than actual disk / filesystem problems.  Still, it would be good to run through the guidance Andre provided in relation to this type of bugcheck, especially since the nature of a bluescreen is an ungraceful shutdown.

    Monday, May 31, 2010 11:45 PM
  • Thanks guys,

    I had a few more crashes, they can be found here:

    http://cid-82861a01bc6d0e76.skydrive.live.com/browse.aspx/.Public/6-1-10%5E_dmp%5E_files?uc=2

    I will try the suggestions above and get back to you. Memtest hasn't found any errors. Also the crashes seem to occur when I boot and leave the system idle (without logging in). Because if I log on the system works fine, no crashes. It seems to only happen if I turn the PC on and then walk away.

     

    Tuesday, June 1, 2010 7:11 PM
  • The characteristics of the latest bugchecks (PAGE_FAULT_IN_NONPAGED_AREA and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED due to access violation) continue to suggest memory corruption is taking place.  Again, check lum.sys and rt64win7.sys for updates.
    Tuesday, June 1, 2010 8:27 PM
  • Yep, it seems like my memory problems are back. I am running Memtest right now and it is reporting errors again, with the same ram settings that previously reported no errors at all, that is 9-9-9-24 1.65V.

    Why would errors appear, disappear after I change the memory settings, and then reappear later with no bios changes?

    Wednesday, June 2, 2010 1:31 AM
  • The memory may be faulty, or some other component (e.g. motherboard) may be faulty.  Start with RAM, though - maybe see if you can get it RMAd. First double (triple?)-check that it is compatible with your motherboard.  

    Test each RAM module independently, and consider running with just one RAM module installed, to try to isolate/identify a specific pattern or associate the problems with a specific module. Cycle through the modules in this fashion.

    Wednesday, June 2, 2010 11:59 AM
  • Thanks for the suggestions, I'll try to isolate my memory problems like you suggest.

    Yeah, the memory issue is weird, to me at least. Last night I reset the memory settings to the default settings a (i.e. 9-12-12-30, voltage=auto). I then ran Memtest and the errors dissapeared. I booted up windows and everything ran fine. I turned the computer off for the night, turned it on htis morining and walked away. NOw, 4 hrs later, I login to windows, and I can see it crashed multiple times again, memory issues are back. Weird.

    Also, last night, I updated the Reatek driver like you suggested, and all other drivers available at ASRock's site.

    Latest dump files are below:

    http://cid-82861a01bc6d0e76.skydrive.live.com/browse.aspx/.Public/dump%5E_files

    Wednesday, June 2, 2010 4:50 PM
  • Latest dumps continue to suggest memory corruption (BAD_POOL_HEADER, MEMORY_MANAGEMENT, etc.).

    LUM.sys is still stale. LUM.sys 2/2/2007 

    Did you recently add CPU-Z?

    Wednesday, June 2, 2010 5:00 PM
  • I just ran Memtest through the first 4 tests, and no memory errors were reported, usually errors appear by then from my experience over the last few days. I haven't changed any BIOS settings since last night. I still think it is a memory issue though. Super weird.
    Wednesday, June 2, 2010 5:01 PM
  • Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test. 
    Wednesday, June 2, 2010 5:04 PM
  • Yeah I was wrong. shortly after my last reply I ran Memtest longer to test 5 and I got a lot of errors. I emailed A-DATA and ASRock and both said, as you have, to test each stick one at a time. A-DATA said they will gladly replace the memory if that is the issue. ASRock said to test the memory and then get back to them, they said it could be a MB issue.

    I'm away from the computer for a few days. I'll test the memory one stick at a time, and MB slots this weekend and post my results sometime this weekend.

    Thanks for all the help.

    Thursday, June 3, 2010 12:53 AM
  • Sounds like a good plan.
    Thursday, June 3, 2010 1:49 AM
  • I think it is working now. Here is what I found out:

    (1) I tested each stick one by one in the same slot.....all passed memtest

    (2) I tested each slot with the same stick......all slots passed

    (3) I tested two slots (A1 and A2 or B1 and B2) .... both pairs passed

    (4) I tested all 4 slots with memory installed ..... all passed

    (5) Windows ran fine for about a week ..... then it started crahsing again after a restart

    (6) ran memtest after crash ..... errors reported

    (7) replaced mother board ..... errors still there

    (8) replaced ram ..... errors dissappeared

     

    So it looks like I just had bad memory. The memory is still under warranty, so I plan on getting some new sticks and putting them on ebay, since the retail store won't take them back after 15 days.

     

    Thanks for all the help. If the computer crashes again I'll repost.

    Wednesday, June 16, 2010 5:26 AM
  • Thanks for the update! Intermittent problems like that are challenging since you keep having to recheck what you thought you knew!  Nice to hear things seem to have stabilized.
    Wednesday, June 16, 2010 10:25 AM