Recurring BSOD


  1. JBaxter
    Posts : 2
    Windows 7 Home Premium 64bit
       New #1

    Recurring BSOD


    Over the past 2-3 months has developed a problem with regular crashes. These are generally but not always associated with intensive applications like game-playing, though often the system will crash a few minutes after playing rather than during.

    The BSOD's show a variety of bugcheck codes and no one error seems to stand out but I'm new to this. I've followed the insructions at the top of the forum and attach the results from jcgriff2's app.

    The system is nearly a year old, running Windows 7 Home Premium 64bit. It's a custom build machine ordered over the internet. About 6 weeks ago I reinstalled the OS from the retail disc provided but this did not improve things.

    I hope someone can help me get this fixed. Thanks for your time.
      My Computer
    Quote Quote

  3. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #2

    I see some serious OS corruption:
    Code:
    g?          Mon Jul 13 21:27:36 2009 (4A5BDF08)
g?          Mon Jul 13 21:31:07 2009 (4A5BDFDB)
g?          Sat Jun 19 00:16:41 2010 (4C1C44A9)
    That represents the following:
    Code:
    hal.dll      Tue Jul 14 06:57:36 2009 (4A5BDF08)
kdcom.dll Tue Jul 14 07:01:07 2009 (4A5BDFDB)
ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
    When the NT Kernel driver corrupts, there's really not much hope for the OS to stay running!

    I suspect some hardware is causing this corruption. RAM is the most likely, though a CPU, motherboard, or even hard drive problem could also cause it.

    Test RAM first; see my guide: RAM - Test with Memtest86+

    Also run Prime95; both the Blend and Small FFTs test: https://www.sevenforums.com/tutorials...t-prime95.html

    Finally, test your hard drive. Use the manufacturer's tool SeaTools.

    ...Summary of the dumps:
    Code:
    
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 12 05:51:21.291 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:19.758
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wlmail.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`039620f0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`039620f0
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 10 17:23:13.231 2010 (UTC - 5:00)
System Uptime: 0 days 9:43:33.574
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`039620f0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`039620f0
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`039620f0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`039620f0
Probably caused by : Unknown_Image ( Unknown_Module_fffffa80_039620f0+1355998 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec  8 16:34:54.439 2010 (UTC - 5:00)
System Uptime: 0 days 0:10:14.906
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+103
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
*** WARNING: Unable to verify timestamp for g?
*** ERROR: Module load completed but symbols could not be loaded for g?
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec  7 15:48:00.252 2010 (UTC - 5:00)
System Uptime: 0 days 2:24:29.657
*** WARNING: Unable to verify timestamp for g?
*** ERROR: Module load completed but symbols could not be loaded for g?
Probably caused by : g?_ ( nt+70740 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec  6 08:00:13.433 2010 (UTC - 5:00)
System Uptime: 0 days 3:39:07.962
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MassEffect.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+100
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
*** ERROR: Module load completed but symbols could not be loaded for g?
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec  5 15:22:56.855 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:54.384
*** ERROR: Module load completed but symbols could not be loaded for g?
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : g?_ ( nt+779b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec  5 06:05:50.803 2010 (UTC - 5:00)
System Uptime: 0 days 0:39:18.270
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 07:49:59.131 2010 (UTC - 5:00)
System Uptime: 0 days 2:30:50.598
Probably caused by : ntkrnlmp.exe ( nt!ExInterlockedRemoveHeadList+36 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!ExInterlockedRemoveHeadList+36
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 02:45:07.487 2010 (UTC - 5:00)
System Uptime: 0 days 0:04:11.907
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  WMIADAP.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiRemoveAnyPage+13e
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 07:24:00.751 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:54.218
Probably caused by : ntkrnlmp.exe ( nt!SwapContext+11 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!SwapContext+11
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 07:21:11.111 2010 (UTC - 5:00)
System Uptime: 0 days 0:08:23.578
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  prime95.exe
FAILURE_BUCKET_ID:  X64_0xD1_nt!KiPageFault+260
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov  3 14:32:43.702 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:18.202
Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+4d3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiInsertPageInFreeOrZeroedList+4d3
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov  3 14:29:34.574 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:52.041
Probably caused by : volsnap.sys ( volsnap!VspTableCompareRoutine+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_volsnap!VspTableCompareRoutine+0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  1 04:57:22.217 2010 (UTC - 5:00)
System Uptime: 0 days 0:31:29.684
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer
    Quote Quote

  4. JBaxter
    Posts : 2
    Windows 7 Home Premium 64bit
    Thread Starter
       New #3

    Thanks for the quick response. I can see this is going to take some digging - preliminary tests with Memtest86+ turned up some odd results. Running the test as soon as the computer was switched on produced a block of errors, something like one test failing for all or most cases, after running for a few minutes. Restarting the test or running after the computer had been on for a short while produced no errors, though I haven't left it running for more than a couple of hours yet. I was able to reproduce this a couple of times.

    Prime95 ran for 2.5 hours with no errors on the 'blend' test but this was when the system was well and truly warmed up. I guess I'll try running this from 'cold' next.

    Meanwhile, I've seen recommendations that increasing memory voltage in the bios can help in some cases of slightly iffy memory. Do you have an opinion on this?
      My Computer
    Quote Quote

  6. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #4

    My opinion on increasing RAM voltages: I have seen it work once, maybe a few times. It's worth a shot, but don't hold your breath. 98/100 times, the only solution is to replace the RAM.
      My Computer
    Quote Quote

 

  Related Discussions
We have multiple conference rooms with resources in active directory so we can schedule meetings in the conference rooms. Recently, I'm not sure for how long, whenever someone creates a recurring event with no end date when you go into the event on the conference room calender it only shows...
Recurring BSOD
in BSOD Help and Support

Hello, I bought a new PC 2 months ago. On the 1st week, it started to do some BSOD. I then reinstalled my video card drivers and was able to be stable for ~1 week. Then the BSODs were back. I then ran memtest86+ for more than 32 hours on my 4x4GB sticks of RAM. I thought one stick was bad, but...
Recurring BSOD
in BSOD Help and Support

About a few days ago, I installed a new internal hard drive on my computer. Nothing bad has been happening until today. So far, I've gotten a BSOD about 3-5 times. First time, the screen said "irql not equal or less". That's been more or less coming back every time. Bad hard drive maybe? This is...
Recurring BSOD
in BSOD Help and Support

So this Happened 5 times already. I laptop crashes, but sometimes it works for days before crashing again, sometimes it crashes within 10 minutes after I logged in to my laptop. window 7 x64 OEM I had it for 1 yr, never even touched to OS, I only updated it when it needs to. The screen says...
Recurring BSOD
in BSOD Help and Support

Well, everything was going well with my new build from a few weeks ago, but at the beginning of the week I encountered my first BSOD. I've been getting 2-3 a day since then. I have attempted removing some of my software and checking for driver updates, etc., but to no success. I posted all my specs...
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 16:15.
Find Us