BSOD help please

[danbmx69]

system info
OVERCLOCKED AMD Phenom II X4 Quad Core 955 Black Edition 3.20GHz @ 3.60GHz / Gigabyte GA-MA790XT-UD4P Motherboard / Corsair XMS3 4GB (2x2GB)

Sapphire ATI Radeon HD 4850 X2 1024MB GDDR5 PCI-Express Graphics Card

Hiper 880W HPU-4M880 SLi Certified ATX 2.2 Power Supply

Asus Xonar HDAV1.3 Deluxe Sound Card

 

[zigzag3143]

system info
OVERCLOCKED AMD Phenom II X4 Quad Core 955 Black Edition 3.20GHz @ 3.60GHz / Gigabyte GA-MA790XT-UD4P Motherboard / Corsair XMS3 4GB (2x2GB)

Sapphire ATI Radeon HD 4850 X2 1024MB GDDR5 PCI-Express Graphics Card

Hiper 880W HPU-4M880 SLi Certified ATX 2.2 Power Supply

Asus Xonar HDAV1.3 Deluxe Sound Card

Pretty straight forward. All of these crashes except one were caused by your xonar sound driver (cmhdav.sys). I would download the newest/ fresh driver you can and re-install it.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\072410-21013-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`03248e50
Debug session time: Sat Jul 24 06:20:21.969 2010 (GMT-4)
System Uptime: 0 days 0:31:03.764
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, fffff880050183a7}

Unable to load image \SystemRoot\system32\drivers\cmhdav.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmhdav.sys
*** ERROR: Module load completed but symbols could not be loaded for cmhdav.sys
Probably caused by : cmhdav.sys ( cmhdav+43a7 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880050183a7, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b30e0
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
cmhdav+43a7
fffff880`050183a7 ff5008          call    qword ptr [rax+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c320 -- (.trap 0xfffff80000b9c320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880059911e0
rdx=fffff8800509f978 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880050183a7 rsp=fffff80000b9c4b0 rbp=0000000000000001
 r8=fffff80000b9c540  r9=11d333b5f0d71141 r10=fffff8000300b000
r11=fffffa8005a6e608 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cmhdav+0x43a7:
fffff880`050183a7 ff5008          call    qword ptr [rax+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000307ab69 to fffff8000307b600

STACK_TEXT:  
fffff800`00b9c1d8 fffff800`0307ab69 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1e0 fffff800`030797e0 : 00000000`00000000 fffffa80`05995210 fffff800`00b9c390 fffff880`0185a093 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c320 fffff880`050183a7 : fffff880`01969800 fffff880`0196dd40 fffff880`0196dd40 fffff880`0185a4b9 : nt!KiPageFault+0x260
fffff800`00b9c4b0 fffff880`01969800 : fffff880`0196dd40 fffff880`0196dd40 fffff880`0185a4b9 00000000`00000000 : cmhdav+0x43a7
fffff800`00b9c4b8 fffff880`0196dd40 : fffff880`0196dd40 fffff880`0185a4b9 00000000`00000000 fffff880`050165af : tcpip!Ipv6Global
fffff800`00b9c4c0 fffff880`0196dd40 : fffff880`0185a4b9 00000000`00000000 fffff880`050165af 00000000`00000001 : tcpip!Ipv6Global+0x4540
fffff800`00b9c4c8 fffff880`0185a4b9 : 00000000`00000000 fffff880`050165af 00000000`00000001 fffff880`018593e3 : tcpip!Ipv6Global+0x4540
fffff800`00b9c4d0 fffff880`050199a9 : fffff880`059911e0 fffffa80`05a6e660 00000000`00000001 fffff800`0308519a : tcpip!IppCompartmentSetTimeout+0xb9
fffff800`00b9c540 fffff880`059911e0 : fffffa80`05a6e660 00000000`00000001 fffff800`0308519a 00000000`00000000 : cmhdav+0x59a9
fffff800`00b9c548 fffffa80`05a6e660 : 00000000`00000001 fffff800`0308519a 00000000`00000000 fffff800`030876a6 : 0xfffff880`059911e0
fffff800`00b9c550 00000000`00000001 : fffff800`0308519a 00000000`00000000 fffff800`030876a6 fffff800`00b9c600 : 0xfffffa80`05a6e660
fffff800`00b9c558 fffff800`0308519a : 00000000`00000000 fffff800`030876a6 fffff800`00b9c600 fffffa80`00000000 : 0x1
fffff800`00b9c560 fffff800`03086a26 : fffffa80`05a6e5c8 00000000`0001d2af 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x15a
fffff800`00b9c5e0 fffff800`0308757e : 00000004`56e3dc1d fffff800`00b9cc58 00000000`0001d2af fffff800`031f9868 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`03086d97 : 00000001`9f1c66c1 00000001`0001d2af 00000001`9f1c6677 00000000`000000af : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03083dfa : fffff800`031f5e80 fffff800`03203c40 00000000`00000000 fffff880`0440652c : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cmhdav+43a7
fffff880`050183a7 ff5008          call    qword ptr [rax+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cmhdav+43a7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cmhdav

IMAGE_NAME:  cmhdav.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4adc2d51

FAILURE_BUCKET_ID:  X64_0xD1_cmhdav+43a7

BUCKET_ID:  X64_0xD1_cmhdav+43a7

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

 

[danbmx69]

the latest drivers are installed, i evan took the card out uninstalled the drivers and went back to on board sound and i was still getiing crashes

 

[danbmx69]

just had another crash now and the system was on idle

the file says
icrosoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072410-18969-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`0324de50
Debug session time: Sat Jul 24 12:22:32.287 2010 (UTC + 1:00)
System Uptime: 0 days 1:01:29.082
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+705d0 )

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

 

[Jonathan_King]

Could you please upload the dmp file for us?

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[danbmx69]

just botted in to safe mode unilstalled re booted and re installed the sound card driver so i shall see what happens

 

[danbmx69]

here is the most recent dump 12:23 to day

 

[ttran]

It's again point to the audio drivers, this time is portcls.sys. You have mentioned that you've update the driver, we will wait for next BSODs.
During the meantime, please remove any Virtual CD program such as Deamon tool or Alcohol 120%, they use sptd.sys, which I found in the loaded driver, well known for causing BSODs
Use this tool to remove sptd.sys: DuplexSecure - Downloads

Please update these drivers:

fffff880`01652000 fffff880`01659000   speedfan speedfan.sys Sun Sep 24 20:26:48 2006 (45168798) [COLOR=Blue]Speedfan[/COLOR]
fffff880`0102a000 fffff880`01045000   jraid    jraid.sys    Tue Nov 04 09:20:09 2008 (490FB159) [COLOR=Blue]JMicron RAID Driver[/COLOR]
fffff880`0809e000 fffff880`080a7000   gdrv     gdrv.sys     Sat Dec 06 07:57:14 2008 (4939CDEA) [COLOR=Blue]Update it or uninstall it, it is a component of Dynamic Energy Saver Advanced (not good to use while u overclock sth).[/COLOR]

In looking through your drivers, I see that you have AVG anti virus installed. AVG is known to cause BSOD, on some systems. I suggest that you uninstall it while trouble shooting using the uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it also >Info > Tool[FONT=&quot]. I recommend that you install MSE and make sure Windows Firewall is turned on.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.532\072410-18969-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`0324de50
Debug session time: Sat Jul 24 18:22:32.287 2010 (UTC + 7:00)
System Uptime: 0 days 1:01:29.082
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : portcls.sys ( portcls!CServiceGroup::ServiceDpc+59 )

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

Regard,

Tuan
[/FONT]

 

[zigzag3143]

If he is both running a raid with an old driver and is overclocking it is no wonder he keeps crashing.

jraid.sys fffff880`0102a000 fffff880`01045000 0x0001b000 0x490fb159 11/3/2008 22:20:09

 

[danbmx69]

thanks for all your help guys, ttran i shall get cracking on what you have said to do

 

[danbmx69]

avg and demon tools have now been uninstalled, runing a game as we speek to see if i get a BSOD

 

[danbmx69]

new dump file just crahed now

 

[ttran]

I don't have much experience with this new stop code, which is 113

STOP 0x00000113: VIDEO_DXGKRNL_FATAL_ERROR

dxgmms1.sys was blamed, please update your directx
Download details: DirectX End-User Runtime

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.485\072410-20732-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032a4e50
Debug session time: Sat Jul 24 20:01:46.927 2010 (UTC + 7:00)
System Uptime: 0 days 0:22:20.347
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 113, {4, fffff88006f86810, 0, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::Release+50 )

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

One more thing, I haven't seen sptd.sys removed. Please use the tool I provide to remove sptd.sys. Have u remove Deamon tool or Alcohol 120%???

Speedfan and grdv.sys need to be update as well, please update those, also consider Ken (Zigzag)'s advise in previous post

Regard,

Tuan

 

[danbmx69]

ok thank you will up date them, i dont quite understand what he means by this

If he is both running a raid with an old driver and is overclocking it is no wonder he keeps crashing.

jraid.sys fffff880`0102a000 fffff880`01045000 0x0001b000 0x490fb159 11/3/2008 22:20:09

what dose he mean by raid?

 

[ttran]

ok thank you will up date them, i dont quite understand what he means by this

If he is both running a raid with an old driver and is overclocking it is no wonder he keeps crashing.

jraid.sys fffff880`0102a000 fffff880`01045000 0x0001b000 0x490fb159 11/3/2008 22:20:09

what dose he mean by raid?

Hum..I'm not sure if I can give you good explanation, but in general, in this case, if you overclocked anything, please reset to default setting and update the driver I mentioned. As I said, the gdrv.sys is not good to run if you overclocked anything.

 

[danbmx69]

ok thank you will up date them, i dont quite understand what he means by this

If he is both running a raid with an old driver and is overclocking it is no wonder he keeps crashing.

jraid.sys fffff880`0102a000 fffff880`01045000 0x0001b000 0x490fb159 11/3/2008 22:20:09

what dose he mean by raid?

Hum..I'm not sure if I can give you good explanation, but in general, in this case, if you overclocked anything, please reset to default setting and update the driver I mentioned. As I said, the gdrv.sys is not good to run if you overclocked anything.[/i dont know how to turn back the clock in the bios as it was done when i bort it

 

[danbmx69]

new dump

 

[CarlTR6]

This dump points to a hardware problem specifically mentions a sound card driver, portcls.sys. This may or may not be the actual cause.

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_073110-16770-01.zip\073110-16770-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`0328ce50
Debug session time: Sat Jul 31 09:22:51.693 2010 (GMT-4)
System Uptime: 0 days 1:34:06.488
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800711c160, 2, 0, fffff880045c058f}

