Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Recurring BSODs often occuring when gaming

22 Sep 2013   #1

Windows 7 Professional x64
 
 
Recurring BSODs often occuring when gaming

Games in question include warframe and planetside 2. I have the absolute most recent graphic card driver (GeForce 327.23). I have no current overclocks running on my machine. except perhaps the graphics cards factory OC. As of making this thread there are no new updates for my windows.

EDIT: one of these blue screens, the DRIVER_VERIFIER_DETECTED_VIOLATION occurred after i started using my new headset, a Corsair Vengeance 1500 (USB plug). I suspect the headset caused this one but cannot say for sure. the other 3 i attached occurred before i started using it.

system info:
RAM: 16Gb
CPU: AMD phenom II x6 1100T black edition.
GPU: Nvidia GTX 580
OS: Windows 7 Professional 64 bit.

If any more info is needed I am happy to provide it, just hoping to get any issues with my computer sorted



Attached Files
File Type: zip Minidumps.zip (105.9 KB, 5 views)
My System SpecsSystem Spec
.

23 Sep 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Based on the bugchecks, I would recommend you follow and complete the steps given below:
1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
Please update or remove the drivers below.
AsUpIO.sys Mon Jul 6 08:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Driver Reference Table - AsUpIO.sys

ASACPI.sys Thu Jul 16 09:31:29 2009 (4A5E9F11)
Asus ATK0110 ACPI Utility (a known BSOD maker in Windows 7 and Win8).
Also a part of many Asus utilities (Win8 versions available from Windows
Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

nusb3hub.sys Fri Apr 23 07:34:35 2010 (4BD0F92B)
NEC Electronics USB 3.0 Host Controller Driver
Driver Reference Table - nusb3hub.sys

nusb3xhc.sys Fri Apr 23 07:34:36 2010 (4BD0F92C)
NEC Electronics USB 3.0 Host Controller Driver
Driver Reference Table - nusb3xhc.sys
------------------------
To perform a clean install of a driver, follow this tutorial:
Follow this:
Quote   Quote: Originally Posted by Arc View Post
Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.
Code:
nvhda64v.sys                Sun Jun 16 18:38:07 2013 (51BDB1AF)
nvvad64v.sys                Tue Aug 20 17:29:10 2013 (52135306)
nvlddmkm.sys                Thu Sep 12 11:16:00 2013 (52314E10)
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.
Monitor hardware temperature with system monitoring software like Speccy or HWMonitor.
Upload a screen shot of the Summary tab as well:SUMMARY OF THE DUMPS:
Code:
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sun Sep 22 03:51:03.857 2013 (UTC + 6:00)
System Uptime: 3 days 6:47:52.012
BugCheck C4, {91, 2, fffff880030af040, 0}
Probably caused by : hardware ( USBPORT!USBPORT_DereferenceEndpoint+2d )
BUGCHECK_STR:  0xc4_91
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Wed Sep 18 21:02:08.859 2013 (UTC + 6:00)
System Uptime: 1 days 10:21:22.015
BugCheck A, {c, 2, 1, fffff80002c9aa50}
Probably caused by : hardware ( nt!KiIpiInterrupt+e0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  spotify.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Tue Sep 17 10:39:45.523 2013 (UTC + 6:00)
System Uptime: 1 days 15:33:13.318
BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sun Sep 15 19:04:57.632 2013 (UTC + 6:00)
System Uptime: 2 days 15:43:40.787
BugCheck 7F, {8, 80050031, 6f8, fffff80002cc3f5b}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  mpc-hc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
My System SpecsSystem Spec
24 Sep 2013   #3

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by koolkat77 View Post
based on the bugchecks, i would recommend you follow and complete the steps given below:
1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear cmos: clear cmos - 3 ways to clear the cmos - reset bios. Uninstall any overclocking tool as these can also be a reason of blue screens.
I have cleared my CMOS to factory defaults.


Quote:
2. Uninstall your current antivirus software. It can be a cause of bsod very often. Please remove it with its removal tool and use microsoft security essentials in its place. malwarebytes is a great combination with it. Go through this thread for more info.
I removed my Antivirus, Panda Global Protection 2013 prior to these blue screens occurring due to previous blue screens. Currently running Security Essentials, will look into malewarebytes.

Quote:
3. Run disk check with both boxes checked for all hdds and with automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
I performed CHKDSK on both of my hard drives, here are the logs, pardon the foreign but hopefully you can filter out the gibberish from the actual important info.

CHKDSK 1 on C:
Code:
Loggnamn:      Application
Källa:         Microsoft-Windows-Wininit
Datum:         2013-09-23 11:56:23
Händelse-ID:   1001
Aktivitetskategori:Ingen
Nivå:          Information
Nyckelord:     Klassiskt
Användare:     Saknas
Dator:         Twilie
Beskrivning:


Kontrollerar filsystemet på C:
Filsystemet är av typen NTFS.

En diskkontroll har schemalagts.
Disken kommer nu att kontrolleras.                       

CHKDSK verifierar filer (steg 1 av 5)...
Rensar upp instanstaggar för filen 0x5ef.
  282368 filposter har behandlats.                                       

Filverifieringen är klar.
  2108 stora filposter har behandlats.                                 

  0 skadade filposter har behandlats.                               

  2 EA-poster har behandlats.                                       

  133 referensposter har behandlats.                                  

CHKDSK verifierar index (steg 2 av 5)...
  367106 indexposter har behandlats.                                     

Indexverifieringen är klar.
  0 oindexerade filer har genomsökts.                               

  0 oindexerade filer har återställts.                              

CHKDSK verifierar säkerhetsbeskrivare (steg 3 av 5)...
  282368 fil-SD/SID-poster har behandlats.                               

Rensar upp 174 oanvända indexposter från indexet $SII i filen 0x9.
Rensar upp 174 oanvända indexposter från indexet $SDH i filen 0x9.
Rensar upp 174 oanvända säkerhetsbeskrivare.
Verifieringen av säkerhetsbeskrivare är klar.
  42370 datafiler har behandlats.                                       

CHKDSK verifierar USN-journalen...
  33603352 USN-byte har behandlats.                                        

Verifieringen av USN-journalen är klar.
CHKDSK verifierar fildata (steg 4 av 5)...
  282352 filer har behandlats.                                           

Verifieringen av filinformationen är klar.
CHKDSK verifierar ledigt diskutrymme (steg 5 av 5)...
  15250847 lediga kluster har bearbetats.                                  

Verifieringen av ledigt diskutrymme är klar.
Korrigeringar har gjorts i filsystemet.

 625129471 kB diskutrymme totalt.
 563602124 kB i 234912 filer.
    122104 kB i 42371 index.
         0 kB i skadade sektorer.
    401855 kB används av operativsystemet.
     65536 kB hårddisksutrymme används av loggfilen.
  61003388 kB ledigt utrymme.

      4096 byte i varje allokeringsenhet.
 156282367 allokeringsenheter finns totalt på disken.
  15250847 allokeringsenheter är tillgängliga på disken.

Intern information:
00 4f 04 00 2e 3b 04 00 a4 5e 07 00 00 00 00 00  .O...;...^......
8a 04 00 00 85 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Kontrollen av disken har slutförts.
Vänta medan datorn startas om.

Händelsens XML-data:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-23T09:56:23.000000000Z" />
    <EventRecordID>13535</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Twilie</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Kontrollerar filsystemet på C:
Filsystemet är av typen NTFS.

En diskkontroll har schemalagts.
Disken kommer nu att kontrolleras.                       

CHKDSK verifierar filer (steg 1 av 5)...
Rensar upp instanstaggar för filen 0x5ef.
  282368 filposter har behandlats.                                       

Filverifieringen är klar.
  2108 stora filposter har behandlats.                                 

  0 skadade filposter har behandlats.                               

  2 EA-poster har behandlats.                                       

  133 referensposter har behandlats.                                  

CHKDSK verifierar index (steg 2 av 5)...
  367106 indexposter har behandlats.                                     

Indexverifieringen är klar.
  0 oindexerade filer har genomsökts.                               

  0 oindexerade filer har återställts.                              

CHKDSK verifierar säkerhetsbeskrivare (steg 3 av 5)...
  282368 fil-SD/SID-poster har behandlats.                               

Rensar upp 174 oanvända indexposter från indexet $SII i filen 0x9.
Rensar upp 174 oanvända indexposter från indexet $SDH i filen 0x9.
Rensar upp 174 oanvända säkerhetsbeskrivare.
Verifieringen av säkerhetsbeskrivare är klar.
  42370 datafiler har behandlats.                                       

CHKDSK verifierar USN-journalen...
  33603352 USN-byte har behandlats.                                        

Verifieringen av USN-journalen är klar.
CHKDSK verifierar fildata (steg 4 av 5)...
  282352 filer har behandlats.                                           

Verifieringen av filinformationen är klar.
CHKDSK verifierar ledigt diskutrymme (steg 5 av 5)...
  15250847 lediga kluster har bearbetats.                                  

Verifieringen av ledigt diskutrymme är klar.
Korrigeringar har gjorts i filsystemet.

 625129471 kB diskutrymme totalt.
 563602124 kB i 234912 filer.
    122104 kB i 42371 index.
         0 kB i skadade sektorer.
    401855 kB används av operativsystemet.
     65536 kB hårddisksutrymme används av loggfilen.
  61003388 kB ledigt utrymme.

      4096 byte i varje allokeringsenhet.
 156282367 allokeringsenheter finns totalt på disken.
  15250847 allokeringsenheter är tillgängliga på disken.

Intern information:
00 4f 04 00 2e 3b 04 00 a4 5e 07 00 00 00 00 00  .O...;...^......
8a 04 00 00 85 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Kontrollen av disken har slutförts.
Vänta medan datorn startas om.
</Data>
  </EventData>
</Event>
CHKDSK 2 on D:
Code:
Loggnamn:      Application
Källa:         Chkdsk
Datum:         2013-09-23 15:35:11
Händelse-ID:   26214
Aktivitetskategori:Ingen
Nivå:          Information
Nyckelord:     Klassiskt
Användare:     Saknas
Dator:         Twilie
Beskrivning:
Chkdsk kördes i läs- och skrivläge.  

Kontrollerar filsystemet på D:
Volymen är demonterad. Alla öppna referenser till volymen är nu ogiltiga.
Volymetiketten är Media Drive.

CHKDSK verifierar filer (steg 1 av 5)...
  154112 filposter har behandlats.                                       

Filverifieringen är klar.
  87 stora filposter har behandlats.                                 

  0 skadade filposter har behandlats.                               

  0 EA-poster har behandlats.                                       

  0 referensposter har behandlats.                                  

CHKDSK verifierar index (steg 2 av 5)...
  172852 indexposter har behandlats.                                     

Indexverifieringen är klar.


CHKDSK verifierar säkerhetsbeskrivare (steg 3 av 5)...
  154112 fil-SD/SID-poster har behandlats.                               

Rensar upp 8 oanvända indexposter från indexet $SII i filen 0x9.
Rensar upp 8 oanvända indexposter från indexet $SDH i filen 0x9.
Rensar upp 8 oanvända säkerhetsbeskrivare.
Verifieringen av säkerhetsbeskrivare är klar.
  9371 datafiler har behandlats.                                       

CHKDSK verifierar USN-journalen...
  35100104 USN-byte har behandlats.                                        

Verifieringen av USN-journalen är klar.
CHKDSK verifierar fildata (steg 4 av 5)...
  154096 filer har behandlats.                                           

Verifieringen av filinformationen är klar.
CHKDSK verifierar ledigt diskutrymme (steg 5 av 5)...
  2804742 lediga kluster har bearbetats.                                  

Verifieringen av ledigt diskutrymme är klar.
Filsystemet har kontrollerats. Inga problem påträffades.

 976758783 kB diskutrymme totalt.
 796664960 kB i 139370 filer.
    330624 kB i 9372 index.
    259711 kB används av operativsystemet.
     65536 kB hårddisksutrymme används av loggfilen.
 179503488 kB ledigt utrymme.

     65536 byte i varje allokeringsenhet.
  15261855 allokeringsenheter finns totalt på disken.
   2804742 allokeringsenheter är tillgängliga på disken.

Händelsens XML-data:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Chkdsk" />
    <EventID Qualifiers="0">26214</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-23T13:35:11.000000000Z" />
    <EventRecordID>13961</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Twilie</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Kontrollerar filsystemet på D:
Volymen är demonterad. Alla öppna referenser till volymen är nu ogiltiga.
Volymetiketten är Media Drive.

CHKDSK verifierar filer (steg 1 av 5)...
  154112 filposter har behandlats.                                       

Filverifieringen är klar.
  87 stora filposter har behandlats.                                 

  0 skadade filposter har behandlats.                               

  0 EA-poster har behandlats.                                       

  0 referensposter har behandlats.                                  

CHKDSK verifierar index (steg 2 av 5)...
  172852 indexposter har behandlats.                                     

Indexverifieringen är klar.


CHKDSK verifierar säkerhetsbeskrivare (steg 3 av 5)...
  154112 fil-SD/SID-poster har behandlats.                               

Rensar upp 8 oanvända indexposter från indexet $SII i filen 0x9.
Rensar upp 8 oanvända indexposter från indexet $SDH i filen 0x9.
Rensar upp 8 oanvända säkerhetsbeskrivare.
Verifieringen av säkerhetsbeskrivare är klar.
  9371 datafiler har behandlats.                                       

CHKDSK verifierar USN-journalen...
  35100104 USN-byte har behandlats.                                        

Verifieringen av USN-journalen är klar.
CHKDSK verifierar fildata (steg 4 av 5)...
  154096 filer har behandlats.                                           

Verifieringen av filinformationen är klar.
CHKDSK verifierar ledigt diskutrymme (steg 5 av 5)...
  2804742 lediga kluster har bearbetats.                                  

Verifieringen av ledigt diskutrymme är klar.
Filsystemet har kontrollerats. Inga problem påträffades.

 976758783 kB diskutrymme totalt.
 796664960 kB i 139370 filer.
    330624 kB i 9372 index.
    259711 kB används av operativsystemet.
     65536 kB hårddisksutrymme används av loggfilen.
 179503488 kB ledigt utrymme.

     65536 byte i varje allokeringsenhet.
  15261855 allokeringsenheter finns totalt på disken.
   2804742 allokeringsenheter är tillgängliga på disken.
</Data>
    <Binary>005A020011450200371A04000000000024040000000000000000000000000000</Binary>
  </EventData>
</Event>
Again, hope you can find the wanted info within these.

Quote:
4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
After 5 runs it still reports back errors that were unable to be fixed.

Quote:
Neither program finds anything.

Quote:
6. Perform a clean start up, this will help avoid any problematic applications from bugging the system.
I have set my system to perform clean start ups.

Quote:
7. Use revo uninstaller free to uninstall stubborn software. Opt for advanced mode and uninstall the software, delete the leftover registry entries.
Installed the software but I have yet to remove a program with it, have not bumped into something i feel require removal.

Quote:
8. Use crystal disk info to upload a screenshot of your hard drives (s). Test your hard drives (s) running a hard drive diag.
For the first part of this step:
Recurring BSODs often occuring when gaming-ghkpwm2.png
And:
Name:  pqm2AYM.png
Views: 53
Size:  59.3 KB

The second part, the one about a hard drive diagnose confused me, could use some elaboration here.

Quote:
9. Test and diagnose ram issues with RAM - Test with Memtest86+. Pay close attention to part 3 of the tutorial "if you have errors" take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
Burned the ISO to a disk and performed 7 passes on my machine. No errors were found.
Quote:
please update or remove the drivers below.
asupio.sys mon jul 6 08:21:38 2009 (4a515fb2)
asus hardware monitoring software related
driver reference table - asupio.sys

asacpi.sys thu jul 16 09:31:29 2009 (4a5e9f11)
asus atk0110 acpi utility (a known bsod maker in Windows 7 and win8).
Also a part of many asus utilities (win8 versions available from windows
update as an optional update - but check asus first!)
driver reference table - asacpi.sys

nusb3hub.sys fri apr 23 07:34:35 2010 (4bd0f92b)
nec electronics usb 3.0 host controller driver
driver reference table - nusb3hub.sys

nusb3xhc.sys fri apr 23 07:34:36 2010 (4bd0f92c)
nec electronics usb 3.0 host controller driver
driver reference table - nusb3xhc.sys
------------------------
to perform a clean install of a driver, follow this tutorial:
I tried to remove all 4 drivers though I am unsure how successfull i was. the ASUS ones dont seem to show up in driver sweeper. the programs for the ASUS sys files shown have long since been uninstalled.
could use some further help on this point.

Quote:
follow this:
Quote   Quote: Originally Posted by arc View Post
lately we have experienced some issues with the latest driver. Install the 314.22 whql only.
Code:
nvhda64v.sys                sun jun 16 18:38:07 2013 (51bdb1af)
nvvad64v.sys                tue aug 20 17:29:10 2013 (52135306)
nvlddmkm.sys                thu sep 12 11:16:00 2013 (52314e10)
  • uninstall all nvidia items in control panel > programs and features
    • 3d vision control driver
    • 3d vision driver
    • graphics driver
    • hd audio driver
    • physx
    • nvidia update
    (are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • now follow drivers - clean left over files after uninstalling
  • boot normally now. Go to drivers - download nvidia drivers, download 314.22 whql. While installing, select custom (advanced) install. In the next page, follow this settings:

let us know the results.
I have downgraded my Nvidia driver to the 314.22 version but I have yet to play any games to utilize if it has had any effect. I would however liek to point out that the new driver, 327.23, came out only a few days ago and may have resorted any issues with drivers post 314.22. I hope this is the case since i dislike the thought of an outdated driver.

Quote:
monitor hardware temperature with system monitoring software like speccy or hwmonitor.
Upload a screen shot of the summary tab as well:
current HWmonitor values:
Recurring BSODs often occuring when gaming-hwm1.png
Name:  HWM2.png
Views: 53
Size:  17.8 KB

Should I post another set of values for when the computer is under load?


I have now tried to follow the posted steps accoringly. Hope the information I provide will help in finding a solution to my problems. The hard drive diagnose confused me and the removal of old sys files related to removed programs/drivers I am unsure i performed correctly.
Cheers for the help provided and hopefully the help to come


My System SpecsSystem Spec
.


24 Sep 2013   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Since SFC couldn't fix the errors I think it's best you do a Repair install. Also do you have any device attached to your USB ports? Unplug and safely remove except the essential ones.
My System SpecsSystem Spec
05 Oct 2013   #5

Windows 7 Professional x64
 
 

SFC is no longer reporting any errors. So far my system has been running without a problem for approximately a week.
One question though, When would it be "safe" to update my graphics driver?
My System SpecsSystem Spec
11 Oct 2013   #6

Windows 7 Professional x64
 
 

I just now received this bluescreen: 101213-26052-01.zip

My system has been running smooth up to this point after previous fixings.


My System SpecsSystem Spec
12 Oct 2013   #7

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\101213-26052-01\101213-26052-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\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 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02014000 PsLoadedModuleList = 0xfffff800`022576d0
Debug session time: Sat Oct 12 05:20:06.058 2013 (UTC + 6:00)
System Uptime: 0 days 22:02:29.792
Unable to load image \SystemRoot\system32\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
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800dc4c028, b62ea000, 2e000175}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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 : AuthenticAMD

Followup: MachineOwner
---------
My System SpecsSystem Spec
13 Oct 2013   #8

Windows 7 Professional x64
 
 

I removed the software my new external installed and formatted the external drive. it now seems to work without causing hal.dll to spazz out. I believe the new external to be the cause since the x124's started pretty much directly after i started using it.

I do however have another issue that I believe is USB related and i could use some input if not too much to ask.
Using an intous 4 drawing pad together with Sculptris seem to caused the following BSODs: minidumps.zip
I wonder if its a case of my USB ports/Drivers gone wacky or simply the software not liking each other.

Anyways, thanks for any imput on this, and sorry for stealing so much of your time.


My System SpecsSystem Spec
13 Oct 2013   #9

Windows 7 Home Premium x64
 
 

Wrek, Hello .
We (the debugging community) are experiencing technical difficulties at the moment as there appears
issues with the public symbols server which we are dependent upon in order to read the dump files
in a meaningful manner.
As things stand patience must be at the utmost of priority.

Thank you for understanding.
My System SpecsSystem Spec
15 Oct 2013   #10

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by YoYo155 View Post
Wrek, Hello .
We (the debugging community) are experiencing technical difficulties at the moment as there appears
issues with the public symbols server which we are dependent upon in order to read the dump files
in a meaningful manner.
As things stand patience must be at the utmost of priority.

Thank you for understanding.
Take your time ^_^
My System SpecsSystem Spec
Reply

 Recurring BSODs often occuring when gaming




Thread Tools



Similar help and support threads for2: Recurring BSODs often occuring when gaming
Thread Forum
Multiple BSOD occuring while gaming/startup (ntoskrnl.exe++) BSOD Help and Support
Solved Recurring BSODs before/after startup BSOD Help and Support
Recurring BSODs with various STOP errors BSOD Help and Support
Randomly occuring 7f BSoDs BSOD Help and Support
PLEASE help me with recurring BSOD problems! Get them while gaming. BSOD Help and Support
Recurring BSODs BSOD Help and Support
Recurring BSoDs BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:25 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33