Hello NocturnalSleep,

Various differemt bugchecks but they're all pointing to your GPU drivers of DirectX one way or another. I'd recommend uninstalling and reinstalling your nVidia video drivers and reinstalling the latest version. If you're already on the latest version, I'd recommend uninstalling and installing a previous version to the latest to be sure it's not a simple driver issue.

Driver(s) in need of update:

ASMMAP64.sys - Sun Feb 04 14:52:56 2007 (LENOVO ATK Hotkey ATK0101 ACPI UTILITY). Update if available here.

vuhub.sys - Fri Nov 16 10:31:13 2007 (Eltima Software USB to Ethernet Connector Driver). Update if available here.

Regards,

Patrick

 

Just in passing you should also update these drivers.

sncduvc.SYS    12/29/2008 5:14:26 AM                       
AsDsm.sys    2/13/2009 2:14:26 AM                       
hamachi.sys    2/19/2009 6:36:41 AM                        
ATK64AMD.sys    5/12/2009 9:04:54 PM                              
snp2uvc.sys    5/20/2009 4:11:05 AM                         
L1C62x64.sys    6/28/2009 11:53:43 PM                     
rimspe64.sys    7/1/2009 7:54:49 PM                           
rixdpe64.sys    7/4/2009 6:27:00 AM

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 Reference Table (DRT)

Driver Reference Table

- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.htm

 

Thank you for the help, PJB and zigzag3143!

I have uninstalled and reinstalled the Nvidia drivers to the latest version, and hopefully, if I didn't botch the install somehow, this will solve my BSOD issue!

I'll attempt to run some games and see how well it works out.

I will now go and update all the drivers that you guys posted that are in need of an update. Thanks for including them too!

EDIT: I've been looking around for the Lenovo ATK Hotkey driver, but the site itself is very confusing and I've only been able to find this page. The problem is, it only lists up to Windows Vista, and so I'm unsure if I should still get this version of the driver, or if it will cause my system problems.

 

My pleasure, keep me updated.

 

Let us know if you need help

 

Indeed, keep us updated is what I meant

As far as your driver question / concern goes.. let's try it this way:

1. Go here: AMD Driver Autodetect

2. Once you've downloaded that, run it and download / install the driver it recommends as the latest for your laptop.

If no drivers can be found for your laptop on W7, let us know.

Regards,

Patrick

 

Absolutely not, we're the best team around! I just put "me" in my post accidentally and didn't want to make that seem as if I was trying be rude in any way

Regards,

Patrick

 

No worries Patrick. An extra set of eyes is always good. US

 

I haven't bsod yet, but if it's going to be sneaky again, I may have to wait a while.

I did notice that my screen would have random white and black squares though...it's been there before I reinstalled the driver. Is it a sign I installed wrong, maybe?

Thanks for the AMD Driver Autodetect link! I will certainly use that.

 

Hello, I've run the AMD Driver Detect and it said "We were unable to find your product or OS." I don't really know what the means... :S

Does it mean that there are no drivers to be found, or it just can't read my computer in the first place?

Also, I bsod again yesterday, and I went and reinstalled my graphics driver. But there doesn't seem to be any luck, since I bsod again today after playing a few hours of a game.

I've attached the minidumps below. Thanks again, you two!

 

Ah, I'm sorry for the triple post! I tried to edit the above post, but I couldn't find the button anywhere.

I got another bsod last night, though it was surprisingly not from my GPU, but from my wireless network adapter. I don't know why it would do that, since I updated my drivers around 5 months ago to the most recent version...

 

*BUMP*