Probably caused by : portcls.sys ( portcls!CServiceGroup::ServiceDpc+63 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800711c160, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880045c058f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f70e0
 fffff8800711c160 

CURRENT_IRQL:  2

FAULTING_IP: 
portcls!CServiceGroup::ServiceDpc+63
fffff880`045c058f 488b1b          mov     rbx,qword ptr [rbx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8000451aae0 -- (.trap 0xfffff8000451aae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8007351cb0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880045c058f rsp=fffff8000451ac70 rbp=fffffa8005ddcf40
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
portcls!CServiceGroup::ServiceDpc+0x63:
fffff880`045c058f 488b1b          mov     rbx,qword ptr [rbx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030beb69 to fffff800030bf600

STACK_TEXT:  
fffff800`0451a998 fffff800`030beb69 : 00000000`0000000a fffff880`0711c160 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`0451a9a0 fffff800`030bd7e0 : fffff800`03035460 fffff880`0711c160 fffff800`030bbb20 fffff880`045bb270 : nt!KiBugCheckDispatch+0x69
fffff800`0451aae0 fffff880`045c058f : fffff800`03239e80 00000000`00000246 fffffa80`05ddcfa0 fffffa80`0711c160 : nt!KiPageFault+0x260
fffff800`0451ac70 fffff800`030cacdc : fffff800`03239e80 fffffa80`05ddcf60 00000004`e97ce43a 00000000`000000e0 : portcls!CServiceGroup::ServiceDpc+0x63
fffff800`0451acd0 fffff800`030c7dfa : fffff800`03239e80 fffff800`03247c40 00000000`00000000 fffff880`045c052c : nt!KiRetireDpcList+0x1bc
fffff800`0451ad80 00000000`00000000 : fffff800`0451b000 fffff800`04515000 fffff800`0451ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
portcls!CServiceGroup::ServiceDpc+63
fffff880`045c058f 488b1b          mov     rbx,qword ptr [rbx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  portcls!CServiceGroup::ServiceDpc+63

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: portcls

IMAGE_NAME:  portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc03

FAILURE_BUCKET_ID:  X64_0xD1_portcls!CServiceGroup::ServiceDpc+63

BUCKET_ID:  X64_0xD1_portcls!CServiceGroup::ServiceDpc+63

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

Enable Driver Verifier:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link:

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[danbmx69]

thank you

 

[CarlTR6]

I also found the driver sptd.sys on your system. This driver is up to date; but older versions of this driver are a known cause of BSOD's. I suggest that you uninstall Daemon Tools or Alcohol and then remove sptd with this tool - DuplexSecure - Downloads I believe Ttran already suggested you uninstall this.

In addition, you have some pre Win 7 drivers that need to be updated. If you need help please post.

AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipsetGlobal Provider of Innovative Graphics, Processors and Media Solutions | AMD

gdrv.sys Fri Dec 05 19:57:14 2008 - appears to be a driver for Gigabyte's Dynamic Energy Saver Advanced program.

jraid.sys Mon Nov 03 21:20:09 2008 - JMicron JR036X RAID Driver or JMicron JMB36X RAID Driver belongs to the software JMicron JR036X RAID Driver or JMicron JMB36X RAID Driver by JMicron Technology Corp.