Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD help please

24 Jul 2010   #11

windows 7
 
 

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


My System SpecsSystem Spec
.

24 Jul 2010   #12

windows 7
 
 

new dump file just crahed now
My System SpecsSystem Spec
24 Jul 2010   #13

Microsoft Window 7 Professional 32 bit
 
 

I don't have much experience with this new stop code, which is 113
Quote:
STOP 0x00000113: VIDEO_DXGKRNL_FATAL_ERROR


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

Code:
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
My System SpecsSystem Spec
.


24 Jul 2010   #14

windows 7
 
 

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?
My System SpecsSystem Spec
24 Jul 2010   #15

Microsoft Window 7 Professional 32 bit
 
 

Quote   Quote: Originally Posted by danbmx69 View Post
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.
My System SpecsSystem Spec
24 Jul 2010   #16

windows 7
 
 

[QUOTE=ttran;860064]
Quote   Quote: Originally Posted by danbmx69 View Post
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
My System SpecsSystem Spec
31 Jul 2010   #17

windows 7
 
 

new dump
My System SpecsSystem Spec
31 Jul 2010   #18

Windows 7 Ultimate 32 bit
 
 

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

Quote:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver
Code:
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*Symbol information
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:

Quote:
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:

My System SpecsSystem Spec
31 Jul 2010   #19

windows 7
 
 

thank you
My System SpecsSystem Spec
31 Jul 2010   #20

Windows 7 Ultimate 32 bit
 
 

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.


My System SpecsSystem Spec
Reply

 BSOD help please




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:02 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33