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: Help, I'm taking heavy fire from BSOD's

28 May 2011   #1
Bly

Windows 7 Professional x64
 
 
Help, I'm taking heavy fire from BSOD's

As thread name says, I'm under heavy fire from BSOD's. The error messages appear to be random, as they change around a lot. I installed the OS about 1 month ago, and things have been bad ever since.

I am running Windows 7 professional, x64, retailed version.

These are my system specs:

Quote:
OCZ DDR3 PLATINUM XTC 4GB PC3-10666 (2X2GB) LOW VOLTAGE x2 (i.e 8 gb)
ASUS P8P67 PRO P67 S-1155 ATX *
COOLER MASTER GX ATX12V 2.3 750W
ASUS RADEON HD6950 2GB GDDR5 PCI-E DVI/HDMI/DP
WESTERN DIGITAL CAVIAR BLACK 1TB 7200RPM SATA/600 64MB
CORSAIR FORCE 2.5" 120GB SSD MLC
INTEL CORE I7 2600K 3.40GHZ 8MB S-1155
Im running with 2 screens,
Dell 1907FP (1280 x 1024)
Samsung TV (1920 x 1080)
I've run prime95 for an hour, it displayed 0 errors.

I've ran Memtest86+ for over a day (12+ passes), with 0 errors.

I've booted on each of my individual ram-sticks, and problem still occurs.

I fear this might be hardware related, as the system only seem to be unstable like this when i do a cold boot. After it has been running for 1-3 hours, the problem very rarely occur, but during the first 1-2 hours, its a repeating frequent hell.

I know about 10 seconds before the BSOD is about to occur, because launching new instances of programs and such doesn't work, and the programs I am already working with becomes unresponsive. Some times the CPU pops up to 100% making the system extremely slow, for no apparent reason, forcing a manual restart of the system.

I have removed fancy things such as the CD tray, special keyboards, special mouse and special headset, but the problem still occurs, so these do not appear to be of any importance to the issue at hand.

Attached is the documents retrieved when following the BSOD posting procedure as advertised by mods in several other threads.

My System SpecsSystem Spec
29 May 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Bly View Post
As thread name says, I'm under heavy fire from BSOD's. The error messages appear to be random, as they change around a lot. I installed the OS about 1 month ago, and things have been bad ever since.

I am running Windows 7 professional, x64, retailed version.

These are my system specs:

Quote:
OCZ DDR3 PLATINUM XTC 4GB PC3-10666 (2X2GB) LOW VOLTAGE x2 (i.e 8 gb)
ASUS P8P67 PRO P67 S-1155 ATX *
COOLER MASTER GX ATX12V 2.3 750W
ASUS RADEON HD6950 2GB GDDR5 PCI-E DVI/HDMI/DP
WESTERN DIGITAL CAVIAR BLACK 1TB 7200RPM SATA/600 64MB
CORSAIR FORCE 2.5" 120GB SSD MLC
INTEL CORE I7 2600K 3.40GHZ 8MB S-1155
Im running with 2 screens,
Dell 1907FP (1280 x 1024)
Samsung TV (1920 x 1080)
I've run prime95 for an hour, it displayed 0 errors.

I've ran Memtest86+ for over a day (12+ passes), with 0 errors.

I've booted on each of my individual ram-sticks, and problem still occurs.

I fear this might be hardware related, as the system only seem to be unstable like this when i do a cold boot. After it has been running for 1-3 hours, the problem very rarely occur, but during the first 1-2 hours, its a repeating frequent hell.

I know about 10 seconds before the BSOD is about to occur, because launching new instances of programs and such doesn't work, and the programs I am already working with becomes unresponsive. Some times the CPU pops up to 100% making the system extremely slow, for no apparent reason, forcing a manual restart of the system.

I have removed fancy things such as the CD tray, special keyboards, special mouse and special headset, but the problem still occurs, so these do not appear to be of any importance to the issue at hand.

Attached is the documents retrieved when following the BSOD posting procedure as advertised by mods in several other threads.

Memory corruption caused by an unknown driver since you have run memtest please run driver verifier to find which driver it isw


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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\052811-9048-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e94650
Debug session time: Sat May 28 12:00:14.124 2011 (GMT-4)
System Uptime: 0 days 0:38:39.951
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002cd19a9, 0, ffffffffffffffff}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

