windows 7 crashes after few minute

[sax]

Hello,
it is almost a week I am facing a problem with windows 7. After few minutes I logon I got the blue screen and a reboot.

If I logon in safe mode with network I don't have any problem (so I guess not be a HW problem).

I run the HP HW diagnositcs but everythings seems to be ok.

I tried to reinstall the nvidia driver but I did not work.

I did not install new driver, new program, what happened was that one day I switch-off my laptop and start facing the problem.

I have been spent a week to looking for a solution but nothing seem to work.

I installed whoCrashed but the information I got are useless because it reports ntoskrln.exe as likely caused but no info about the driver the caused the problem


This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFF80003400C40, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\100410-39468-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


I run PowerSuite, but it did not resolve.

The OS is original installed by HP.

Could you please help me

I run the exe I have downloaded from you site and put the result in the attached file

Thanks in advanced

 

[zigzag3143]

Hello,
it is almost a week I am facing a problem with windows 7. After few minutes I logon I got the blue screen and a reboot.

If I logon in safe mode with network I don't have any problem (so I guess not be a HW problem).

I run the HP HW diagnositcs but everythings seems to be ok.

I tried to reinstall the nvidia driver but I did not work.

I did not install new driver, new program, what happened was that one day I switch-off my laptop and start facing the problem.

I have been spent a week to looking for a solution but nothing seem to work.

I installed whoCrashed but the information I got are useless because it reports ntoskrln.exe as likely caused but no info about the driver the caused the problem


This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFF80003400C40, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\100410-39468-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


I run PowerSuite, but it did not resolve.

The OS is original installed by HP.

Could you please help me

I run the exe I have downloaded from you site and put the result in the attached file

Thanks in advanced

These were all virtally identical. they were caused by VBoxNetAdp.sys This file is from Sun Microsystems, Inc. and belongs to product Sun VirtualBox.

I would remove the offending app and driver to test

You also have some really old driver from circa 2005. They need updating.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

drivers

iirsp.sys        fffff880`017aa000    fffff880`017bb000    0x00011000    0x439f418a    12/13/2005 17:47:54                        
nfrd960.sys        fffff880`018b5000    fffff880`018c5000    0x00010000    0x4485ef94    6/6/2006 17:11:48                                               
adpu320.sys        fffff880`01650000    fffff880`0167f000    0x0002f000    0x45e4c6ff    2/27/2007 20:04:15                        
adpahci.sys        fffff880`0127b000    fffff880`012d1000    0x00056000    0x46377921    5/1/2007 13:30:09                        
arc.sys        fffff880`016ef000    fffff880`01708000    0x00019000    0x4656035b    5/24/2007 17:27:55                        
ads3kv48.SYS        fffff880`05200000    fffff880`05279000    0x00079000    0x46a7f398    7/25/2007 21:06:32                        
SiSRaid2.sys        fffff880`01bc5000    fffff880`01bd3000    0x0000e000    0x48da86c4    9/24/2008 14:28:20                        
000.fcl        fffff880`0823f000    fffff880`0826a000    0x0002b000    0x48dcdf7a    9/26/2008 09:11:22                        
sisraid4.sys        fffff880`01bd3000    fffff880`01beb000    0x00018000    0x48e3f1f4    10/1/2008 17:56:04                        
adp94xx.sys        fffff880`01200000    fffff880`0127b000    0x0007b000    0x4939bf42    12/5/2008 19:54:42                        
lsi_fc.sys        fffff880`017bb000    fffff880`017da000    0x0001f000    0x493ef531    12/9/2008 18:46:09

DMP

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\011610-27596-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
WARNING: Whitespace at end of path element
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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`03288e50
Debug session time: Sat Jan 16 16:12:22.290 2010 (GMT-4)
System Uptime: 0 days 0:37:00.492
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8003d61bb0, fffff80000b9c518, fffffa80074c3e10}

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

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8003d61bb0, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80074c3e10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80074c3e10

DEVICE_OBJECT: fffffa800666a050

DRIVER_OBJECT: fffffa800597fb70

IMAGE_NAME:  VBoxNetAdp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b2a38e9

MODULE_NAME: VBoxNetAdp

FAULTING_MODULE: fffff88006a61000 VBoxNetAdp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000312be23 to fffff800030bcf00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0312be23 : 00000000`0000009f 00000000`00000003 fffffa80`03d61bb0 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`030c8fa6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`030c8326 : fffff800`0326b700 00000000`00022c02 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`030c8e7e : 00000005`2b845601 fffff800`00b9cc58 00000000`00022c02 fffff800`032382c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030c8697 : 00000000`ce55b5c2 00000000`00022c02 00000000`ce55b5a8 00000000`00000002 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030c56fa : fffff800`03235e80 fffff800`03243c40 00000000`00000001 fffffa80`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_VBoxNetAdp.sys

BUCKET_ID:  X64_0x9F_IMAGE_VBoxNetAdp.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8003d61bb0, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80074c3e10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80074c3e10

DEVICE_OBJECT: fffffa800666a050

DRIVER_OBJECT: fffffa800597fb70

IMAGE_NAME:  VBoxNetAdp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b2a38e9

MODULE_NAME: VBoxNetAdp

FAULTING_MODULE: fffff88006a61000 VBoxNetAdp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000312be23 to fffff800030bcf00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0312be23 : 00000000`0000009f 00000000`00000003 fffffa80`03d61bb0 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`030c8fa6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`030c8326 : fffff800`0326b700 00000000`00022c02 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`030c8e7e : 00000005`2b845601 fffff800`00b9cc58 00000000`00022c02 fffff800`032382c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030c8697 : 00000000`ce55b5c2 00000000`00022c02 00000000`ce55b5a8 00000000`00000002 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030c56fa : fffff800`03235e80 fffff800`03243c40 00000000`00000001 fffffa80`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_VBoxNetAdp.sys

BUCKET_ID:  X64_0x9F_IMAGE_VBoxNetAdp.sys

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

 

[sax]

Thanks zigzag for the fast analisys.
Well, the first thing I have done is to remove the virtualBox and the behaviour seemed to be ok, when after about 2 hours I got another crash. But this time the error is different: UNEXPECTED_KERNEL_MODE_TRAP
I am going to looking for the new driver (I have always been done using windows update, but you suggested to do manually, so I need a little time to complete the task).
Meanwhile, I have attached the last minidump, if you can have a look, just to know where is the problem, I go on working in safe mode to update the drive.
Thanks a lot for support me, in this forum I see you guys are very good .
Bye

 

[sax]

I have done it

Hello,
finally I resolved the problem. I want to post a little report just in case someone can find it useful.

First I had a BSOD after few minute I logged in and the error was DRIVER_VERIFIER_DETECTED_VIOLATION, module ntoskrnl.exe.
First thing is to run HD check (RAM, HD), I had done it but I had no error . So I posted my problem here (a very good idea) and zigzag very quickly gave me the solution: deinstall SunViirtualBox (I miss it and I looking for a solution, cause I think it is a very good product). After that I got another error: UNEXPECTED_KERNEL_MODE_TRAP . This time zigzag did not give me a quick answer (I suppose he is very busy in this forum people post problems restless ). I serfed around and I read a problem with AVG and ZoneAlarm. I deinstalled ZA, and resolve my problem.

Thanx
Good luck