New
#11
Yes, but it can't be opened and debugged with the debugger , which is a bit more important.
Sent from my SGH-i917 using Board Express
Yes, but it can't be opened and debugged with the debugger , which is a bit more important.
Sent from my SGH-i917 using Board Express
Ok, here it is :)
MEMORY.rar
Still can't make this load properly - something's up with the data in this dump. I hate to ask, but can you take another? This one still only has user-mode context data in it.
Maybe I am doing smth wrong ?
Here is new one
MEMORYdump.rar
Using Process explorer I found that Interrupts is the one I should me watching!
Searching a little bit I have found that problem could be in ATA Channel, that it can be switched to PIO mode, but on mine, it says that DMA is enabled!
Also, when waking from sleep I hear that sound like when you remove USB from PC, even thought I haven't removed anything...
Here are the errors I get in event log
Code:1. The server could not bind to the transport \Device\NetBT_Tcpip_{82C32301-772F-42A6-B96C-C167143DB45A} because another computer on the network has the same name. The server could not start. 2. The name "BENKO-PC :20" could not be registered on the interface with IP address 192.168.1.81. The computer with the IP address 192.168.1.80 did not allow the name to be claimed by this computer. 3. The name "BENKO-PC :0" could not be registered on the interface with IP address 192.168.1.81. The computer with the IP address 192.168.1.80 did not allow the name to be claimed by this computer. For first source is server, for 2nd and 3rd source is NetBT
Well, interrupts (and the system process) would indicate a driver issue or a system configuration issue, but it's unfortunately not easy to tell from a process explorer snapshot. As I said initially, my suspicion is a networking issue, but all of the "easy" tests sort of dispel that.
Let me think about what to do here - dumping it hasn't been successful, but more info is good. Let's see if I can come up with something that'll spill the beans, so to speak, that we can do here.
Unfortunately, when your machine crashes and dumps, it only seems to save the user-mode portion of data (the kernel-mode stacks and such are not included). This probably has something to do with your issue, and in a customer scenario I'd just set up a kernel debugger and crash cart, but that's difficult over the internet .