4: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cd19a9, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!SwapContext_PatchXRstor+c7
fffff800`02cd19a9 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efe100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x1E

PROCESS_NAME:  wmplayer.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d1a5d8 to fffff80002cced00

STACK_TEXT:  
fffff880`0b096498 fffff800`02d1a5d8 : 00000000`0000001e ffffffff`c0000005 fffff800`02cd19a9 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b0964a0 fffff800`02cce382 : fffff880`0b096c78 fffff880`009b3180 fffff880`0b096d20 fffffa80`09756b60 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0b096b40 fffff800`02cccc8a : fffffa80`09756b60 fffff880`0b096da0 00000000`0000a918 00000000`7ef92000 : nt!KiExceptionDispatch+0xc2
fffff880`0b096d20 fffff800`02cd19a9 : dffff800`02cd14da 00000000`00000000 00000000`00000000 fffff880`0b086000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0b096eb8 dffff800`02cd14da : 00000000`00000000 00000000`00000000 fffff880`0b086000 00000000`00000000 : nt!SwapContext_PatchXRstor+0xc7
fffff880`0b096ec0 00000000`00000000 : 00000000`00000000 fffff880`0b086000 00000000`00000000 00000000`00000000 : 0xdffff800`02cd14da


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002cd1803 - nt!SwapContext_PatchXSave+2
    [ 01:21 ]
    fffff80002cd18e4 - nt!SwapContext_PatchXRstor+2 (+0xe1)
    [ 09:29 ]
    fffff80002cd1aa3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf)
    [ 01:21 ]
    fffff80002cd1b86 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3)
    [ 09:29 ]
4 errors : !nt (fffff80002cd1803-fffff80002cd1b86)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------
Quote:
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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.
My System SpecsSystem Spec
30 May 2011   #3
Bly

Windows 7 Professional x64
 
 

Just ran verifier with the recommended settings; and surely enough, the system went haywire about 3 seconds after the background image was loaded. The BSOD stated something about drivers trying to corrupt my system, so it seems you were onto something there. I tried to boot in two times, so there are two minidumps in my attachement.
My System SpecsSystem Spec
.


30 May 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Bly View Post
Just ran verifier with the recommended settings; and surely enough, the system went haywire about 3 seconds after the background image was loaded. The BSOD stated something about drivers trying to corrupt my system, so it seems you were onto something there. I tried to boot in two times, so there are two minidumps in my attachement.
Both of these were Related to btath_lwflt.sys Blue Manager from Atheros. I would remove it to test or at least update and re-install it.

Both were also Related to Kone.sys Kone Gaming Mouse Driver from ROCCAT Ltd. I would re-install it as well

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\053011-12324-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e93650
Debug session time: Mon May 30 11:09:16.242 2011 (GMT-4)
System Uptime: 0 days 0:00:25.054
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {3c, 47474747000001a8, 0, 0}

Unable to load image Kone.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Kone.sys
*** ERROR: Module load completed but symbols could not be loaded for Kone.sys
Probably caused by : Kone.sys ( Kone+d6e )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000000000003c, ObReferenceObjectByHandle is being called with a bad handle.
Arg2: 47474747000001a8, bad handle passed in,
Arg3: 0000000000000000, object type,
Arg4: 0000000000000000, 0.

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


BUGCHECK_STR:  0xc4_3c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  KoneHID.EXE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031543dc to fffff80002ccdd00

STACK_TEXT:  
fffff880`0aaf22c8 fffff800`031543dc : 00000000`000000c4 00000000`0000003c 47474747`000001a8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0aaf22d0 fffff800`0316990f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0aaf2310 fffff880`069a6d6e : fffff980`1075eee0 00000000`00000000 fffffa80`0a445e20 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0xdf
fffff880`0aaf2360 fffff980`1075eee0 : 00000000`00000000 fffffa80`0a445e20 00000000`00000000 fffff880`069a88a8 : Kone+0xd6e
fffff880`0aaf2368 00000000`00000000 : fffffa80`0a445e20 00000000`00000000 fffff880`069a88a8 00000000`00000000 : 0xfffff980`1075eee0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Kone+d6e
fffff880`069a6d6e ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Kone+d6e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Kone

