Tech Support Forum banner
Status
Not open for further replies.

BSOD_Windows7_Vista_v2.64_jcgriff2_.exe complains about Win7 OS

2K views 15 replies 3 participants last post by  Wrench97 
#1 ·
Hi,

I have downloaded both files (BSOD_Windows7_Vista_v2.64_jcgriff2_.exe and autoruns.exe) and when running as admin, it tells me:
Code:
23.10.2012 20:44:03,68

 * * *   H E L L O   from    jcgriff2   * * *
 * * *   H E L L O   from    jcgriff2   * * *
 * * *   H E L L O   from    jcgriff2   * * *


username                        Marco
Windows OS                      Windows_NT
Computer Name                   STUDIO1737
PC Brand

Processor Architecture          x86
Processor                       x86 Family 6 Model 23 Stepping 6, GenuineIntel
Number of Proc's                2



*********************************************************************

 This program is not supported on versions of Windows prior to Vista

*********************************************************************

Drücken Sie eine beliebige Taste . . .
My OS is Win7 Home Premium, 32 Bit, SP1, Build 7601.

It's a full retail version, originally installed on my harddisk, cloned to my SSD, deleted on the harddisk (now d:).
Computer is a Dell Studio 1737 laptop.

What did I miss here?
 
See less See more
#4 · (Edited)
Hi -

Please bring up an Admin CMD prompt -
START | type cmd.exe | RIGHT-click on "cmd.exe" | select "Run as Administrator" | paste the following commands in 1-by-1
Code:
[FONT=Lucida Console]
set x1=%userprofile%\documents\jcgriff2BSOD_10-23-2012

md "%x1%" & cd /d "%x1%"

systeminfo >"%x1%\systeminfo"

msinfo32 /nfo "%x1%\$msinfo32.nfo"

dxdiag /t "%x1%\dxdiag"

[/FONT]
That last one will appear to run quickly as control of the CMD screen is returned to you immediately. The output will show up in a few minutes.

Alll output filles are being written to a new folder in Documents called jcgriff2BSOD_10-23-2012

I'm writing a few more.. Please start with those.

Regards. .. .

jcgrifff2
 
#5 ·
Hi -

Keep the Admin CMD screen up or open another -
START | type cmd.exe | RIGHT-click on "cmd.exe" | select "Run as Administrator" | paste the following commands in 1-by-1
Code:
[FONT=Lucida Console]
   set x1=%userprofile%\documents\jcgriff2BSOD_10-23-2012

   cd /d "%x1%" & set > "%x1%\set1"

   wevtutil qe Application /c:50000 /rd:true /f:text >"%x1%\evtx_app.txt"

   wevtutil qe System /c:50000 /rd:true /f:text >"%x1%\evtx_sys.txt"

   driverquery /v >"%x1%\driverquery_verbose.txt"

  perfmon /report 

[/FONT]
The last command will bring the perfmon fille viewer up. Save as an HTML file.

The 2 wevtutil commands may take a minute or so EACH to run. CMD may appear to hang, but it is not.

Zip up the entire jcgriff2BSOD_10-23-2012 folder and attach.

Regards. .. .

jcgrifff2
 
#7 ·
From the 4 dumps 3 are the driver power state failure 0x09f and 1 a 0x50 PAGE_FAULT_IN_NONPAGED_AREA
All 4 dumps name a different process so there is little to pin it to.

One named is appliand.sys. This is a Applian Network Service driver
Another is Vboxnetadp.sys a VirtualBox Host-Only Network Adapter Driver

Lets see if Driver Verifier can pin it down
Follow the instructions here, make sure to set a restore point before enabling verifier, also if you do not have Windows disk create a Windows repair disk
http://www.techsupportforum.com/for...-windows-7-and-vista-bsod-related-473665.html




BSOD BUGCHECK SUMMARY

Code:
[font=lucida console]
Debug session time: Sun Oct 21 16:49:34.262 2012 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\102312-13447-01.dmp]
Bugcheck code 0000009F
Arguments: 

Arg1: 00000003, A device object has been blocking an Irp for too long a time

Arg2: 857e9340, Physical Device Object of the stack

Arg3: 83165ae0, Functional Device Object of the stack

Arg4: 8823bc40, The blocked IRP


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
MaxSpeed:     2400
CurrentSpeed: 2393
BiosVersion = A08
BiosReleaseDate = 11/25/2009
SystemManufacturer = Dell Inc.
SystemProductName = Studio 1737
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Oct 17 16:10:39.488 2012 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\101812-11980-01.dmp]
Bugcheck code 0000009F
Arguments: 

Arg1: 00000003, A device object has been blocking an Irp for too long a time

Arg2: 857c4640, Physical Device Object of the stack

Arg3: 8312aae0, Functional Device Object of the stack

Arg4: 86606f00, The blocked IRP


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
MaxSpeed:     2400
CurrentSpeed: 2393
BiosVersion = A08
BiosReleaseDate = 11/25/2009
SystemManufacturer = Dell Inc.
SystemProductName = Studio 1737
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Aug 19 07:09:39.089 2012 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\081912-23509-01.dmp]
Bugcheck code 00000050
Arguments: 

Arg1: fbd04180, memory referenced.

Arg2: 00000001, value 0 = read operation, 1 = write operation.

Arg3: 82444a19, If non-zero, the instruction address which referenced the bad memory

	address.

Arg4: 00000000, (reserved)


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
MaxSpeed:     2400
CurrentSpeed: 2393
BiosVersion = A08
BiosReleaseDate = 11/25/2009
SystemManufacturer = Dell Inc.
SystemProductName = Studio 1737
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Aug 27 02:54:32.178 2012 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\090412-8767-01.dmp]
Bugcheck code 0000009F
Arguments: 

Arg1: 00000003, A device object has been blocking an Irp for too long a time

Arg2: 857ef030, Physical Device Object of the stack

Arg3: 83174ae0, Functional Device Object of the stack

Arg4: 899034e8, The blocked IRP


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
MaxSpeed:     2400
CurrentSpeed: 2393
BiosVersion = A08
BiosReleaseDate = 11/25/2009
SystemManufacturer = Dell Inc.
SystemProductName = Studio 1737
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/font]
 
#11 ·
Follow up:

I have enabled Driver Verifier and stopped using Virtual Box, and I got no BSOD any more.

But when I use Virtual Box again, while shutting down the virtual machine, my screen gets corrupted (white with many colored small horizontal bars, mouse pointer still visible, computer frozen, no minidump).

Without Driver Verifier active, Virtual Box shutdown is fine.


For the future, I'll remember to shut down my virtual machine before hibernating (I only use it to compile freetz.org anyway).

Thanks for your help!
 
#14 ·
It's blamed on appliand.sys which is described as Applian Network Service/Applian Technologies APPLIAND helper driver.

Do you have a program called Replay Media Catcher 4 installed?
Do you use it?
These type of network services are problematic since they try to send and receive keep alive packets to maintain a connection even while windows is trying to shut down, sleep or hibernate.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top