Windows 7 Keep Getting Random Crashing with ntoskrnl.exe

unrealluke

New Member
Joined
Jul 27, 2012
Messages
6
My PC crashes at random times, I have tried every thing I can think of to repair the problem.




AMD Phenom(tm) II X6 1090T Processor
Speed: 3210
Installed RAM: 16GB MB that runs at 1600mhz
NVIDIA GeForce GTX 560
Asus Crosshair IV Formula

I use kasperksy internet security.

I use a Razer Mouse and keyboard.
I have 2 Screens Running.
I use display fusion.

sfc /scannow (done no errors)
spybot, combofix and kasperksy (scans not a thing found)
Ccleaner and Glary Registry Repairs (done and fixed)
All drivers updated and checked with Driver Genius Professional Edition (done)
Scanned my HDD for Errors (done)
Ran a Memtest for Errors (done)
Reinstalled Windows (done)
Driver Verifier (done) (Random BSOD errors ntoskrnl.exe and wdf01000.sys - Windows 7 Forums)


Replaced Graphic Card because of over heating but error form before I placed it.

Ram is set to 1600MHz and 1.5v like the manufacturer website says.
 

Attachments

Solution
Hello there!

Seems like it might be related to VIA audio drivers VMfilt64.sys Link Removed please uninstall it and apply the latest update and install it. Also Razer Tarantula Keyboard Driver i.e. Lycosa.sys. Please reinstall that as well.

Bugcheck:

Code: 
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000003366, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 =...
Sort by date Sort by votes
Hello there!

Seems like it might be related to VIA audio drivers VMfilt64.sys Link Removed please uninstall it and apply the latest update and install it. Also Razer Tarantula Keyboard Driver i.e. Lycosa.sys. Please reinstall that as well.

Bugcheck:

Code: 
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000003366, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000309744e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c0100
 0000000000003366 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalSynchronizationObject+4e
fffff800`0309744e 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003b1da40 -- (.trap 0xfffff88003b1da40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000003366 rbx=0000000000000000 rcx=0000000000003339
rdx=fffff880076c3318 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000309744e rsp=fffff88003b1dbd0 rbp=0000000000000000
 r8=0000000000000000  r9=fffff880038a4180 r10=0000000000000100
r11=fffff80003240260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KiSignalSynchronizationObject+0x4e:
fffff800`0309744e 488908          mov     qword ptr [rax],rcx ds:2000:00000000`00003366=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003090769 to fffff800030911c0

STACK_TEXT:  
fffff880`03b1d8f8 fffff800`03090769 : 00000000`0000000a 00000000`00003366 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03b1d900 fffff800`0308f3e0 : fffff800`03382000 fffff880`01ab1000 fffff880`01ab0000 fffff880`076c3320 : nt!KiBugCheckDispatch+0x69
fffff880`03b1da40 fffff800`0309744e : fffff800`03532340 fffff800`03236d90 fffffa80`100df1e0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03b1dbd0 fffff800`03095846 : 00000000`00000000 fffffa80`100df1e0 00000000`00000000 fffff800`03236d90 : nt!KiSignalSynchronizationObject+0x4e
fffff880`03b1dc20 fffff880`061e1817 : fffff880`00000000 fffff980`00000008 fffff800`03236d00 fffffa80`108e52a0 : nt!KeSetEvent+0x106
fffff880`03b1dc90 fffff880`00000000 : fffff980`00000008 fffff800`03236d00 fffffa80`108e52a0 fffffa80`100df1e0 : VMfilt64+0x1817
fffff880`03b1dc98 fffff980`00000008 : fffff800`03236d00 fffffa80`108e52a0 fffffa80`100df1e0 fffff800`035322eb : 0xfffff880`00000000
fffff880`03b1dca0 fffff800`03236d00 : fffffa80`108e52a0 fffffa80`100df1e0 fffff800`035322eb fffffa80`100df1e0 : 0xfffff980`00000008
fffff880`03b1dca8 fffffa80`108e52a0 : fffffa80`100df1e0 fffff800`035322eb fffffa80`100df1e0 fffffa80`100df1e0 : nt!ViPendingWorkers
fffff880`03b1dcb0 fffffa80`100df1e0 : fffff800`035322eb fffffa80`100df1e0 fffffa80`100df1e0 fffff980`09245000 : 0xfffffa80`108e52a0
fffff880`03b1dcb8 fffff800`035322eb : fffffa80`100df1e0 fffffa80`100df1e0 fffff980`09245000 fffff980`09244ea0 : 0xfffffa80`100df1e0
fffff880`03b1dcc0 fffff800`0353236c : fffff800`03236d90 00000000`00000080 fffffa80`0c9f0040 d14b97cb`4890c700 : nt!ViPendingCompleteAfterWait+0x7b
fffff880`03b1dd00 fffff800`03327e6a : e9e9ace8`e8a3e7e7 ecc2ebeb`bbeaeab3 d3ededd2`ececccec ededd4ed`edd4eded : nt!ViPendingWorkerThread+0x2c
fffff880`03b1dd40 fffff800`03081ec6 : fffff880`03764180 fffffa80`0cac3660 fffff880`0376f040 ededb2e9`e9ade6e6 : nt!PspSystemThreadStartup+0x5a
fffff880`03b1dd80 00000000`00000000 : fffff880`03b1e000 fffff880`03b18000 fffff880`03b1da10 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VMfilt64+1817
fffff880`061e1817 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  VMfilt64+1817

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VMfilt64

