BSOD Windows Home Premium 64bit

Sorry. I meant to say uninstalled. I'm going to try the verify again.

Ok. I've done everything on the list. This is what happens at boot up with verify on. It just gets a blue screen at boot up and it closes so fast I can't even read it.

I cleared the Minidump folder and ran the program again. I'm not sure why they're the same...

Ok. I got it. Sorry for being such a noob. lol

Guy123 said:

Ok. I got it. Sorry for being such a noob. lol

Driver verifier caught HIDCLASS.SYS as the offending driver. I also noticed SPTD.SYS


For HIDCLASS you are going to need to

1-run a system file check to verify and repair system files.
SFC /SCANNOW Command - System File Checker

2- If that doesnt fix it (found errors but could not fix) do a repair install.

I also noticed you are running SPTD.SYS, which is a huge BSOD problem. used in daemon tools/alcohol120

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

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\111410-34616-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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`0308be50
Debug session time: Sat Nov 13 09:59:05.778 2010 (GMT-5)
System Uptime: 0 days 0:00:12.902
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff8800fe6c818, fffff9800a2e4dc0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff8800fe6c818, The address in the driver's code where the error was detected.
Arg3: fffff9800a2e4dc0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_23b

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23b

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`0fe6c818 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`0fe6c818 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff9800a2e4dc0

DEVICE_OBJECT: fffffa80076b13d0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff800030c2400 -- (!locks fffff800030c2400)

Resource @ nt!PiEngineLock (0xfffff800030c2400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff800030c2400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800033483dc to fffff80002ebe740

STACK_TEXT:  
fffff880`033770f8 fffff800`033483dc : 00000000`000000c9 00000000`0000023b fffff880`0fe6c818 fffff980`0a2e4dc0 : nt!KeBugCheckEx
fffff880`03377100 fffff800`0335247a : fffff800`033469f0 fffff880`0fe6c818 fffff980`0a2e4dc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03377140 fffff800`03353483 : 00000000`0000023b 00000000`c0000010 fffff980`0a2e4dc0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`03377190 fffff800`03353b42 : fffff980`0a2e4f20 fffff880`0fe6c818 00000000`00000000 fffff800`0304b440 : nt!VfErrorReport1+0x63
fffff880`03377230 fffff800`03348071 : fffffa80`07b3f1c8 00000000`00000001 00000000`00000000 fffff980`0a2e4f20 : nt!ViGenericVerifyIrpStackUpward+0x62
fffff880`03377260 fffff800`03354b2d : fffffa80`07776810 fffffa80`07b3f010 fffff980`0a2e4dc0 fffff980`0a2e4dc0 : nt!VfMajorVerifyIrpStackUpward+0x91
fffff880`033772a0 fffff800`0336650d : fffff980`0a2e4f20 fffff880`03377480 00000000`c0000010 fffff980`0a2e4f20 : nt!IovpCompleteRequest2+0xad
fffff880`03377310 fffff800`02ec0d26 : fffff980`0a2e4f23 fffff800`00000000 00000000`000000ff fffff880`00000005 : nt!IovpLocalCompletionRoutine+0x9d
fffff880`03377370 fffff800`0335e19f : fffff980`0a2e4dc0 fffff880`0fe76300 fffffa80`076b1500 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`03377450 fffff800`02ea4e22 : fffff880`00000013 fffff880`03377578 fffff980`0a2e4f20 fffffa80`076b1520 : nt!IovCompleteRequest+0x19f
fffff880`03377520 fffff880`0fe6cb17 : 00000000`00000000 fffffa80`076b1520 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`03377550 fffff880`0fe6c903 : 00000000`00000000 fffffa80`076b1520 fffff980`0a2e4dc0 fffff880`03377600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`03377590 fffff800`03364c16 : fffff980`00000002 fffff980`0a2e4dc0 00000000`00000002 fffff800`0336037e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`03377600 fffff800`03363c42 : fffff980`0a2e4f68 00000000`00000002 fffffa80`076b2190 fffffa80`077e3700 : nt!IovCallDriver+0x566
fffff880`03377660 fffff800`03364c16 : fffff980`0a2e4dc0 00000000`00000002 fffffa80`076b2040 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
fffff880`03377690 fffff800`03363d58 : fffff980`0a2e4dc0 fffffa80`076b2040 00000000`00000000 fffffa80`07b07180 : nt!IovCallDriver+0x566
fffff880`033776f0 fffff800`03363e42 : fffffa80`04f83e30 00000000`00000001 fffffa80`04f83e30 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`03377760 fffff800`03350faf : fffffa80`04f83b60 00000000`000007ff fffff800`02ffd5b8 fffff800`03255ea9 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`03377800 fffff800`02f72522 : fffffa80`04f83b60 00000000`00000000 ffffffff`ffffffff 00000000`00000016 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`03377830 fffff800`032a971c : fffffa80`04f83b60 00000000`00000001 00000000`00000000 00000000`00000002 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`03377860 fffff800`032ab314 : fffffa80`04f83b60 fffffa80`04f83b60 fffffa80`04f4e550 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`03377950 fffff800`032ab7fc : fffffa80`07407a20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x264
fffff880`03377bc0 fffff800`02fc0382 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`03377c10 fffff800`02ecb961 : fffff800`02fc0080 fffff800`03315e01 fffffa80`04f31000 00000000`00000421 : nt!PnpDeviceActionWorker+0x302
fffff880`03377cb0 fffff800`03162c06 : 00000000`00000000 fffffa80`04f31040 00000000`00000080 fffffa80`04f05040 : nt!ExpWorkerThread+0x111
fffff880`03377d40 fffff800`02e9cc26 : fffff880`0316a180 fffffa80`04f31040 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03377d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcbfd

FAILURE_BUCKET_ID:  X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

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

Ok, I've done all of that. The system file check didn't come up with any errors and I deleted daemon and used the driver remover too.

I still get an IO error when I boot with verifier on though. Also, when I run the perfmon report it says I have about 4gb of memory available but I have 6 installed. Is that a problem? Thanks a bunch for your help.

Guy123 said:

Ok, I've done all of that. The system file check didn't come up with any errors and I deleted daemon and used the driver remover too.

I still get an IO error when I boot with verifier on though. Also, when I run the perfmon report it says I have about 4gb of memory available but I have 6 installed. Is that a problem? Thanks a bunch for your help.

Love to read them but none were included in the upload try this method.

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.