Strange and unusual events..BSOD

[techjunkie2728]

Windows 7 BSOD
x64
This is the original installed OS
This is an OEM version of Windows 7 Home Premium

I purchased this hardware in January of this year
This OS installation is about two weeks old, I have recovered my system about 9 times because of a faulty recovery partition. These issues have been present since day 1 in January.

There are numerous issues, slow downs, lock ups, bsods, and errors that I cannot explain, HP is reluctant to properly fix their error. Can someone with some real expertise help me with these issues! Thank you very much!

 

[zigzag3143]

Windows 7 BSOD
x64
This is the original installed OS
This is an OEM version of Windows 7 Home Premium

I purchased this hardware in January of this year
This OS installation is about two weeks old, I have recovered my system about 9 times because of a faulty recovery partition. These issues have been present since day 1 in January.

There are numerous issues, slow downs, lock ups, bsods, and errors that I cannot explain, HP is reluctant to properly fix their error. Can someone with some real expertise help me with these issues! Thank you very much!

These were probably caused by sptd.sys which is part of a virtual drive software package. It needs to be moved

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



You also have a few old drivers needing update

000.fcl        fffff880`087c7000    fffff880`087f2000    0x0002b000    0x48dcdf7a    9/26/2008 09:11:22                        
vcsvad.sys        fffff880`05898000    fffff880`058a2000    0x0000a000    0x491fed16    11/16/2008 05:51:18                        
mcdbus.sys        fffff880`05cf7000    fffff880`05d33880    0x0003c880    0x49a3cd1f    2/24/2009 06:34:07                        
ahcix64s.sys        fffff880`01095000    fffff880`010e5000    0x00050000    0x49bf455b    3/17/2009 02:38:19

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5be50
Debug session time: Sat Oct 16 01:32:13.862 2010 (GMT-4)
System Uptime: 0 days 1:09:16.688
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c5877e, fffff8800a3a6e40, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c5877e, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a3a6e40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
fffff800`02c5877e f00fba3100      lock btr dword ptr [rcx],0

CONTEXT:  fffff8800a3a6e40 -- (.cxr 0xfffff8800a3a6e40)
rax=fffffa80072c2200 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80072c2200 rsi=00000000ffffffff rdi=fffffa80072c2200
rip=fffff80002c5877e rsp=fffff8800a3a7810 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=00000000000033f0
r11=fffff8800a3a7860 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=fffff900c43a29f0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26:
fffff800`02c5877e f00fba3100      lock btr dword ptr [rcx],0 ds:002b:00000000`00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Crysis.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c5877e

STACK_TEXT:  
fffff880`0a3a7810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26


FOLLOWUP_IP: 
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
fffff800`02c5877e f00fba3100      lock btr dword ptr [rcx],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff8800a3a6e40 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26

BUCKET_ID:  X64_0x3B_nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26

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

 

[techjunkie2728]

hello

Thank you for the help! I haven't done anything as of yet, but I was wondering, how do I go about updating those drivers?

 

[zigzag3143]

Thank you for the help! I haven't done anything as of yet, but I was wondering, how do I go about updating those drivers?

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