Quite a few BSOD's going today.

EDIT : added zip file.

I am VERY worried. First of all here are my system specs :

Intel Quad Core Q9550 CPU @ 2.83ghz
6 gigs of Corsair Dominator 1066 DDR2 ram
PNY Quadro FX 1700 512MB
Asus P5Q Deluxe motherboard
WD CaviarBlack 760gig HDD

Windows 7 64 bits Professional

---

I understand that my rig is not intended for gaming, but I do game once in a while. I now bought Starcraft II, I played the beta and everything went fine. I am runing the latest Quadro Graphics drivers from Nvidia and I am getting good performance at low settings in that game.

Since 3 days I once in a while get the error message where my keyboard ( Razer Tarantula ) is not recognized. It is not the only USB device i have plugged in, I also have a wacom intuos 4 and a Razer mice aswell. But now this is getting frequent. And today was horrible. I got 4 BSOD's today. I have not overclocked anything and my Bios has always been under default settings. Here are my codes. I havent unfortunatly saved the first one.


Could this lead to faulty hardware? I got the first 3 while playing Starcraft II ( ive been playing since 3 months, I had the beta, and never got anything like this) and the last one while opening firefox. I have performed CC cleaner and I have my Asus Probe up... my temperature seems quite stable. I have dusted EVERY SINGLE hardware on my computer.

I am very unsure about all this. Any suggestions?

Several different codes may very well be hardware, the most likely memory. Lets not guess, follow these instructions and we can all find out the cause
https://www.sevenforums.com/crashes-d...tructions.html

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (go to top of page)
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (go to top of page)
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (go to top of page)
Usual causes: System service, Device driver, graphics driver, ?memory

Code:

opyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_WIN7BSODJCGRIFFPERFMON[1].zip\Windows7_BSOD_jcgriff2\081910-18626-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: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Thu Aug 19 20:56:25.664 2010 (GMT-4)
System Uptime: 0 days 10:00:35.350
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800577bce5, fffff880009fc6a8, fffff880009fbf10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )
Followup: MachineOwner
---------
2: kd> !analyze -v

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_WIN7BSODJCGRIFFPERFMON[1].zip\Windows7_BSOD_jcgriff2\082210-17316-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: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50
Debug session time: Sun Aug 22 22:16:00.546 2010 (GMT-4)
System Uptime: 0 days 4:59:12.232
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3D, {fffff88002ffc8e0, 0, 0, fffff8800578b3eb}
Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )

Code:

icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_WIN7BSODJCGRIFFPERFMON[1].zip\Windows7_BSOD_jcgriff2\082310-18876-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: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Mon Aug 23 15:19:56.314 2010 (GMT-4)
System Uptime: 0 days 5:19:26.000
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )
Followup: MachineOwner
---------

Code:

icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_WIN7BSODJCGRIFFPERFMON[1].zip\Windows7_BSOD_jcgriff2\082310-19936-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: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02e9ee50
Debug session time: Mon Aug 23 20:50:14.766 2010 (GMT-4)
System Uptime: 0 days 2:34:14.451
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002cc7ed9, fffff880095da3f0, 0}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+1d24a3 )
Followup: MachineOwner
---------

Outdated Drivers
Lachesis Lachesis.sys Fri Aug 17 03:48:44 2007
AsIO AsIO.sys Mon Apr 06 03:21:08 2009
ASACPI ASACPI.sys Wed May 13 21:25:17 2009
amdxata amdxata.sys Tue May 19 13:56:59 2009



You have presented 6 dump reports. with 4 different codes.

Probable Causes as given. Two of the reports make reference to network issues.
netio.sys a networking inssue
and dxgmms1.sys video card issue
The other reports gave probable causes that are highly unlikley and will not be addressed at this juncture
Taken as a whole the most likely cause of your problem would be a network related issue, driver issue (especially related to video or graphics), memory

Suggested Solution
Download memtest86 and test RAM
RAM - Test with Memtest86+

Scan with your Anti Virus

SFC /scannow
https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. Update drivers listed as probable causes. Update drivers for graphic and networking

Asacpi.sys is a driver from the Austek Computer Corp. Your driver is old and may be a cause BSOS's in current Windows versions; it must be updated
http://support.asus.com/download/dow...Language=en-us

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 help you 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
- - 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 manufacturer links are on this page: Drivers and Downloads
To remove any left over driver remnants, especially from graphics cards, use driver sweeper http://www.guru3d.com/category/driversweeper/




After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.

Please remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.

Fungole

First thanks for the rep.

Take your time with the computer, work at your own pace. I will be here to help when you have questions or problems. I think that your problem may be solved after you follow the given suggestions. If you do get another BSOD, just post and we will use that information in conjunction with what we know and get closer to the final answer.
The minidumps give clues they are not definitive; it is trial and error.

Thanks again for you kind words.

Heres some free information
Want to know what drivers you have and their date?

I will assume that you are shaking your head yes.

In search, type cmd
In cmd type driverquery.

Now you will know if the driver has been installed.

This one is my treat, take care.