IMAGE_NAME:  Kone.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4940b9b4

FAILURE_BUCKET_ID:  X64_0xc4_3c_Kone+d6e

BUCKET_ID:  X64_0xc4_3c_Kone+d6e

Followup: MachineOwner
---------
My System SpecsSystem Spec
01 Jun 2011   #5
Bly

Windows 7 Professional x64
 
 

I've just reinstalled windows clean, did all the system updates, did NOT use the KONE mouse, just a simple one, so no need to install those drivers; also did not install any of the bluetooth drivers for my motherboard; but still the very same thing just happend.

Attached is the bsod info for this run around.
My System SpecsSystem Spec
01 Jun 2011   #6

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Bly View Post
I've just reinstalled windows clean, did all the system updates, did NOT use the KONE mouse, just a simple one, so no need to install those drivers; also did not install any of the bluetooth drivers for my motherboard; but still the very same thing just happend.

Attached is the bsod info for this run around.
This one was blamed on audiodg, It is known to have problems especicially when enhancements are being use like room virtualization. It often increases its memory use until it crashes.

I would untick all the enhancements and you might want to google the audiodg problem to see which possible solution fits best for your system.

We also have to start thinking hardware.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060111-17050-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c4d650
Debug session time: Wed Jun  1 10:59:05.314 2011 (GMT-4)
System Uptime: 0 days 0:22:34.142
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a5, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880012331d5 to fffff80002a87d00

STACK_TEXT:  
fffff880`060a8578 fffff880`012331d5 : 00000000`00000024 00000000`000c08a5 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`060a8580 fffff880`01232e28 : 00000001`00000000 00000000`00000000 00000000`00000000 00000200`00000000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`060a8680 fffff880`01142bcf : fffffa80`06e71368 fffffa80`06e71010 fffffa80`0797e010 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x8ba9
fffff880`060a8730 fffff880`011416df : fffffa80`071e2cb0 fffffa80`06ecc701 fffffa80`071e2c00 fffffa80`06e71010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`060a87c0 fffff800`02aafc25 : fffffa80`06e71030 fffffa80`073e7f20 fffffa80`06f82a30 fffff800`02bfae80 : fltmgr!FltpDispatch+0xcf
fffff880`060a8820 fffff800`02aaf6f9 : 00000000`00000001 00000000`00000001 fffffa80`06f82970 fffffa80`06f82970 : nt!IoPageRead+0x255
fffff880`060a88b0 fffff800`02a9607a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff680`000020b0 : nt!MiIssueHardFault+0x255
fffff880`060a8980 fffff800`02a85e2e : 00000000`00000001 00000000`00417000 00000000`77982501 00000000`00000000 : nt!MmAccessFault+0x146a
fffff880`060a8ae0 00000000`778a2f61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`001de0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778a2f61


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+155
fffff880`012331d5 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsPagingFileIo+155

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792f9

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

Followup: MachineOwner
---------
My System SpecsSystem Spec
06 Jun 2011   #7
Bly

Windows 7 Professional x64
 
 

Hi, and thanks for your time in helping me.

From the randomness of the error messages being thrown from Windows, I'm starting to realize this probably might be a hardware related issue indeed.

This is likely to be my last post in this thread, and attached with it is one final minidump. I would love it if you could analyse it and see if it has any valuable information within it.
My System SpecsSystem Spec
Reply

 Help, I'm taking heavy fire from BSOD's





Thread Tools



Similar help and support threads for2: Help, I'm taking heavy fire from BSOD's
Thread Forum
Solved Heavy Fire Afghanistan Side by Side Configuration error on install Gaming
BSOD while playing Mount and Blade with Fire and Sword BSOD Help and Support
BSOD doing anything heavy, error 0x7e BSOD Help and Support
BSOD under heavy load BSOD Help and Support
Solved BSOD while heavy browsing with multiple tabs BSOD Help and Support
BSOD from idle desktop to heavy gaming BSOD Help and Support
BSoD during heavy system load 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 06:49 AM.
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