Heya. I'm unsure as to whether this is the right forum for this or not, but I would appreciate some assistance.
My PC recently randomly restarted itself. I'm not sure as to why...I was just in the middle of doing my usual programs and it abruptly restarted. When it loaded to the desktop everything looked fine...but I noticed the little yellow shield with the exclamation icon pop up on my bottom blue bar for a second and then disappear. This icon usually appears whenever my computer is installing an OS update or notifying me of when it is done...Odd thing was that when, I checked my most recent updates log and saw that nothing had updated(?)
My computer is running the Windows XP Pro OS.
Can anyone help me with this problem?
Thanks
TTC
/final edit:
After observing the log further I think I found the root of the cause.
4/28/2008: Save Dump - The computer has rebooted from a bugcheck. [etc etc etc]
Anything I should be concerned about?
Full Version: My Computer Just Randomly Restarted?
This type of rebooting behaviour is can be caused by your computer overheating. You can check your system temperatures with SpeedFan, which should give you an indication of whether your system is running too hot.
Also, I would recommend that you open your computer case and make sure all the fans are spinning okay and that there isn't an excessive amount of dust in there that would impede air flow. See the following Bleeping Computer tutorial for guidance on cleaning inside your computer.
Cleaning the Interior of your PC
Also, I would recommend that you open your computer case and make sure all the fans are spinning okay and that there isn't an excessive amount of dust in there that would impede air flow. See the following Bleeping Computer tutorial for guidance on cleaning inside your computer.
Cleaning the Interior of your PC
Before the random restart the tower felt pretty cool, and even now (it hasn't had any restarts since before) its still pretty cold.
My fans were replaced sometime back...And the thing in my tower that was found to be causing heating problems in the past (the graphics card fan died) has been removed and replaced with a brand new card. Back when the tower was overheating during those days, the computer emitted a loud humming noise. There has been no humming noise present since my computer had that part replaced. This note, occured before the restart happened just now.
It should be noted that prior to the random restart I was trying to run three large memory programs. The programs had been having problems with "not responding", so I was killing off each process individually through the windows task manager. It had been after I restarted up two of the three programs again, that it abruptly restarted.
I'm on the Speedfan site right now. What am I suppossed to do to check the heating of the computer?
/edit: in addition, I have cleaned the fans as of 3 weeks ago. I cleaned all 3 fans that are present in my HP Media Center PC m7680n model.
My fans were replaced sometime back...And the thing in my tower that was found to be causing heating problems in the past (the graphics card fan died) has been removed and replaced with a brand new card. Back when the tower was overheating during those days, the computer emitted a loud humming noise. There has been no humming noise present since my computer had that part replaced. This note, occured before the restart happened just now.
It should be noted that prior to the random restart I was trying to run three large memory programs. The programs had been having problems with "not responding", so I was killing off each process individually through the windows task manager. It had been after I restarted up two of the three programs again, that it abruptly restarted.
I'm on the Speedfan site right now. What am I suppossed to do to check the heating of the computer?
/edit: in addition, I have cleaned the fans as of 3 weeks ago. I cleaned all 3 fans that are present in my HP Media Center PC m7680n model.
Did you get a "Blue Screen of Death" error message when the computer restarted?
With SpeedFan, you download and install SpeedFan 4.34 from the website.
With SpeedFan, you download and install SpeedFan 4.34 from the website.
Nope. It just blanked out for a moment, went to the normal start up screen, and after loading brought me to the desktop. Nothing seemed altered or changed, and everything has been running just as fine as it usually is.
I figured it had to do with what I had found in the System part of the event viewer. Here is a full version of what it said under the description:
4/28/2008: Save Dump - The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbfb08ae9, 0x95aea67c, 0x00000000) A dump was saved in: C:\WINDOWS\Minidump\Mini042808-01.dmp.
For more information, see help and support center at: http://go.microsoft.com/fwlink/events.asp.
EDIT: I have installed speedfan. What do I do now?
I figured it had to do with what I had found in the System part of the event viewer. Here is a full version of what it said under the description:
4/28/2008: Save Dump - The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbfb08ae9, 0x95aea67c, 0x00000000) A dump was saved in: C:\WINDOWS\Minidump\Mini042808-01.dmp.
For more information, see help and support center at: http://go.microsoft.com/fwlink/events.asp.
EDIT: I have installed speedfan. What do I do now?
You can analyse the dump file, which may give you a better idea of the cause of the crash.
Windows xp: How to analyze dump file
With SpeedFan, just run it and it will give you the system temperatures.
Windows xp: How to analyze dump file
With SpeedFan, just run it and it will give you the system temperatures.
I figured out how to use the Speedfan program. This is what I saw with it:
Is everything alright?
Is everything alright?
What CPU does your computer have?
QUOTE(Budapest @ Apr 28 2008, 09:01 PM) 
What CPU does your computer have?
Um, what exactly do you mean? Do you mean its computer specs?
For example: Intel Celeron 1.7GHz
I believe its this:
Dual-core 2.13 GHz Intel Core 2 Duo E6400 processor
Hardware Platform: PC
Processor: 2.13 GHz Intel Core Duo
Number of Processors: 2
RAM: 2000 MB
RAM Type: DDR2 SDRAM
(I found this out through a description of the computer on Amazon. I did not get my PC from amazon though...
My computer is an HP Media Center m7680n. I purchased it through CompUSA.
This is all else I know for certain regarding the model:
1. It came with a 300W PSU.
2. It's original graphics card was : Nvidia GeForce 7300 LE video card (256 MB shared)
It has been replaced with the following graphics card: VGA ASUS N EN7300GT SILENT/HTD/256M. The card is kinna big than the other one, and I heard it can sometimes run a little hot.
3. It originally ran on the Windows Media XP Center OS, but was downgraded to Windows XP Pro.
/edit: As a final note, I was reminded that a long time ago prior to the computer getting the replaced part that it restarted randomly once in the middle of the night. This was during a time I used to keep it on for days at a time. (I am a MMO player. I often have to keep one to two of the game client program open at a time) The recent restart happened after I had kept it on two days in a row with this heavy-memory program active. Coincidence, or is there a correlation?
Dual-core 2.13 GHz Intel Core 2 Duo E6400 processor
Hardware Platform: PC
Processor: 2.13 GHz Intel Core Duo
Number of Processors: 2
RAM: 2000 MB
RAM Type: DDR2 SDRAM
(I found this out through a description of the computer on Amazon. I did not get my PC from amazon though...
My computer is an HP Media Center m7680n. I purchased it through CompUSA.
This is all else I know for certain regarding the model:
1. It came with a 300W PSU.
2. It's original graphics card was : Nvidia GeForce 7300 LE video card (256 MB shared)
It has been replaced with the following graphics card: VGA ASUS N EN7300GT SILENT/HTD/256M. The card is kinna big than the other one, and I heard it can sometimes run a little hot.
3. It originally ran on the Windows Media XP Center OS, but was downgraded to Windows XP Pro.
/edit: As a final note, I was reminded that a long time ago prior to the computer getting the replaced part that it restarted randomly once in the middle of the night. This was during a time I used to keep it on for days at a time. (I am a MMO player. I often have to keep one to two of the game client program open at a time) The recent restart happened after I had kept it on two days in a row with this heavy-memory program active. Coincidence, or is there a correlation?
Core temps of 39 and 40C don't sound too bad. You CPU should be good up to about 60C. That temp reading of 74C doesn't look too good, but unfortunately it's hard to know what it's referring to. But you said that you'd had all the fans replaced recently so I would think it's probably not a temp issue. Still, it's worth a look inside the case to see if there's a dust problem.
Did you try the dump file analysis?
Did you try the dump file analysis?
QUOTE(Budapest @ Apr 28 2008, 09:30 PM)
Core temps of 39 and 40C don't sound too bad. You CPU should be good up to about 60C. That temp reading of 74C doesn't look too good, but unfortunately it's hard to know what it's referring to. But you said that you'd had all the fans replaced recently so I would think it's probably not a temp issue. Still, it's worth a look inside the case to see if there's a dust problem.
Did you try the dump file analysis?
Did you try the dump file analysis?
Well, its good to hear everything else in it is going ok at around 60 C at most...but...Hmm.
It's confusing. I cleaned the fan towards the back, and I cleaned the fan up at top. Maybe its the center fan that needs cleaning?
I'm trying to figure out what I'm supposed to install from that site. @_@ There's a lot of different links as to what's available. What specifically on that site am I supposed to download?
/edit: Oh btw, I switched the Speedfan to chart mode. It seems to be going a steady 74 C that occasionally drops to 73 C. Could it be possible that that's just the normal temperature for the computer?
As an update, I just got in contact with HP's tech support regarding the computer temperatures.
They said around 60-70C is perfectly normal. :thumbsup:
I'm in the process now of asking whether a little bit above that is alright. Asides from that, things are looking ok....
They said around 60-70C is perfectly normal. :thumbsup:
I'm in the process now of asking whether a little bit above that is alright. Asides from that, things are looking ok....
I think you want the Windows 32 Bit one.
As for the fans, I think the ones to concentrate on are those that sit directly on the CPU and GPU. They look like this.
As for the fans, I think the ones to concentrate on are those that sit directly on the CPU and GPU. They look like this.
QUOTE(Budapest @ Apr 28 2008, 10:11 PM)
I think you want the Windows 32 Bit one.
As for the fans, I think the ones to concentrate on are those that sit directly on the CPU and GPU. They look like this.
As for the fans, I think the ones to concentrate on are those that sit directly on the CPU and GPU. They look like this.
Oh, I know which one you're referring to. I hadn't cleaned that one, but when I had a technician look at back when I was having the graphic card problems it he said it seemed to be running fine.
/edit: I'll open up the tower and check it out just in case.
((Please delete this post.))
Update regarding the situation. Still need assistance
Prior to clean, the computer core reached a high of 80C! Yikes!
I've just cleaned the processor fan as you've suggested, using the guide that you have provided. I'm running the computer currently with one side of the case off, so I can make sure if there's anything wrong with the fans or not.
After running it for a bit (under an hour) there's are the following temperatures I got from it:
GPU: 57 C (just went up to 59 C)
Temp 1: 42 C (note: this value has been occasionally rising and falling from around 30ish, its now staying a steady 42 C)
Temp 2: -128C
Temp 3: 22C
HD0: 42C
HD1: 42C
Core 0: 33C
Core 1 : 35C
Core: 69 C (At one point went down to 67, then up to 68C a minute or two later. Now staying a solid value of 72 C.)
*Both HD values are indicating to be going up.
The processor fan seems to be working fine. It's been going a constant speed and not stopping. The internals seem a little warm towards the bottom of the tower. The silver lined thing on the graphics card seems to have a good portion of heat.
[b] Now what should I do?
/edit: Here's the log I got using the analysis thing for windump. I think something went wrong....I installed the 32 bit version of it.
Prior to clean, the computer core reached a high of 80C! Yikes!
I've just cleaned the processor fan as you've suggested, using the guide that you have provided. I'm running the computer currently with one side of the case off, so I can make sure if there's anything wrong with the fans or not.
After running it for a bit (under an hour) there's are the following temperatures I got from it:
GPU: 57 C (just went up to 59 C)
Temp 1: 42 C (note: this value has been occasionally rising and falling from around 30ish, its now staying a steady 42 C)
Temp 2: -128C
Temp 3: 22C
HD0: 42C
HD1: 42C
Core 0: 33C
Core 1 : 35C
Core: 69 C (At one point went down to 67, then up to 68C a minute or two later. Now staying a solid value of 72 C.)
*Both HD values are indicating to be going up.
The processor fan seems to be working fine. It's been going a constant speed and not stopping. The internals seem a little warm towards the bottom of the tower. The silver lined thing on the graphics card seems to have a good portion of heat.
[b] Now what should I do?
/edit: Here's the log I got using the analysis thing for windump. I think something went wrong....I installed the 32 bit version of it.
QUOTE
Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini042808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Apr 28 19:30:45.515 2008 (GMT-4)
System Uptime: 0 days 22:14:26.210
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
................................................................................
................................................
Loading User Symbols
Loading unloaded module list
..........................
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfb08ae9, 95aea67c, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : nv4_disp.dll ( nv4_disp+f2ae9 )
Followup: MachineOwner
---------
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 447f8ef8
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nv4_disp+f2ae9
bfb08ae9 8b5e50 mov ebx,dword ptr [esi+50h]
TRAP_FRAME: 95aea67c -- (.trap 0xffffffff95aea67c)
ErrCode = 00000000
eax=00000000 ebx=00033128 ecx=e4f3ee88 edx=e3e0fe40 esi=000000f0 edi=e3e0fe80
eip=bfb08ae9 esp=95aea6f0 ebp=e4f3c340 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nv4_disp+0xf2ae9:
bfb08ae9 8b5e50 mov ebx,dword ptr [esi+50h] ds:0023:00000140=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bfb08cb6 to bfb08ae9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
95aea6fc bfb08cb6 e4f3c340 e4f3ee80 00001000 nv4_disp+0xf2ae9
95aea700 e4f3c340 e4f3ee80 00001000 e3aa1740 nv4_disp+0xf2cb6
95aea704 e4f3ee80 00001000 e3aa1740 00000000 0xe4f3c340
95aea708 00000000 e3aa1740 00000000 00000000 0xe4f3ee80
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+f2ae9
bfb08ae9 8b5e50 mov ebx,dword ptr [esi+50h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+f2ae9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini042808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Apr 28 19:30:45.515 2008 (GMT-4)
System Uptime: 0 days 22:14:26.210
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
................................................................................
................................................
Loading User Symbols
Loading unloaded module list
..........................
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfb08ae9, 95aea67c, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : nv4_disp.dll ( nv4_disp+f2ae9 )
Followup: MachineOwner
---------
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 447f8ef8
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nv4_disp+f2ae9
bfb08ae9 8b5e50 mov ebx,dword ptr [esi+50h]
TRAP_FRAME: 95aea67c -- (.trap 0xffffffff95aea67c)
ErrCode = 00000000
eax=00000000 ebx=00033128 ecx=e4f3ee88 edx=e3e0fe40 esi=000000f0 edi=e3e0fe80
eip=bfb08ae9 esp=95aea6f0 ebp=e4f3c340 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nv4_disp+0xf2ae9:
bfb08ae9 8b5e50 mov ebx,dword ptr [esi+50h] ds:0023:00000140=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bfb08cb6 to bfb08ae9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
95aea6fc bfb08cb6 e4f3c340 e4f3ee80 00001000 nv4_disp+0xf2ae9
95aea700 e4f3c340 e4f3ee80 00001000 e3aa1740 nv4_disp+0xf2cb6
95aea704 e4f3ee80 00001000 e3aa1740 00000000 0xe4f3c340
95aea708 00000000 e3aa1740 00000000 00000000 0xe4f3ee80
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+f2ae9
bfb08ae9 8b5e50 mov ebx,dword ptr [esi+50h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+f2ae9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.