[Ken Housiaux]

Hello, I'm new here but i heard from people that you might be able to solve my problem.

I have been getting random BSOD's whenever I use my computer. I can happen anytime when playing games, you tube or even just working with word and it is kinda starting to drive me crazy.

These are my sytem specs:

computer name: KENHOUSIAUX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8496668672 total
VM: 2147352576, free: 1931972608

I found this information through the aplication WhoCrashed.

On Sat 8-6-2013 11:37:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060813-17893-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF80002ED8F3F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 8-6-2013 11:37:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF80002ED8F3F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I also uploaded the dump file through C:/Windows/Minidump

Thx for your help in advance and i hope we are able to solve this problem, if you need anything else just tell me

 

[satrow]

Welcome to TSF, Ken!

One crash dump isn't usually enough on its' own to be very useful, please study then follow the BSOD Sticky to collect and upload the required data: http://www.techsupportforum.com/for...ons-windows-8-windows-7-and-vista-452654.html

In the current crash dump, I think I'm seeing evidence of interference with the IAStorDataMgrS <-- Intel Storage drivers. The only 'bad' driver I see loaded is the WinRing0x64.sys (7/26/2008) <-- the WinRing libraries are used by many different programs:
WinRing0x64.sys Sat Jul 26 14:29:37 2008 (488B26C1)
many different programs that center around the using of the WinRing libraries (RealTemp, Corsair Link2 (known BSOD issues w/Win8), Razer GameBooster, etc)
http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff80002ed8f3f}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

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

4: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff80002ed8f3f

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  IAStorDataMgrS

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ed51e9 to fffff80002ed5c40

STACK_TEXT:  
fffff880`009b9de8 fffff800`02ed51e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff880`009b9df0 fffff800`02ed36b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009b9f30 fffff800`02ed8f3f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff8c9`0a580830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8f


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
    fffff80002ed8eb2 - nt!SwapContext_PatchXSave+2

	[ 01:21 ]
    fffff80002ed8f96 - nt!SwapContext_PatchXRstor+2 (+0xe4)

	[ 09:29 ]
2 errors : !nt (fffff80002ed8eb2-fffff80002ed8f96)

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

 

[Ken Housiaux]

Hello Satrow, Thank you for your reply, really appreciated.

I'll make sure to follow the sticky, thank you for that.
Sorry I didn't have any other crash dumps as well I had the stupid idea to clean my pc after I had a BSOD so that caused removing my crashdumps, Anyways I haven't had any crashes for a few days now so that's a bit odd normally I get like one each day. But when another BSOD occurs I'll make sure to get as much information as possible and I will follow the steps to provide you that information.

Again thank you very much and sorry about my bad English It's not my native language.

 

[satrow]

Ken, there's no need to apologise for your English usage, it's probably better than mine and I live next door to them!

Well, I hope some miracle has happened and you don't get any more BSODs - but if you do, someone will be here and happy to help you out :grin:

 

[Ken Housiaux]

Hello I already opened a thread but I didn't show the files properly, my apologies for that.

Anyways I have received yet another Crash, this time it happened when I was watching YouTube.

Here are the dumps with the perfmon file(I am dutch so the perfmon was written in dutch, so I hope that when you open it it will be in English.)

Additional info:

computer name: KENHOUSIAUX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8496668672 total
VM: 2147352576, free: 1931120640

Thx in advance.

 

[Ken Housiaux]

Here are they in English, again my apologies