Crashing, then Blue screen (pics attached) (windows vista)

[Mikep]

So i recently started playing Diablo 3, While listening to itunes. My Music starts to skip and the game gets real choppy. Then my computer will end up shutting down and go to the blue screen(pics provided).
Any help or ideas are greatly appreciated.
Sincerely -Mike Thanks in advance.

 

[Patrick]

Re: Crashing, then Blue screen(pic's attached) (windows vista)

Hi Mike,

Please refer to the following and reply back accordingly with the required information - https://www.sysnative.com/forums/bs...ctions-windows-8-1-8-7-and-windows-vista.html

Regards,

Patrick

 

[Mikep]

Re: Crashing, then Blue screen(pic's attached) (windows vista)

Dell Studio xps 435 MT
Window's vista home premium(preinstalled)
Intel(R) Core(TM) i7 CPU 920@2.67ghz
Ram: 6.00
64-bit
AMD Radeon HD 6800

Power supply... Couldn't find any info on that
Hope this is all you need. I'll check back in tomorrow.
Thanks in advance
-Mike

 

[Patrick]

Re: Crashing, then Blue screen(pic's attached) (windows vista)

Thanks.

There don't appear to be any crash dumps in the output. Let's do the following:

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick

 

[Mikep]

Re: Crashing, then Blue screen(pic's attached) (windows vista)

Thanks.

There don't appear to be any crash dumps in the output. Let's do the following:

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick

I appreciate you putting in the time to help me out. I apologize for not responding promptly i didn't see the email until now. I followed all the steps the only thing i had to change was the Small memory dump. What's the next step wait for a crash? lol
Thanks in advance
-Mike
.

 

[Patrick]

What's the next step wait for a crash? lol

Yep!

Keep me updated.

Regards,

Patrick

 

[Mikep]

okay thank you sir... there's no real trigger lol.. So i'm gonna have to be patient lol

 

[Patrick]

Not a problem, patience is a virtue.

Regards,

Patrick

 

[Patrick]

Just checking in to ask if we've had a crash yet? Seems about that time : )

Regards,

Patrick

 

[Mikep]

View attachment 10070View attachment report126.zip
Okay sooo i apologize for this... but i'm having issues again. (recently attempted to play pc games again) (World of warcraft gross i know)
But it crashed again so this should be all the information you need.

 

[jcgriff2]

Hi Mike. . .

There were no memory dumps in the attached zip.

There is no doubt that you are experiencing BSODs as the Event Viewer has logged 7 BSODs since 17 August 2014:

Event[12588]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2014-09-21T22:52:06.000
  Description: 
The computer has rebooted from a bugcheck.  
The bugcheck was: [COLOR=#ff0000]0x0000001e (0xffffffffc0000005[/COLOR], 0xfffff96000233b82, 0x0000000000000000, 0x0000000000000009). 
A dump was saved in: C:\Windows\MEMORY.DMP.

Event[13433]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2014-09-16T21:42:34.000
  Description: 
The computer has rebooted from a bugcheck.  
The bugcheck was: [COLOR=#ff0000]0x00000101[/COLOR] (0x0000000000000019, 0x0000000000000000, 0xfffffa6001b27180, 0x0000000000000006). 
A dump was saved in: C:\Windows\MEMORY.DMP.

Event[17307]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2014-09-05T20:44:57.000
  Description: 
The computer has rebooted from a bugcheck.  
The bugcheck was: [COLOR=#ff0000]0x00000101[/COLOR] (0x0000000000000019, 0x0000000000000000, 0xfffffa6001927180, 0x0000000000000006). 
A dump was saved in: C:\Windows\MEMORY.DMP.

Event[17996]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2014-09-02T20:37:44.000
  Description: 
The computer has rebooted from a bugcheck.  
The bugcheck was: [COLOR=#ff0000]0x00000101[/COLOR] (0x0000000000000019, 0x0000000000000000, 0xfffffa6001927180, 0x0000000000000006). 
A dump was saved in: C:\Windows\MEMORY.DMP.

Event[20078]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2014-08-24T11:53:27.000
  Description: 
The computer has rebooted from a bugcheck.  
The bugcheck was: [COLOR=#ff0000]0x00000124[/COLOR] (0x0000000000000000, 0xfffffa8009db7030, 0x00000000be000000, 0x0000000000800400). 
A dump was saved in: C:\Windows\MEMORY.DMP.

Event[20456]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2014-08-23T15:53:17.000
  Description: 
The computer has rebooted from a bugcheck.  
The bugcheck was: [COLOR=#ff0000]0x00000124[/COLOR] (0x0000000000000000, 0xfffffa8009d35030, 0x0000000000000000, 0x0000000000000000). 
A dump was saved in: C:\Windows\MEMORY.DMP.

Event[21784]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2014-08-17T20:49:12.000
  Description: 
The computer has rebooted from a bugcheck.  
The bugcheck was: [COLOR=#ff0000]0x00000124[/COLOR] (0x0000000000000000, 0xfffffa8009ee6030, 0x00000000be000000, 0x0000000000800400). 
A dump was saved in: C:\Windows\MEMORY.DMP.

Bugchecks
(1) 0x1e (0xc5,,,) - kernel threw an exception; the exception = 0xc5 -- memory access violation (does NOT necessarily mean that RAM is involved)
(3) 0x101 - CPU hang
(3) 0x124 - WHEA (Windows Hardware Error Architecture), a.k.a., Machine Check Exception

Not sure why your system is not producing BSOD kernel dump files.

Check system crash settings - https://www.sysnative.com/forums/wi...-death-windows-8-1-8-7-and-windows-vista.html

Go through these steps - https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/9599-bsods-but-no-dump-files.html

Regards. . .

jcgriff2

 

[Mikep]

Thanks for the quick response... Okay so i set the memory dump to Kernel... it was previously on mini. Now i have to wait for another crash for it to dump the data?

 

[jcgriff2]

Hi. . .

Yes... but we can try and help your system BSOD by running Driver Verifier.

Driver Verifier "checks" 3rd party drivers. If D/V detects a violation, it will force a BSOD and [hopefully] add additional information to the BSOD dump to help ID the offending driver. This assumes that a 3rd party driver is causing your BSODs, which at this point does not seem to be the case because of the 0x101 (CPU hang) and 0x124 (Machine Check Exception) bugchecks. Unknown hardware failure is the likely cause. But it can't hurt to run Driver Verifier.

https://www.sysnative.com/forums/bs...ted-windows-10-8-1-8-7-and-windows-vista.html

Let Driver Verifier run in the background for at least 24 hours. You can use the system while its running, but may experience system resource issues and lagging.

Be sure to save any work frequently as Driver Verifier will BSOD your system if a driver is caught misbehaving.

Regards. . .

jcgriff2

 

[Mikep]

Alright Thanks for the help. I'll repost my reports and such after the next bsod. Hope it's soon haha

 

[Jared]

Without dump files, it's extremely difficult to point a definitive answer. However, looking at the different types of bugchecks, I'm almost certain you have a failing CPU. Is it under warranty still? Keep trying to upload any dump files (if they generate).