Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Two Months of random, yet consistent, BSOD's


01 Sep 2011   #1

Windows 7 64Bit
 
 
Two Months of random, yet consistent, BSOD's

Hello, as the title says I have been have random BSOD's recently for the past two months and, for the 1st time, I feel unable to fix this problem myself and am in desperate need of help.

My system is a new build and has been fine since its construction at Christmas [by myself] until recently. For the past two months the system will randomly crash to a blue screen [usually with the screen going all..fuzzy].

I have ran MemTest for a few hours: O errors found.
I have tried updating numerous drivers [I still think this is the issue] to no avail.
I have tried using the windows debugger but I cant get it to stop telling me im using the wrong symbols.
I have ran 'WhoCrashed' and it just states its a ntoskrnl error.
Also scanned for HD errors and came up with nothing.


I am gutted at this and would be very grateful for your help.

System Specs:

OS Windows 7 64Bit
CPU AMD Phenom II 965 Black Edition
Motherboard ASUS M4A89GTD PRO - AMD 890GX
Memory Corsair 4GB 1600MHz CL9 DDR3 Memory Kit
Graphics Card(s) Sapphie HD6870
Sound Card CREATIVE - SoundBlaster Audigy SE 7.1-Channel Sound Card
Hard Drives Samsung F3 HD103SJ
PSU Corsair TX Series, 650 Watt, ATX, PS/2, Power Supply
Case NZXT Hades
Cooling Arctic Cooling Freezer 7 Pro Rev.2 CPU Cooler

My mouse is a Razer Lachesis Refresh & my Keyboard is a Steelseries Merc Stealth.


Im very new to this so If I have missed anything out or there is anything I should do please just say. Im determined to get this fixed. I have attached the NT6 and my Minidump folders for you to look at.

Thank You

My System SpecsSystem Spec
.

01 Sep 2011   #2