I'm still having problems. And now I'm getting freezes (it's happened twice). I also had a software randomly uninstall on me that I don't ever remember uninstalling. I did eventually uninstall some software today hoping that maybe they weren't the cause, but that didn't work. :/

Thanks for reading. I apologize for the quadruple posts in a row.

 

Hello, very sorry for the lack of response.. your thread seemed to have slipped through my subscriptions!

I've taken a look at your latest attached dumps, there's a 124 hardware bugcheck. If we run an !errrec on the second parameter of the bugcheck, so in your case it's what I've bolded: BugCheck 124, {4, fffffa80071da8d8, 0, 0}

we then get this...

kd> !errrec fffffa80071da8d8
===============================================================================
Common Platform Error Record @ fffffa80071da8d8
-------------------------------------------------------------------------------
Record Id     : 01cd72c7df7f6965
Severity      : Fatal (1)
Length        : 672
Creator       : Microsoft
Notify Type   : PCI Express Error
Timestamp     : 8/5/2012 5:42:21
Flags         : 0x00000000

===============================================================================
Section 0     : PCI Express
-------------------------------------------------------------------------------
Descriptor    @ fffffa80071da958
Section       @ fffffa80071da9e8
Offset        : 272
Length        : 208
Flags         : 0x00000001 Primary
Severity      : Recoverable

Port Type     : Root Port
Version       : 1.1
Command/Status: 0x0010/0x0407
Device Id     :
  VenId:DevId : 8086:d138
  Class code  : 030400
  Function No : 0x00
  Device No   : 0x03
  Segment     : 0x0000
  Primary Bus : 0x00
  Second. Bus : 0x00
  Slot        : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ fffffa80071daa1c
  Device Caps : 00008021 Role-Based Error Reporting: 1
  Device Ctl  : 0107 ur FE NF CE
  Dev Status  : 0003 ur fe NF CE
   Root Ctl   : 0008 fs nfs cs

AER Information @ fffffa80071daa58
  Uncorrectable Error Status    : 00014000 ur ecrc mtlp rof UC ca CTO fcp ptlp sd dlp und
  Uncorrectable Error Mask      : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
  Uncorrectable Error Severity  : 00062010 ur ecrc MTLP ROF uc ca cto FCP ptlp sd DLP und
  Correctable Error Status      : 00002000 ADV rtto rnro dllp tlp re
  Correctable Error Mask        : 00000000 adv rtto rnro dllp tlp re
  Caps & Control                : 0000000e ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
  Header Log                    : 00000000 00000000 00000000 00000000
  Root Error Command            : 00000000 fen nfen cen
  Root Error Status             : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer
  Correctable Error Source ID   : 00,00,00
  Correctable Error Source ID   : 00,00,00

===============================================================================
Section 1     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80071da9a0
Section       @ fffffa80071daab8
Offset        : 480
Length        : 192
Flags         : 0x00000000
Severity      : Informational

Proc. Type    : x86/x64
Instr. Set    : x64
CPU Version   : 0x00000000000106e5
Processor ID  : 0x0000000000000003

As you can see, your issue is a PCI Express Error. If we look a little bit further, we can see:

Device Id     :
  VenId:DevId : 8086:d138

If we head to PCI Vendor and Device Lists and run the DevID through it, it shows up with the following:

PCI Vendor and Device Lists

Unfamiliar with this, I decided to click the Vendor Name and it pops up with two entries, the second being this:

Chip Number:  S1D13808   Chip Description:  Embedded Memory Display Controller   Notes:  2MB Display Controller for LCD/CRT/TV devices

So the chip descrip. is Embedded Memory Display Controller, which matches up with our previous DevId look-up. Now if we take it one step further again, we see that the chip number is "S1D13808". If we google "S1D13808", a search comes up for Epson LCD Controller. Does this sound relevant or right to your situation at all?

If not, based off of the PCI-e 124 errors, and the dxgmms1.sys culprits (DirectX constantly crashing), we're likely dealing with an internal hardware issue here if you've gone above and beyond regarding video card driver updates, etc, specifically something with the PCI-e part of the laptop board.

Regards,

Patrick

 

It's quite alright, I understand if my thread was obscure for a while! I think there was a point where it didn't appear as if it was updated with a new post on the forums.

The Epson LCD Controller sounds vaguely familiar, but I'm unable to confirm it. I've looked through my devices and I don't see anything about it. There is an Atheros AR8131 PCI-E Gigabit Ethernet Controller NDIS 6.20), though, in my Network Adapters devices. There are also several PCI-e buses in my System devices.

It sounds like either with the Epson LCD Controller or with the PCI-e errors, I'm going to have to be doing something with the hardware of my system. I was hoping to not have to go into my computer, because I'm not that good with it/naming many parts. :sad:

The PCI-e errors would also explain the failure of my wireless network driver crashes, right? Especially if it was related to the PCI-E Gigabit Ethernet Controller above? Though if it's apparently an Epson related hardware then I'm not sure...

Thanks for the reply, Patrick! I really do appreciate it. :smile:

 

Hi,

My pleasure. As I said earlier, the Epson LCD Controller was just a hunch when I was looking through that site, I figured I'd ask just in case if you had that particular device. If not, you're likely correct in saying that this is motherboard related, especially if it's also crashing your wireless network drivers all the time as well. "Embedded Memory Controller" likely is something relating to a regular Memory Controller on desktop boards and such, or MCC (Memory Chip Controller).

As it's a laptop and not a desktop, if you're sure you don't have an Epson LCD Controller, my next recommendation to you would be to contact Asus and let them know that you're having 124 hardware BSOD's that are mentioning PCI-e errors, and you've gone above and beyond in troubleshooting.

Regards,

Patrick

 

Hi Patrick,

I apologize for the late reply, I had been away attending an orientation for my college.

My wireless network drivers haven't actually crashed since I updated them several months ago, so I think it is a hardware issue.

I will try to contact Asus, but it's a used laptop, so I doubt I have any warranty left. I will also head on over to the hardware section of this forum and ask for a bit of help. It's a bummer it has to be the motherboard.

If you can, can you also look at this last bsod for me? I just want to know what was the cause, and if it's the same, just to make sure it's not going to a random bsod, and to narrow everything down.

Thanks again!

 

Hi,

The latest attached crash dump from August 10th, is a 119: VIDEO_SCHEDULER_INTERNAL_ERROR bugcheck faulting dxgmms1.sys. To just give you an idea and understanding of what's going on, I will explain why DirectX is the fault and not the drivers.. but first, let's take a look at the stack trace:

STACK_TEXT:  
fffff880`035ae758 fffff880`0455222f : 00000000`00000119 00000000`07000000 fffffa80`0aca2010 fffffa80`0e620af0 : nt!KeBugCheckEx
fffff880`035ae760 fffff880`03143318 : fffffa80`0e60ebb0 00000000`00000000 00000000`00000000 fffffa80`0e620b50 : watchdog!WdLogEvent5+0x11b
fffff880`035ae7b0 fffff880`0314337a : fffffa80`0000378e fffffa80`0e620b50 00000000`00000000 fffffa80`0aca2010 : dxgmms1!VidSchiCheckConditionDeviceCommand+0x8c
fffff880`035ae7e0 fffff880`0313f360 : fffffa80`06e10df0 fffffa80`0e620af0 fffffa80`0acc1000 fffffa80`0acc1000 : dxgmms1!VidSchiCheckPendingDeviceCommand+0x3e
fffff880`035ae820 fffff880`0313e7da : fffffa80`00000001 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x438
fffff880`035ae8e0 fffff880`0313de00 : fffffa80`00000000 fffffa80`0aca2010 00000000`00000000 fffff880`060c7000 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`035ae980 fffff880`0313dc4c : 00000000`00000002 fffffa80`0aca2010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`035ae9d0 fffff880`030441cf : fffffa80`09b53040 00000000`00000000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`035aea20 fffff880`0f4e77f0 : fffffa80`09d76000 fffffa80`09d76000 00000000`00000000 00000000`00000000 : [SIZE=3][COLOR=Red][U][B]dxgkrnl!DxgNotifyDpcCB[/B][/U][/COLOR][/SIZE]+0x77
fffff880`035aea50 fffffa80`09d76000 : fffffa80`09d76000 00000000`00000000 00000000`00000000 fffff880`0f4e7783 : nvlddmkm+0xd97f0
fffff880`035aea58 fffffa80`09d76000 : 00000000`00000000 00000000`00000000 fffff880`0f4e7783 fffffa80`09d76000 : 0xfffffa80`09d76000
fffff880`035aea60 00000000`00000000 : 00000000`00000000 fffff880`0f4e7783 fffffa80`09d76000 00000000`00000000 : 0xfffffa80`09d76000

As you can see, I have bolded, underlined and italicized the important thing to look at here, which is dxgkrnl!DxgNotifyDpcCB.

Interrupts / Interrupt Service Routines to handle device I/O need to be done quickly or they run the risk of holding up the system due to the high IRQL. A simple and quick definition of IRQL is: An interrupt request level (IRQL) defines the hardware priority at which a processor operates at any given time.

If you'd like to further read into it, you can check this article: What is IRQL? - A Hole In My Head - Site Home - MSDN Blogs

Due to the system running the risk of being held up, the interrupt is designed to create what is called a DPC (Deferred Procedure Call), which puts off the responsibility of handling the I/O till later. Just for a short reference, we can see Dpc in the stack trace as mentioned earlier: (dxgkrnl!DxgNotifyDpcCB).

Now, once the DPC itself is in the next DPC queue, it will then do the servicing of the I/O device. The interrupt is there to notify the system to prepare for the I/O, but the DPC is doing all the work.

Essentially, the interrupt has already done all of its work, and now the DPC must do its work (the I/O), which DirectX is involved in (and that is why you see DirectX as the fault in the crash dump).

So, with that said... we have a few things to do and try here:

1. Check nVidia's website and ensure you're on the latest drivers - Drivers - Download NVIDIA Drivers

If you are already on the latest drivers, I recommend rolling back a version or so to be sure the latest drivers are not the issue. I do not recommend beta drivers unless they are a last resort in troubleshooting situations.

If rolling back a version or so does not help, given your previous crash dumps being PCI-e x124, your issue is likely most definitely motherboard related.

Regards,

Patrick

 

Sadly, I have no previous version, because I looked up it was recommended to do a clean new install of new Nvidia drivers since installing a new one on top of the old one could cause problems with the build of the most recent drivers. I could download an earlier version and install that, though.

But I do think this is turning more into a motherboard issue, since things that shouldn't be crashing (like my wireless network card) are out of nowhere and DirectX keeps crashing. None of my bsods after I installed the new graphics drivers have been GPU related, so I think that my bsods were multiple issues, and now it's been narrowed down to one.

Thanks again for looking at it, Patrick!

If I solve this issue I'll come back and post about it. I really appreciate the help!