IMAGE_NAME:  VMfilt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a7267b0

FAILURE_BUCKET_ID:  X64_0xA_VMfilt64+1817

BUCKET_ID:  X64_0xA_VMfilt64+1817

Followup: MachineOwner
 
Last edited:
Upvote 0 Downvote
Solution
I have Changed my audio driver and have uninstalled the keyboard driver and changed keyboard.

it took about 6 hours to crash and I got a error with win32k.sys I was using google chrome and java at the time.

also when i got back in to windows I had Kaspersky (previous application launch failed)
 

Attachments

Upvote 0 Downvote
im still getting BSOD here some more dumps

really need some help.

also does any one know any programs that can remove all drivers form my pc so its like when I installed windows?
 

Attachments

Upvote 0 Downvote
Hello there!

Reinstall your WiFi Adaptor i.e. http://sysnative.com/drivers/driver.php?id=yk62x64.sys also reinstall your nVidia display drivers as well.


BSOD BUGCHECK SUMMARY

Code: 
[font=lucida console]
Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\072912-20420-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 29 06:30:30.475 2012 (GMT+5)
System Uptime: 0 days 5:45:19.646
BugCheck 7F, {8, 80050031, 6f8, fffff96000158b82}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ts3client_win6
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff960`00158b82
BiosVersion = 3027   
BiosReleaseDate = 10/28/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Documents and Settings\Shyam\_jcgriff2_\dbug\__Kernel__\072912-23025-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 29 23:07:39.626 2012 (GMT+6)
System Uptime: 0 days 4:11:02.436
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : yk62x64.sys ( yk62x64+2080 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_yk62x64+2080
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 3027   
BiosReleaseDate = 10/28/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

M
  • Solved
Windows 8 Random BSOD with different types of error codes
2
Replies
26
Views
9K
kemical
  • Solved
Windows 7 BSOD error: 0x0000003b. Help needed
Replies
6
Views
3K
kemical
T
  • Solved
Windows 7 i keep getting random BSOD
Replies
1
Views
1K
Trouble
  • Solved
Windows 7 BSoD and random shutdowns/reboots
Replies
3
Views
3K
Oberst Hajj
B
  • Solved
Windows 7 Having trouble playing games, constant BSOD, random crashes at times
Replies
15
Views
4K
Vir Gnarus
V