Windows 7 Ultimate x64
 
 

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\Windows_NT6_BSOD_jcgriff2\Windows_NT6_BSOD_jcgriff2\082311-27846-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eac670
Debug session time: Tue Aug 23 04:40:11.253 2011 (UTC - 6:00)
System Uptime: 0 days 0:11:08.829
Loading Kernel Symbols
..............................................WARNING: Unknown_Module_fffffa80_053362a0 overlaps Unknown_Module_fffffa80_05336040
.
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000002
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000002
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3039656332646164
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c9f8 -- (.exr 0xfffff80000b9c9f8)
ExceptionAddress: fffff80002cef2b2 (nt!KiTimerExpiration+0x00000000000000f2)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9caa0 -- (.trap 0xfffff80000b9caa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffbfa80049b5480 rbx=0000000000000000 rcx=fffff80002e5d1a8
rdx=0000000000000079 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cef2b2 rsp=fffff80000b9cc30 rbp=000000000000a779
 r8=fffffa8004986460  r9=00000000000000c6 r10=0000000000000079
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!KiTimerExpiration+0xf2:
fffff800`02cef2b2 48894808        mov     qword ptr [rax+8],rcx ds:1d28:fffbfa80`049b5488=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cdb5fe to fffff80002ce3c10

STACK_TEXT:  
fffff800`00b9bad8 fffff800`02cdb5fe : fffffa80`06e71950 00000000`00000000 fffff800`00b9c250 fffff800`02d0f830 : nt!KeBugCheck
fffff800`00b9bae0 fffff800`02d0f4fd : fffff800`02eed71c fffff800`02e2ac30 fffff800`02c67000 fffff800`00b9c9f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bb10 fffff800`02d0e2d5 : fffff800`02e2e0fc fffff800`00b9bb88 fffff800`00b9c9f8 fffff800`02c67000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bb40 fffff800`02d1f361 : fffff800`00b9c9f8 fffff800`00b9c250 fffff800`00000000 fffff800`02e59e80 : nt!RtlDispatchException+0x415
fffff800`00b9c220 fffff800`02ce32c2 : fffff800`00b9c9f8 00000001`8ea758d8 fffff800`00b9caa0 fffff800`02e5d1a8 : nt!KiDispatchException+0x135
fffff800`00b9c8c0 fffff800`02ce1bca : 00000000`00000000 fffffa80`05320400 fffffa80`05573900 fffffa80`053204b0 : nt!KiExceptionDispatch+0xc2
fffff800`00b9caa0 fffff800`02cef2b2 : 00000001`8ea5d238 fffff800`00b9cc58 00000000`0000a778 fffff800`02e5d188 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9cc30 fffff800`02cef167 : 00000000`8f8812c6 00000000`0000a779 00000000`8f8812c9 00000000`00000079 : nt!KiTimerExpiration+0xf2
fffff800`00b9ccd0 fffff800`02cdb96a : fffff800`02e59e80 fffff800`02e67cc0 00000000`00000000 fffff880`04202db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02cdb5fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------

0: kd> lmvm nt
start             end                 module name
fffff800`02c67000 fffff800`03250000   nt         (pdb symbols)          f:\symcache\ntkrnlmp.pdb\47F5C3BF9E0A493C9F63BB8F6413358B2\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: f:\symcache\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Wed Jun 22 20:53:23 2011 (4E02AAA3)
    CheckSum:         0055C228
    ImageSize:        005E9000
    File version:     6.1.7601.17640
    Product version:  6.1.7601.17640
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.1.7601.17640
    FileVersion:      6.1.7601.17640 (win7sp1_gdr.110622-1506)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
Missing image name, possible paged-out or corrupt data.
The dump shows OS corruption occurring:

Run memtest86 again: RAM - Test with Memtest86+

Run Full Diagnostics on HDD or SSD and if it passes continue to run:

Driver Verifier - Enable and Disable

this will tell you what driver is causing the issue when it blue screens..
My System SpecsSystem Spec
01 Sep 2011   #3

Windows 7 64Bit
 
 

Thanks for the reply. It BSOD in the middle of reading your post.

Ok so I ran chkdsk and it came up with no errors.

Chkdsk was executed in read-only mode on a volume snapshot.
Checking file system on C:
The type of the file system is NTFS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
414720 file records processed. File verification completed.
897 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
479930 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
414720 file SDs/SIDs processed. Cleaning up 190 unused index entries from index $SII of file 0x9.
Cleaning up 190 unused index entries from index $SDH of file 0x9.
Cleaning up 190 unused security descriptors.
Security descriptor verification completed.
32606 data files processed. CHKDSK is verifying Usn Journal...
36241720 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.
976657407 KB total disk space.
129260884 KB in 378142 files.
192996 KB in 32607 indexes.
0 KB in bad sectors.
547755 KB in use by the system.
65536 KB occupied by the log file.
846655772 KB available on disk.
4096 bytes in each allocation unit.
244164351 total allocation units on disk.
211663943 allocation units available on disk.

So I will go away and run the memtest using a USB. If it passes that, will I have to reinstall Windows 7? Or is it perhaps just a lone driver thats causing all of this?
My System SpecsSystem Spec
.


01 Sep 2011   #4

Windows 7 64b Ultimate
 
 

Actually, there are multiple dumps of a later date. The second to last, of the 27th, shows problems with your Graphical card drivers (or the card itself)

Check here for the latest drivers to be sure: ati driver

For some reason, you do not have all the logs required in the JCGriff upload. Please check and try again?

Also, check the drivers for your mouse etc. They are 2007... and can't see here if they are Windows 7 compatible. Check please. (Alpham164.sys and Alpham264.sys)

The dump before that (24th Aug) shows memory corruption... so do all the tests Seth advised..

Also, as an extra step to ruleout Windows 7 drivers vs third party vs HW... run in Safe Mode for a longer period of time. A PITA, I know.. but it might help...
My System SpecsSystem Spec
01 Sep 2011   #5

Windows 7 64Bit
 
 

Wow im stunned. I downloaded the mentest but this time put it on my USB stick...

It stopped completely on test 5 [at 49%] with 300,000 errors!

Im shocked. Does this mean my RAM is the culprit and needs returned to Corsair for a replacement?

I recently updated the drivers for my mouse from Razer's website...I wonder if that is the driver for my old mouse that I used for a month when I first built the computer?

I also hope my graphics card isn't dying. It plays games fine, the crash can be totally random. Nothing specific seems to cause it. I can game for 5 hours, go on the internet THEN it crashes. It was one of my first thoughts when this started so I have been updating its drivers. I will double check and make sure though.

Thanks for helping
My System SpecsSystem Spec
01 Sep 2011   #6

Windows 7 64b Ultimate
 
 

Test the ram sticks individually before final judgment...
My System SpecsSystem Spec
02 Sep 2011   #7

Windows 7 64Bit
 
 

Ok, now im even more disheartened. I spent today testing the RAM from my USB stick.

I tried both stick individually for two hours each and they both passed. I then tried them together...and they passed.

Thing is, my motherboard does display the red RAM error light when I turn the sytem on then it vanishes. When I tested one of the sticks I did get some bizarre 'overclocking failed' message and then nothing would respond but a reset put things back to normal.

Im really baffled. Why would it fail a test with both yesterday then pass them all today? Im desperate to get to the root of the problem with your help.

Thanks
My System SpecsSystem Spec
03 Sep 2011   #8

Windows 7 64b Ultimate
 
 

Sometimes a bad seating is/was the problem. Seat both well, check, do a memtest86 (4 passes at least i.e. 4 or more hours...) and if all is well, normal boot and see if you're ok....
My System SpecsSystem Spec
03 Sep 2011   #9

Windows 7 64Bit
 
 

Thanks for continuing to help.


I will run an extensive 4 hour test with both seated and see what happens then I'll report back and let you know.
My System SpecsSystem Spec
03 Sep 2011   #10

Windows 7 64Bit
 
 

Ok, so before I got to even run the test I was having a look about the internet for over an hour with no problems and then the screen fuzzs up and it crashes [no BSOD but same effect].

I have uploaded the new crash file, hopefully someone can look at it.

Thank You
My System SpecsSystem Spec
Reply

 Two Months of random, yet consistent, BSOD's




Thread Tools



Similar help and support threads for2: Two Months of random, yet consistent, BSOD's
Thread Forum
Random BSOD over last few months, tried debug on my own w/o luck BSOD Help and Support
Been getting random BSOD for months BSOD Help and Support
Solved Various BSODs are back, not consistent, seems random BSOD Help and Support
Random BSOD about a four months now BSOD Help and Support
Random [BSOD] for a few months BSOD Help and Support
Solved random BSOD, restarts for the past 2 months BSOD Help and Support
Random BSOD for the pass 3 months BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 03:06 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33