Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

System Service Exception BSOD Sony Vegas


  • Please log in to reply

#16
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

Newer drivers are not always better and drivers should not be updated unless the update is intended to resolve an issue that your computer has, if you do install the update when it is not required you will more often than not end up with the very issue that the update is intended to resolve, The Golden Rule of Drivers: If It Ain't Broke, Don't Fix It try installing drivers that are dated before the first time that the issue happened.

 

Your dxdiag report shows that among other things you have memory leakage ( Event Name: RADAR_PRE_LEAK_WOW64 ) Event Name is telling you that Windows handled the leak, this may be nothing at all to do with the present issue but it does also need checking, run Windows own memory test as a starting point, details here depending on the results you may need to run Memtest 86+ for 5 or 6 passes.


  • 0

Advertisements


#17
KELLER1224

KELLER1224

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts

Here is another dump file for good measures

Attached Files


  • 0

#18
KELLER1224

KELLER1224

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts

So i installed some older nvidia drivers and i didnt blue screen. instead, i white screened. My computer just completely white screened. I will try some different drivers.


  • 0

#19
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

The latest crash dump is showing the same cause as the last, have you completed the suggestions made in reply #16.

 

Is Windows fully up to date.

 

Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Machine Name:
Kernel base = 0xfffff801`2e886000 PsLoadedModuleList = 0xfffff801`2eb502d0
Debug session time: Sun May 25 09:31:36.151 2014 (UTC - 4:00)
System Uptime: 0 days 20:10:36.679
*******************************************************************************
* *
* 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: fffff8012e957c1c, Address of the instruction which caused the bugcheck
Arg3: ffffd00022e4aa70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

FAULTING_IP:
nt!KxWaitForLockOwnerShipWithIrql+14
fffff801`2e957c1c 48890a mov qword ptr [rdx],rcx

CONTEXT: ffffd00022e4aa70 -- (.cxr 0xffffd00022e4aa70)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd00022e4b4f0
rdx=0080000000000000 rsi=ffffe000f75c2600 rdi=ffffd00022e4b4f0
rip=fffff8012e957c1c rsp=ffffd00022e4b4a0 rbp=ffffd00022e4b510
r8=ffffd00022e4b540 r9=7fffc001b2f13510 r10=7ffffffffffffffc
r11=ffffd00022e4b7f0 r12=ffffe000f86e9540 r13=ffffc001c027e600
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff801`2e957c1c 48890a mov qword ptr [rdx],rcx ds:002b:00800000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B This points towards your GPU drivers, see here

PROCESS_NAME: vegas110.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8012e91ff64 to fffff8012e957c1c

STACK_TEXT:
ffffd000`22e4b4a0 fffff801`2e91ff64 : ffffe000`f799b6a0 fffff801`8893e7b2 ffffe000`f86e9540 00000000`00000000 : nt!KxWaitForLockOwnerShipWithIrql+0x14
ffffd000`22e4b4d0 fffff801`8893e822 : ffffe000`f86e9502 ffffe000`f86e9540 ffffc001`c05cb000 ffffd000`22e4bb00 : nt!ExAcquireResourceSharedLite+0x404
ffffd000`22e4b540 fffff801`8893b90c : ffffe000`f86e9540 ffffc001`c05cb000 ffffc001`c05cb000 00000000`00000000 : dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+0x62
ffffd000`22e4b570 fffff960`001ccaa3 : 00000001`40000b80 ffffe000`f75c2600 00000000`7719c020 00000000`00000000 : dxgkrnl!DxgkEscape+0x45c
ffffd000`22e4ba30 fffff801`2e9e57b3 : ffffe000`f75c2600 00000000`0bc4e470 00000000`00000020 00000000`06f8d1d0 : win32k!NtGdiDdDDIEscape+0x53
ffffd000`22e4ba80 00000000`771a74aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0bc4e458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771a74aa


FOLLOWUP_IP:
dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+62
fffff801`8893e822 4084f6 test sil,sil

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+62

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53183e72

STACK_COMMAND: .cxr 0xffffd00022e4aa70 ; kb

FAILURE_BUCKET_ID: X64_0x3B_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+62

BUCKET_ID: X64_0x3B_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+62

Followup: MachineOwner


  • 0

#20
KELLER1224

KELLER1224

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts

I got a dated driver and I just ran trhough an entire render and it worked! Ill try some more. Hope its fixed!


  • 0

#21
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

Fingers crossed for you KELLER1224  :thumbsup:

 

As the computer appears stable may I suggest that you create a new restore point.


  • 0

#22
KELLER1224

KELLER1224

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts

Ok it is officially fixed. Only issue is, I need the current driver of Nvidia's to obtain my footage through their program. So I'll have to switch between them depending on what I'm doing. Thank you so much philpower2. I really appreciate your help and didn't think I would be able to find help online like this. Great tech.


  • 0

#23
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

Glad you got it sorted and thanks for the follow up KELLER1224  :thumbsup:

 

You are welcome btw  :)


  • 0

#24
KELLER1224

KELLER1224

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts

I rendered 3 vids fine. Then this.... :(  I THOUGHT IT WAS FIXED LOLOL

Attached Files


  • 0

#25
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

Can I ask what version of software you use for rendering videos.

 

Run Process Explorer from the link here to see what if anything is placing high demands on the CPU etc

 

Download Speedfan and install it.  Once it's installed, run the program and post here the information it shows.  The information I want you to post is the stuff that is circled in the example picture I have attached.


If you are running on a vista machine, please go to where you installed the program and run the program as administrator.

 

speedfan.png

(this is a screenshot from a vista machine)

 

 Download then run HWMonitor and post a screenshot so that we have a comparison to the Speedfan results, details from here

 

To capture and post a screenshot;

 

Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload... then after typing in any response you have... click on browse...desktop...find the screenshot..select it and click on the upload button...then on the lower left...after it says upload successful...click on add reply like you normally would.

 

Screenshot instructions are provided to assist those that may read this topic but are not yet aware of the “how to”.


  • 0

Advertisements


#26
KELLER1224

KELLER1224

    Member

  • Topic Starter
  • Member
  • PipPip
  • 18 posts

Im using Sony Vegas Pro 11.0

 

Attached Thumbnails

  • HWMonitor Results.jpg
  • Speedfan Results.jpg

  • 0

#27
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

For troubleshooting purposes could you try another version of Vegas Pro as in an earlier build if you have the latest of Pro 11.

 

Your HWMonitor and Speedfan screenshots are showing bad readings for the +5V rail, this can affect the performance of the GPU among other things and needs to be checked out, see table below;

 

Please restart your computer and check the temperatures/voltages in the BIOS, no screenshot is required just make a note of the temperatures and the +3.3V, +5V and the +12V and post them with your next reply.

 

NB: BIOS voltage readings.

The readings are not conclusive in the BIOS as the computer is under the least amount of load, if they are higher or lower than what they should be though it does suggest a PSU problem.

 

Use msconfig to determine what is causing the problem

These are good tutorials on using msconfig in XP, Vista or Windows 7:
How to use msconfig in Windows XP
How to use msconfig in Windows Vista
How to use msconfig in Windows 7 and Windows 8

Click on Start then Run, type msconfig and press Enter.
Click on the Startup tab (for Windows 8, the Startup tab has a link to open Task Manager/Startup tab. Use that.), record what is currently starting then click the Disable Allbutton.
Reboot and see if it runs better.
If yes then use msconfig to enable several items at a time till you find the culprit.


If no, start msconfig and click on the Services tab.
Check the Hide All Microsoft Services box, record what is currently starting then click the Disable All button.
Again, do a regular boot, see if it runs normal.
If yes then use msconfig to enable services till you find the culprit.


Once you've found the culprit, uninstall it or find out how to eliminate it from your system. Simply disabling it in msconfig is a temporary fix at best.
Enable everything else you disabled.  

Attached Thumbnails

  • PSU tolerance table..jpg

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP