Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

Multiple BSODs - Win8 x64 - can't troubleshoot myself

This is a discussion on Multiple BSODs - Win8 x64 - can't troubleshoot myself within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. Hi, I'm an engineering student and I'm trying hard to troubleshoot my BSODs problems born with the installation of Windows


Closed Thread
 
Thread Tools Search this Thread
Old 04-22-2013, 08:05 AM   #1
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System

Cry

Hi,
I'm an engineering student and I'm trying hard to troubleshoot my BSODs problems born with the installation of Windows 8 x64 and/or of a new SSD. I see this forum is full of highly technical answers I liked and also good helpers so I chose to register for your help.

Let's follow your guidelines.
Sys details (in my profile too) are:
OS - Windows 8 with Media Center (never used, just grabbed the offer!)
OS Arch - x64
OS install mode - Clean
OS type - Full clean version in my language (ITA) (edu license + free media center license)
Age of system (hardware) - varies a lot, I upgraded the system progressively, I'll try to put age for each component.
Age of OS installation - installed 11/2012

CPU - Intel Core 2 Quad Q9300 (Yorkfield 45nm - LGA775) - bought 06/2008
Video Card - Sapphire AMD Radeon HD 7870 GHz Edition 2GB GDDR5 - bought 08/2012
Audio Card - Creative SoundBlaster Audigy2 Starter (PCI) - bought 06/2008
MotherBoard - Asus P5K PRO - latest BIOS 1303 (2009.01.22) - bought 06/2008
Power Supply - Corsair HX850 - bought 04/2013

System Manufacturer - me
RAM - 1st dual channel (slot 2,4) 2x1GB OCZ Model OCZ2G11002G (K), spec: PC2-8800 1100Mhz 5-6-6-15 2.3 Volts VDIMM (2.35V Extended Voltage Protection) - Link - bought 06/2008
RAM - 2nd dual channel (slot 1,3) 2x2GB Kingston HyperX Model KHX8500D2K2/4G (Kit), spec: PC2-8500 1066Mhz 5-5-5-15 2.3 Volts VDIMM - Link - bought 08/2012
Settings in BIOS - RAM 1066Mhz - 5-6-6-15 - 2.2 to 2.3V (various tried, no changes noticed) VDIMM. FSB / PCIE / SATA ecc freqs. are all standard, no ASUS intelligent/auto-overclocker is active.
Disk #1 (system) - SSD - Samsung - 256GB - Model 830 Series MZ-7PC256 (on Intel(R) ICH9R/DO/DH SATA AHCI Controller SATA 2.0 3Gb/s) - bought 11/2012
Disk #2 - HDD - Seagate - 2TB - Model Barracuda ST2000DM001-1CH164 (on Intel(R) ICH9R/DO/DH SATA AHCI Controller SATA 2.0 3Gb/s) - bought approx 03/2012
Disk #3 - HDD - Seagate - 320GB - Model Barracuda ST3320620A (on Marvell 88SE6102 PATA controller UDMA/100) - bought 06/2008
CDDVD/RW - Samsung - SH-224BB - bought 2012
Screen #1 - ASUS - VH226 FULL HD - HDMI - bought 04/2009
Screen #2 - Philips TV - 37PF9830/10 FULL HD - DVI - used occasionally for gaming or remote PVR with XBMC.

External devices - 1. Logitech mouse MX600 receiver (wireless) 2. Logitech Illuminated Keyboard (wires) 3. Logitech HD Pro Webcam C910.

Things I already tried:
  1. sfc /scannow - no problems
  2. chkdsk on every disk - no problems
  3. System Update Readiness Tool by Microsoft for Windows 8 KB947821 - no problems
  4. Since RAM is the most dubious part, I tested if it's working and set properly.
    I run tests on:
    ╖ 1 module at a time & 2xOCZ & 2xKingston & all ram installed.
    with:
    ╖ Windows Diagnostic complete - no errors at all
    ╖ memtest86+ with startup ISO - no errors at all
  5. Temperatures are ok, machine is in a big case (can't remember brand/model) and highly ventilated.
  6. I tried some OCCT tests and I am actually getting an error after some minutes: "Error detected". Reading their FAQ this means the pc badly did some calculation for sure. No BSODs while doing these tests.
  7. This morning I uninstalled Kaspersky Internet Security 2013. Defender activated itself.
  8. Upgraded ATK0110 ACPI driver by Asus to 1043.6.0.0 as suggested in other threads.
  9. Upgraded as much as possible any Intel/Marvel driver found and AMD graphics drivers. The same with external devices.
  10. Made the verifier tool of Windows do the tests as suggested in the dedicated thread, since today. I limited it to the audio drivers because it's the oldest component of the system with low to no official Windows 8 support announced (drivers seem good, signed 10/2012 and all works btw). And...I just had two BSODs while writing! The filename shown in the BS indicates a Creative driver: hap16v2k.sys . The Nirsoft tool is NOT indicating it as the cause, but:
    ╖ 042213-16536-01.dmp 22/04/2013 15.58.39 SYSTEM_SERVICE_EXCEPTION HIDPARSE.SYS x64 ntoskrnl.exe C:\Windows\Minidump\042213-16536-01.dmp and
    ╖ 042213-13322-01.dmp 22/04/2013 16.19.21 DRIVER_IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe ntoskrnl.exe x64 ntoskrnl.exe C:\Windows\Minidump\042213-13322-01.dmp
    I'm doing another complete log/dump with your tool and I am attaching it. What do you think about this, can the badly supported audio card be causing my issues?
  11. PS/2 drivers of mouse and keyboard keep appearing in devices management, even after uninstalling them, if I enable viewing of hidden devices. They have a yellow check mark and the error is that device is not present or not working properly or with drivers missing. In fact no PS/2 device is attached. Don't know if this is important or not.

The BSODs that occur are very random, not linked with what I use the pc for. They are occurring since I used/installed Win8 and the SSD (same time).
Knowing this, I must give some more details on an issue I had to troubleshoot at the same time...

After having tried first Win8 installation/s I had problems with the PC not booting at all. This was due to the Window's "System Reserved" partition at the beginning of the disk. In fact I didn't have the System Reserved partition at all with Win7 and had no problems at all before (in another disk, now detached). Win8 generated it again as it was a clean install in the SSD and BIOS would stop the boot at POST, while detecting drives, due to a known BIOS+chipset bug that has never been fixed that can cause the hang if the first partition is littler than (some) GB. This is what I read on the net and in fact after having enlarged the System Reserved Partition (right after a 100% clean install and first reboot for first boot) all went fine (it's 5GB now). To do this I hot-plugged the drive after having booted the PC into a live Unix system (this way it would go past the POST and work ok), took apart the System Reserved, enlarged it (with gparted), and then I went on with the first boot. Layout of the SSD is now as follows:
1st part - 210 GB - Win8 partition
2nd part - 5 GB - Win8 System Reserved partition
3rd part - 24 GB - Over Provisioning dedicated unallocated space.

I usually get the BSODs while working at the pc as a website developer, just browsing the web or playing. Not necessarily listening to music/audio. Never had BSODs when leaving the TV on for hours for watching movies/PVR with XBMC. I am also occasionally using the PC for playing with friends. This involves using the MotionInJoy driver and BT adapter installed that makes PS3 controllers work as an xbox controller. The BT adapter, driver and application are (usually) not attached and active when I get BSODs, they aren't attached and active at all while not playing and I'm still getting all the BSODs in these situations.

p.s. the BSOD_Windows7_Vista_v2.64_jcgriff2_.exe is hanging at the end echoing always "Waiting for SystemInfo", while msinfo32 did its work and closed as far as I can understand. I guess it's alright anyway...isn't it?

Thanks for reading the longest post ever. Sorry. I'm really out of ideas and I tried so many. I think as much information as possible can help troubleshooting this, hope you agree and this is gonna be the case
Have a nice day,
Matteo.
Attached Files
File Type: zip cmatte_Windows7_Vista_jcgriff2.zip (4.83 MB, 1640 views)
cmatte is offline  
Sponsored Links
Advertisement
 
Old 04-22-2013, 11:32 AM   #2
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


I want to add that I used the autorun tool and it was seeing some problems with audio items of the registry that indicated the specified files wasn't in the expected path.
I installed the drivers again and all is ok now. The only problem remained is a missing dll an autorun item is trying to register at boot. I found out the file that was in a different folder due to x64 and the same file in the same folder but with a 64(.dll) suffix so I registered both successfully and changed the:
regsvr32 /s ctasio.dll TO
regsvr32 /s ctasio64.dll .

Regards,
Matteo.
cmatte is offline  
Old 04-23-2013, 12:34 AM   #3
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,368
OS: Windows 10, 8.1 + Windbg :)



Quote:
Originally Posted by cmatte View Post

. . . the BSOD_Windows7_Vista_v2.64_jcgriff2_.exe is hanging at the end echoing always "Waiting for SystemInfo", while msinfo32 did its work and closed as far as I can understand. I guess it's alright anyway...isn't it?
Hi Matteo,

The jcgriff2 file collection app will usually show the "waiting for systeminfo" message for an extended period of time when the Windows Error Reporting (WERCON) section gets overloaded due to BSODs, APPCRASHes, APPHANGs, etc...

Your WERCON section contained 3,329 entries, 79 of which were BSODs (Windows 8 & Windows 7 only retain 50 mini kernel dumps; older ones are auto-deleted by Windows). The WERCON entries begin on the day Windows was installed - 26 October 2012. Please note that not all WERCON entries are severe errors -- some are simple system events such as a USB driver being loaded or perhaps one not being found. Shutting it down caused no problems at all in this case.

I would suggest updating MotioninJoy simulate Xbox 360 controller (virtual Xinput device) - your's is from 2004 -
Code:
ctgame.sys                  Tue Apr  6 20:42:49 2004 (40734E89) 
xusb21.sys                  Wed Apr  8 10:28:44 2009 (49DCB49C)
http://www.sysnative.com/drivers/driver.php?id=ctgame.sys
http://www.sysnative.com/drivers/driver.php?id=xusb21.sys


Several of your Creative Audio drivers were named in BSODs -
Code:
ctoss2k.sys                 Thu Oct 11 09:15:06 2012 (5076C65A) 
ctac32k.sys                 Thu Oct 11 09:18:10 2012 (5076C712)
ctaud2k.sys                 Thu Oct 11 09:15:48 2012 (5076C684)
ctprxy2k.sys                Thu Oct 11 09:15:52 2012 (5076C688)
ctsfm2k.sys                 Thu Oct 11 09:14:55 2012 (5076C64F)
emupia2k.sys                Thu Oct 11 09:14:51 2012 (5076C64B) 
ha10kx2k.sys                Thu Oct 11 09:15:09 2012 (5076C65D)
hap16v2k.sys                Thu Oct 11 09:15:13 2012 (5076C661) 
http://www.sysnative.com/drivers/driver.php?id=CTAUDFX.SYS
http://www.sysnative.com/drivers/driver.php?id=ctac32k.sys
http://www.sysnative.com/drivers/driver.php?id=ctaud2k.sys
http://www.sysnative.com/drivers/driver.php?id=ctoss2k.sys
http://www.sysnative.com/drivers/driver.php?id=ctprxy2k.sys
http://www.sysnative.com/drivers/driver.php?id=ctsfm2k.sys
http://www.sysnative.com/drivers/driver.php?id=emupia2k.sys
http://www.sysnative.com/drivers/driver.php?id=ha10kx2k.sys
http://www.sysnative.com/drivers/driver.php?id=hap16v2k.sys


Remove Daemon Tools for now -
Code:
dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)  
http://www.sysnative.com/drivers/driver.php?id=dtsoftbus01.sys


Update Intel storage driver -
Code:
iaStor.sys                  Mon Sep 13 21:23:32 2010 (4C8ECE94) 
http://www.sysnative.com/drivers/driver.php?id=iaStor.sys


I would recommend removal of Kaspersky Internet Security for now - at least until BSOD epidemic is over -
Code:
kl1.sys                     Tue Jun 19 09:27:15 2012 (4FE07E33)
klflt.sys                   Tue Mar 26 10:44:39 2013 (5151B457)
klif.sys                    Tue Mar 26 11:05:41 2013 (5151B945)
klim6.sys                   Thu Aug  2 07:08:40 2012 (501A5FB8)
klkbdflt.sys                Mon Sep  3 09:54:42 2012 (5044B6A2)
klmouflt.sys                Mon Sep  3 10:20:14 2012 (5044BC9E)
klwfp.sys                   Wed Feb 27 03:48:31 2013 (512DC85F)
kneps.sys                   Tue Mar  5 04:09:23 2013 (5135B643)
http://www.sysnative.com/drivers/driver.php?id=kl1.sys
http://www.sysnative.com/drivers/driver.php?id=klflt.sys
http://www.sysnative.com/drivers/driver.php?id=klif.sys
http://www.sysnative.com/drivers/driver.php?id=klim6.sys
http://www.sysnative.com/drivers/driver.php?id=klkbdflt.sys
http://www.sysnative.com/drivers/driver.php?id=klmouflt.sys

Remove KIS with removal tool - https://kb.eset.com/esetkb/index?page=content&id=SOLN146

Reboot upon completion. Install Microsoft Security Essentials (MSE)

Regards. . .

jcgriff2


`

BSOD SUMMARY
Code:

Debug session time: Mon Apr 22 10:18:25.119 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\042213-13322-01.dmp]
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
System Uptime: 0 days 0:19:59.922
*** WARNING: Unable to verify timestamp for hap16v2k.sys
*** ERROR: Module load completed but symbols could not be loaded for hap16v2k.sys
*** WARNING: Unable to verify timestamp for ctoss2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctoss2k.sys
*** WARNING: Unable to verify timestamp for ha10kx2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha10kx2k.sys
*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
Probably caused by : hap16v2k.sys ( hap16v2k+27d3c )
BugCheck D1, {48, 2, 1, fffff88001427d3c}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000048, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001427d3c, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_AV_hap16v2k+27d3c
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Apr 22 09:57:39.056 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\042213-16536-01.dmp]
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
System Uptime: 0 days 4:04:26.858
*** WARNING: Unable to verify timestamp for ha10kx2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha10kx2k.sys
*** WARNING: Unable to verify timestamp for emupia2k.sys
*** ERROR: Module load completed but symbols could not be loaded for emupia2k.sys
Probably caused by : ha10kx2k.sys ( ha10kx2k+d3b3d )
BugCheck 3B, {c0000005, fffff88006d48b3d, fffff8800965e360, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88006d48b3d, Address of the instruction which caused the bugcheck
Arg3: fffff8800965e360, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_ha10kx2k+d3b3d
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Apr 22 04:28:46.783 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\042213-15600-01.dmp]
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
System Uptime: 1 days 19:34:24.342
Probably caused by : memory_corruption ( nt!MiApplyCompressedFixups+60 )
BugCheck 1E, {ffffffffc0000005, fffff800416878ef, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800416878ef, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1e_c0000005
PROCESS_NAME:  GOContactSync.
FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!MiApplyCompressedFixups+60
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Apr 13 14:15:05.547 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\041313-13884-01.dmp]
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
System Uptime: 0 days 8:27:41.205
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+4f9 )
BugCheck 3B, {c0000005, fffff802e7432e06, fffff8800cf9c040, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff802e7432e06, Address of the instruction which caused the bugcheck
Arg3: fffff8800cf9c040, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectByHandleWithTag+4f9
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Fri Apr 12 18:48:33.451 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\041313-15210-01.dmp]
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
System Uptime: 0 days 11:04:52.133
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntkrnlmp.exe ( nt!FsRtlCheckOplockEx+168 )
BugCheck 1000007E, {ffffffffc0000005, fffff803198bd178, fffff88003755558, fffff88003754d90}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff803198bd178, The address that the exception occurred at
Arg3: fffff88003755558, Exception Record Address
Arg4: fffff88003754d90, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_nt!FsRtlCheckOplockEx+168
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Tue Apr  9 06:21:06.537 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040913-14383-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 1 days 11:10:36.122
Probably caused by : win32k.sys ( win32k!_VisrgnFromWindow+f )
BugCheck 3B, {c0000005, fffff9600022883f, fffff8801151b080, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600022883f, Address of the instruction which caused the bugcheck
Arg3: fffff8801151b080, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  MediaMonkey.ex
FAILURE_BUCKET_ID:  X64_0x3B_win32k!_VisrgnFromWindow+f
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sun Apr  7 18:33:31.296 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040813-13696-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 2:50:51.008
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+346 )
BugCheck 1000007E, {ffffffffc0000005, fffff8800785f682, fffff8800ab86728, fffff8800ab85f60}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800785f682, The address that the exception occurred at
Arg3: fffff8800ab86728, Exception Record Address
Arg4: fffff8800ab85f60, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+346
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Apr  6 18:12:39.977 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040713-7113-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:45:00.695
Probably caused by : ntkrnlmp.exe ( nt!IopXxxControlFile+332 )
BugCheck 3B, {c0000005, fffff8013aac7e80, fffff8800bb86fa0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8013aac7e80, Address of the instruction which caused the bugcheck
Arg3: fffff8800bb86fa0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  NFS13.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!IopXxxControlFile+332
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Apr  6 14:51:56.629 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040613-23103-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:00:15.439
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+1c3eb )
BugCheck C2, {9b, 1, 20, fffff88006f3c3eb}
BugCheck Info: BAD_POOL_CALLER (c2)
Bugcheck code 000000c2
Arguments: 
Arg1: 000000000000009b, Attempt to allocate pool with a tag of zero.  This would make the pool untrackable and worse, corrupt the existing tag tables.
Arg2: 0000000000000001, Pool type
Arg3: 0000000000000020, Size of allocation in bytes
Arg4: fffff88006f3c3eb, Caller's address.
BUGCHECK_STR:  0xc2_9b
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc2_9b_MijXfilt+1c3eb
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Apr  6 14:10:33.195 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040613-7503-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 22:48:05.863
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+396c )
BugCheck D1, {f36938, 2, 0, fffff8800686f96c}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000f36938, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800686f96c, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_AV_intelppm+396c
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Fri Apr  5 15:15:34.287 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040513-7862-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 1:50:22.980
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+4a )
BugCheck 1000007E, {ffffffffc0000005, fffff88006a2667e, fffff8800977f628, fffff8800977ee60}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006a2667e, The address that the exception occurred at
Arg3: fffff8800977f628, Exception Record Address
Arg4: fffff8800977ee60, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+4a
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Apr  3 14:14:27.939 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040313-7300-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:10:52.656
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+ac )
BugCheck 1000007E, {ffffffffc0000005, fffff80341cfca76, fffff88008370738, fffff8800836ff70}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80341cfca76, The address that the exception occurred at
Arg3: fffff88008370738, Exception Record Address
Arg4: fffff8800836ff70, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_dxgkrnl!DpSynchronizeExecution+ac
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Apr  3 14:02:46.061 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040313-7254-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 4:35:35.729
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+2392c )
BugCheck A0000001, {5, 0, 0, 0}
BugCheck Info: Unknown bugcheck code (a0000001)
Bugcheck code a0000001
Arguments: 
Arg1: 0000000000000005
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0xA0000001
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  NFS13.exe
FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+2392c
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Apr  3 09:14:41.208 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040313-7690-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:35:03.925
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+21 )
BugCheck 3B, {c0000005, fffff801770d3aa6, fffff8800fcbbff0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801770d3aa6, Address of the instruction which caused the bugcheck
Arg3: fffff8800fcbbff0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+21
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Apr  3 08:38:10.808 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040313-7441-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:21:27.525
Probably caused by : win32k.sys ( win32k!HmgSetOwner+1ed )
BugCheck 50, {ffffea825ba7a76b, 0, fffff960001d3f7d, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: ffffea825ba7a76b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960001d3f7d, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  MediaMonkey.ex
FAILURE_BUCKET_ID:  X64_AV_win32k!HmgSetOwner+1ed
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Tue Apr  2 19:13:33.086 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040313-8938-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 1:41:45.802
Probably caused by : ntkrnlmp.exe ( nt!IopXxxControlFile+360 )
BugCheck 3B, {c0000005, fffff8021167cee1, fffff8800e163fd0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8021167cee1, Address of the instruction which caused the bugcheck
Arg3: fffff8800e163fd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  XBMC.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!IopXxxControlFile+360
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Tue Apr  2 17:30:53.290 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040213-8174-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 4:16:21.982
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+318 )
BugCheck 50, {fffffa9800395218, 0, fffff8030bad0fa7, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: fffffa9800395218, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8030bad0fa7, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  fifa13.exe
FAILURE_BUCKET_ID:  X64_AV_nt!MiDeleteAddressesInWorkingSet+318
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Tue Apr  2 13:13:39.538 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040213-7722-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 21:32:13.156
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )
BugCheck 10D, {5, 0, 1202, fffffa8009c849d0}
BugCheck Info: WDF_VIOLATION (10d)
Bugcheck code 0000010D
Arguments: 
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
	a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001202, Reserved.
Arg4: fffffa8009c849d0, Reserved.
BUGCHECK_STR:  0x10D_5
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Apr  1 15:40:37.187 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040113-7441-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 3:42:08.904
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+21 )
BugCheck 3B, {c0000005, fffff8004acc9aa6, fffff8800ecd0030, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8004acc9aa6, Address of the instruction which caused the bugcheck
Arg3: fffff8800ecd0030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  SetPoint.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGADAPTER::AcquireCoreResourceShared+21
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Apr  1 08:20:59.791 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040113-8517-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 2 days 1:11:39.677
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : Ntfs.sys ( Ntfs+11742 )
BugCheck 24, {b50019060b, fffff88012f23d38, fffff88012f23570, fffff801c36ca58f}
BugCheck Info: NTFS_FILE_SYSTEM (24)
Bugcheck code 00000024
Arguments: 
Arg1: 000000b50019060b
Arg2: fffff88012f23d38
Arg3: fffff88012f23570
Arg4: fffff801c36ca58f
PROCESS_NAME:  avp.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs+11742
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Mar 30 06:40:31.686 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\033013-5616-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:08:09.403
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReleasePendingResources+18 )
BugCheck 1000007E, {ffffffffc0000005, fffff88006c813f8, fffff88009346638, fffff88009345e70}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006c813f8, The address that the exception occurred at
Arg3: fffff88009346638, Exception Record Address
Arg4: fffff88009345e70, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VIDMM_GLOBAL::ReleasePendingResources+18
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Mar 30 06:28:43.511 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\033013-8236-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 10:59:25.203
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+1595e5 )
BugCheck 3B, {c0000005, fffff880085c35e5, fffff88010d30c60, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880085c35e5, Address of the instruction which caused the bugcheck
Arg3: fffff88010d30c60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  XBMC.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+1595e5
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Fri Mar 29 19:28:31.117 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\033013-7831-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 6:53:23.833
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchWaitForEvents+15b )
BugCheck 1000007E, {ffffffffc0000096, fffff801faaab9e3, fffff88005bea598, fffff88005be9dd0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff801faaab9e3, The address that the exception occurred at
Arg3: fffff88005bea598, Exception Record Address
Arg4: fffff88005be9dd0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VidSchWaitForEvents+15b
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Fri Mar 29 12:33:55.736 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032913-13884-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 2 days 21:43:28.283
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : hardware ( atikmdag+104fc3 )
BugCheck 1000007E, {ffffffff80000004, fffff880085cefc3, fffff88009167388, fffff88009166bc0}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffff80000004, The exception code that was not handled
Arg2: fffff880085cefc3, The address that the exception occurred at
Arg3: fffff88009167388, Exception Record Address
Arg4: fffff88009166bc0, Context Record Address
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_atikmdag.sys
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Tue Mar 26 14:49:41.353 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032613-7347-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:06:52.069
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a7 )
BugCheck 1000007E, {ffffffffc0000005, fffff88006a266db, fffff880051dd628, fffff880051dce60}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006a266db, The address that the exception occurred at
Arg3: fffff880051dd628, Exception Record Address
Arg4: fffff880051dce60, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a7
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Tue Mar 26 14:41:55.835 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032613-8486-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 1 days 7:47:23.428
Probably caused by : win32k.sys ( win32k!xxxInternalDoPaint+63 )
BugCheck 3B, {c0000005, fffff960002b6573, fffff8800e740db0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960002b6573, Address of the instruction which caused the bugcheck
Arg3: fffff8800e740db0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  OUTLOOK.EXE
FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxInternalDoPaint+63
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Mar 25 06:46:33.306 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032513-9266-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 13:19:30.998
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 1000007F, {8, fffff880034d6cb0, 0, fffff880086c6706}
BugCheck Info: UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
Bugcheck code 1000007F
Arguments: 
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff880034d6cb0
Arg3: 0000000000000000
Arg4: fffff880086c6706
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  csrss.exe
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sun Mar 24 17:26:14.086 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032413-7924-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 4:45:53.802
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ClearTrimmedList+10 )
BugCheck 1000007E, {ffffffffc0000005, fffff8800682d2e8, fffff88008f685e8, fffff88008f67e20}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800682d2e8, The address that the exception occurred at
Arg3: fffff88008f685e8, Exception Record Address
Arg4: fffff88008f67e20, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VIDMM_GLOBAL::ClearTrimmedList+10
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sun Mar 24 12:39:26.599 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032413-9094-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 21:48:05.267
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : tcpip.sys ( tcpip+8d756 )
BugCheck 1E, {ffffffffc0000005, fffff880022db756, fffff8800e7a1e78, fffff8800e7a16b0}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880022db756, The address that the exception occurred at
Arg3: fffff8800e7a1e78, Parameter 0 of the exception
Arg4: fffff8800e7a16b0, Parameter 1 of the exception
BUGCHECK_STR:  0x1e_c0000005
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1e_c0000005_tcpip+8d756
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Mar 23 14:48:54.501 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032313-7503-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 5:02:41.218
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : Ntfs.sys ( Ntfs+cc44b )
BugCheck 24, {b50019060b, fffff8800d7bbf98, fffff8800d7bb7d0, fffff8034e70c0dd}
BugCheck Info: NTFS_FILE_SYSTEM (24)
Bugcheck code 00000024
Arguments: 
Arg1: 000000b50019060b
Arg2: fffff8800d7bbf98
Arg3: fffff8800d7bb7d0
Arg4: fffff8034e70c0dd
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x24_Ntfs+cc44b
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Mar 23 09:45:20.767 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032313-7472-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 14:46:40.458
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::Present+c19 )
BugCheck 3B, {c0000005, fffff801b3c54bca, fffff8800ea20ad0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801b3c54bca, Address of the instruction which caused the bugcheck
Arg3: fffff8800ea20ad0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGCONTEXT::Present+c19
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Fri Mar 22 18:57:39.634 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032213-7176-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:27:27.351
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+4a )
BugCheck 1000007E, {ffffffffc0000005, fffff88006a8b67e, fffff88008f5d628, fffff88008f5ce60}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006a8b67e, The address that the exception occurred at
Arg3: fffff88008f5d628, Exception Record Address
Arg4: fffff88008f5ce60, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+4a
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Fri Mar 22 18:29:10.614 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032213-7503-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 1:39:46.331
Probably caused by : win32k.sys ( win32k!SfnDWORD+15b )
BugCheck 1A, {5100, fffff6fc40094dc0, 3, ffffffffffffff00}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6fc40094dc0
Arg3: 0000000000000003
Arg4: ffffffffffffff00
BUGCHECK_STR:  0x1a_5100
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x1a_5100_win32k!SfnDWORD+15b
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Tue Mar 19 20:33:38.532 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032013-7940-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 6:06:42.250
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+3f )
BugCheck D1, {80052b8010, a, 0, fffff880067876ff}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 00000080052b8010, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880067876ff, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+3f
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Mar 18 21:40:21.845 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031913-8533-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 13:45:12.562
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1d4ef )
BugCheck 1A, {5005, fffff70001080000, 2676, 9baf}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000005005, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000002676
Arg4: 0000000000009baf
BUGCHECK_STR:  0x1a_5005
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_5005_nt!_??_::FNODOBFM::_string_+1d4ef
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Mar 18 07:54:12.556 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031813-11746-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 18:47:32.223
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1de8d )
BugCheck 1A, {41284, edcf001, a6a7, fffff70001080000}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000000000edcf001
Arg3: 000000000000a6a7
Arg4: fffff70001080000
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+1de8d
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sun Mar 17 13:05:26.928 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031713-7534-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 2:02:14.644
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : memory_corruption ( nt!MiLockDataControlArea+89 )
BugCheck A, {800cb05658, 2, 1, fffff80245b6c0dd}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: 000000800cb05658, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80245b6c0dd, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_AV_nt!MiLockDataControlArea+89
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Mar 16 01:07:29.235 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031613-13291-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 1 days 4:42:37.902
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+2311c )
BugCheck A0000001, {5, 0, 0, 0}
BugCheck Info: Unknown bugcheck code (a0000001)
Bugcheck code a0000001
Arguments: 
Arg1: 0000000000000005
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0xA0000001
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+2311c
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Thu Mar 14 20:22:37.118 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031513-7987-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 3 days 10:34:53.713
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+a7 )
BugCheck 50, {fffffa836ff2dbe0, 1, fffff8030b2b67a7, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: fffffa836ff2dbe0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8030b2b67a7, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_AV_nt!PoIdle+a7
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sun Mar 10 18:58:08.276 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031013-8190-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 21:20:51.845
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+d5 )
BugCheck 1E, {ffffffffc0000005, fffff801aa6a5665, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801aa6a5665, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1e_c0000005
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!KiSwapContext+d5
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Mar  9 21:36:07.144 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031013-7566-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 1 days 3:58:26.738
Probably caused by : win32k.sys ( win32k!xxxSimpleDoSyncPaint+4f )
BugCheck 3B, {c0000005, fffff96000074caf, fffff8800676bed0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000074caf, Address of the instruction which caused the bugcheck
Arg3: fffff8800676bed0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxSimpleDoSyncPaint+4f
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Fri Mar  8 17:36:28.903 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030813-8190-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 3 days 6:24:54.351
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : afd.sys ( afd+4cbc3 )
BugCheck 3B, {c0000005, fffff88003e89bc3, fffff8800e812e70, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88003e89bc3, Address of the instruction which caused the bugcheck
Arg3: fffff8800e812e70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  WinSCP.exe
FAILURE_BUCKET_ID:  X64_0x3B_afd+4cbc3
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sun Mar  3 18:47:31.669 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030313-7425-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 10:20:27.311
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchStMxCsr+94 )
BugCheck 1E, {ffffffffc0000096, fffff800ab6a19e3, 0, 0}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff800ab6a19e3, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1e_c0000096
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1e_c0000096_nt!SwapContext_PatchStMxCsr+94
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Feb 27 14:26:24.259 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\022713-7472-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 4:30:54.951
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+3ba00 )
BugCheck D1, {18, a, 0, fffff88006ed2a00}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000018, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88006ed2a00, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_AV_atikmpag+3ba00
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Feb 27 09:54:38.552 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\022713-7612-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 2 days 4:11:40.097
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+f )
BugCheck 3B, {c0000005, fffff80217cddcaf, fffff880101015f0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80217cddcaf, Address of the instruction which caused the bugcheck
Arg3: fffff880101015f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiFindNodeOrParent+f
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Feb 25 05:41:28.051 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\022513-7800-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 1 days 9:28:03.448
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+9410 )
BugCheck 116, {fffffa80080494d0, fffff88006e97410, 0, d}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Bugcheck code 00000116
Arguments: 
Arg1: fffffa80080494d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006e97410, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Sat Feb 23 20:06:04.064 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\022413-7628-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 8:01:20.756
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+14 )
BugCheck 50, {fffff8ac01678480, 0, fffff801e236a234, 2}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: fffff8ac01678480, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801e236a234, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_AV_nt!MiCaptureProtectionFromProto+14
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Wed Feb 20 21:21:47.950 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\022113-7706-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 2 days 1:24:15.398
*** WARNING: Unable to verify timestamp for ha10kx2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha10kx2k.sys
Probably caused by : ha10kx2k.sys ( ha10kx2k+bc8b1 )
BugCheck 1E, {ffffffffc0000005, fffff88008d318b1, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88008d318b1, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1e_c0000005
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1e_c0000005_ha10kx2k+bc8b1
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Feb 18 19:56:42.981 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\021913-12027-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 12:05:06.698
Probably caused by : WppRecorder.sys ( WppRecorder!WppAutoLogTrace+14a )
BugCheck 1E, {ffffffffc0000005, fffff880011529ba, 0, ffffffffffffffff}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880011529ba, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1e_c0000005
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1e_c0000005_WppRecorder!WppAutoLogTrace+14a
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Debug session time: Mon Feb 11 07:22:02.119 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\021113-8642-01.dmp]
Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
System Uptime: 0 days 0:07:16.837
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedInsertTailList+2e )
BugCheck D1, {8000009100, 2, 0, fffff8800681182e}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000008000009100, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800681182e, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_AV_dxgmms1!VidSchiInterlockedInsertTailList+2e
MaxSpeed:     2500
CurrentSpeed: 2505
BiosVersion = 1303   
BiosReleaseDate = 12/16/2008
SystemManufacturer = System manufacturer
SystemProductName = P5K PRO
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``

     
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           https://mvp.support.microsoft.com/profile/Griffith   

           www.sysnative.com
             
           www.jcgriff2.com 


ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
jcgriff2 is offline  
Sponsored Links
Advertisement
 
Old 04-23-2013, 02:38 AM   #4
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Hi J.C.,
first of all thanks for your help.
I have some questions about your instructions, because I'm unsure on how to follow them the right way.
Quote:
Originally Posted by jcgriff2 View Post
I would suggest updating MotioninJoy simulate Xbox 360 controller (virtual Xinput device) - your's is from 2004 -
Code:
ctgame.sys                  Tue Apr  6 20:42:49 2004 (40734E89) 
xusb21.sys                  Wed Apr  8 10:28:44 2009 (49DCB49C)
http://www.sysnative.com/drivers/driver.php?id=ctgame.sys
http://www.sysnative.com/drivers/driver.php?id=xusb21.sys
  • First driver ctgame.sys is the newest Creative driver for the available (optionally attachable) game port of the sound card. Creative itself says in the driver it releases that it is NOT supported since Win7. The driver is that old, so, and I am actually unable to find a newer one. I disabled the port from the device manager, should this be enough?
  • About the xusb21.sys driver, I first uninstalled any driver and re-installed it with the MotionInJoy tool. I remember it got updated during 2012 to version it shows actually, 0.7.1001. Then I tried to find a xbox360 device in the device manager and I could find:
    "MotioninJoy Virtual Xinput device for Windows" installed.
    Driver overall shows version 0.6.5.0 of 10/11/2011.
    Driver details show:
    C:\windows\system32\DRIVERS\:
    MijXfilt.sys version 0.5.0002.0 by MotionInJor with no digital signature 05/2012
    xusb21.sys version 9.18.1015.0 by Microsoft signed by Shenzen Saikeware Technology Co., Ltd 12/2011
    C:\Windows\system32\:
    WdfCoInstaller01009.dll version 1.9.7600.16385 (win7_rtm.09713-1255) by Microsoft signed by Shenzen 12/2011
    I went to the link you gave me and downloaded the official xbox 360 drivers for Win7 x64 (Win8 is not listed).
    I installed the software from the gui but, as expected, it didn't update the MotionInJoy device drivers. The same asking Win to look for updated drivers in the folder I extracted the package to. So I checked the files manually and it contains:
    xusb21.sys version 9.18.1034.0 by MS 08/2009
    WdfCoInstaller01009.dll version 1.9.7100.0 by MS 08/2009
    Do you think I should do some sort of collage? If yes, only xusb21.sys? Should I go into safe mode or replace the file only?

Quote:
Originally Posted by jcgriff2 View Post
Update Intel storage driver -
Code:
iaStor.sys                  Mon Sep 13 21:23:32 2010 (4C8ECE94) 
http://www.sysnative.com/drivers/driver.php?id=iaStor.sys
Here I have some problems. I had already tried but I am highly unsure of what/how to install. I usually make Windows decide if the drivers in a package are ok or not, extracting the package and making it look for something new in the folders. I could get to that version that way some weeks ago. Now, doing the same with the drivers you linked doesn't find new stuff and it's the same problem I had before.
First of all, I am trying to update the device:
Intel(R) ICH9R/DO/DH SATA AHCI Controller
PCI\VEN_8086&DEV_2922&SUBSYS_82771043&REV_02
PCI\VEN_8086&DEV_2922&SUBSYS_82771043
PCI\VEN_8086&DEV_2922&CC_010601
PCI\VEN_8086&DEV_2922&CC_0106
That in the details shows only that file:
iaStor.sys 10.0.0.1046 from Intel signed by MS 09/2010
At the Intel website there's:
Intelо Rapid Storage Technology (Intelо RST) RAID Driver - Installs the Intelо Rapid Storage Technology (RAID) driver version 12.5.0.1066. -
OS: Windows Server 2008 *, Windows 7 *, Windows 8*, .. More> Windows Server 2008 *, Windows 7 *, Windows 8*, Windows Server 2008 R2* - 3/22/2013 - Latest
that seems what I need. It has f6flpy-x64.zip and SetupRST.exe . The setup says immediately Platform not supported. The most relevant log I can see of what it tries to do are these:
Code:
2013:04:23 10:34:31:129:   Scanning x64\iaAHCIC.inf (Name: AHCI64, Version: 12.5.0.1066)
2013:04:23 10:34:31:132:     Section with the best match: INTEL.NTamd64.6.2
2013:04:23 10:34:31:136:       Device: PCI\VEN_8086&DEV_3B29&CC_0106 (Intel(R) 5 Series 4 Port SATA AHCI Controller)
2013:04:23 10:34:31:139:       Device: PCI\VEN_8086&DEV_3B2F&CC_0106 (Intel(R) 5 Series 6 Port SATA AHCI Controller)
2013:04:23 10:34:31:142:       Device: PCI\VEN_8086&DEV_3B22&CC_0106 (Intel(R) 5 Series/3400 Series SATA AHCI Controller)
2013:04:23 10:34:31:146:       Device: PCI\VEN_8086&DEV_1C02&CC_0106 (Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller)
2013:04:23 10:34:31:149:       Device: PCI\VEN_8086&DEV_1C03&CC_0106 (Intel(R) Mobile Express Chipset SATA AHCI Controller)
2013:04:23 10:34:31:152:       Device: PCI\VEN_8086&DEV_1D02&CC_0106 (Intel(R) C600 Series Chipset SATA AHCI Controller)
2013:04:23 10:34:31:156:       Device: PCI\VEN_8086&DEV_1E02&CC_0106 (Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller)
2013:04:23 10:34:31:159:       Device: PCI\VEN_8086&DEV_1E03&CC_0106 (Intel(R) 7 Series Chipset Family SATA AHCI Controller)
2013:04:23 10:34:31:162:       Device: PCI\VEN_8086&DEV_8C02&CC_0106 (Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller)
2013:04:23 10:34:31:166:       Device: PCI\VEN_8086&DEV_8C03&CC_0106 (Intel(R) 8 Series Chipset Family SATA AHCI Controller)
2013:04:23 10:34:31:169:       Device: PCI\VEN_8086&DEV_9C02&CC_0106 (Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller)
2013:04:23 10:34:31:172:       Device: PCI\VEN_8086&DEV_9C03&CC_0106 (Intel(R) 8 Series Chipset Family SATA AHCI Controller)
2013:04:23 10:34:31:175:     MUP OS bits: 0x36D50
2013:04:23 10:34:31:180:   Scanning x64\iaStorAC.inf (Name: RAID64, Version: 12.5.0.1066)
2013:04:23 10:34:31:183:     Section with the best match: INTEL.NTamd64.6.2
2013:04:23 10:34:31:187:       Device: PCI\VEN_8086&DEV_2822&CC_0104 (Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller)
2013:04:23 10:34:31:190:       Device: PCI\VEN_8086&DEV_282A&CC_0104 (Intel(R) Mobile Express Chipset SATA RAID Controller)
2013:04:23 10:34:31:193:     MUP OS bits: 0x36D50
2013:04:23 10:34:31:198: E Win32 exception occurred!!
2013:04:23 10:34:31:201:     Error code: 0x4E24 (20004)
2013:04:23 10:34:31:205:     Error text: ''
2013:04:23 10:34:31:208:     Extended error text: 'Error in device matching'
2013:04:23 10:34:31:211:     Debug info: 'Setup.cpp (156)'
2013:04:23 10:34:31:233:   Showing dialog: FINISH
So no luck here.
The zip contains what could seem the driver I need, but as I said Device Manager can't find a suitable/newer driver there automatically. Selecting those inf manually gives various devices and I'm unable to understand which one I could choose. This is the list:
  1. Intel(R) 5 Series 4 Port SATA AHCI Controller
  2. Intel(R) 5 Series 6 Port SATA AHCI Controller
  3. Intel(R) 5 Series/3400 Series SATA AHCI Controller
  4. Intel(R) 7 Series Chipset Family SATA AHCI Controller
  5. Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller
  6. Intel(R) 8 Series Chipset Family SATA AHCI Controller
  7. Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller
  8. Intel(R) C600 Series Chipset SATA AHCI Controller
  9. Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller
  10. Intel(R) Mobile Express Chipset SATA AHCI Controller
I don't really know. I found someone that seems to be lamenting the same problem here but he has a newer driver than mine, so I'll try to find it in the meantime. What I just know it's ICH9R on P35. It also sounds strange the zip contains only iaStorF.sys and iaStorA.sys , NOT iaStor.sys . I took the wrong driver?

Quote:
Originally Posted by jcgriff2 View Post
I would recommend removal of Kaspersky Internet Security for now - at least until BSOD epidemic is over - [...]
Reboot upon completion. Install Microsoft Security Essentials (MSE)
Ok. About MSE, I've read on MS forums in Win8 the included "Defender" substitutes it completely, so I just did nothing more than uninstalling (did that previously) and now using the remover and reboot.

I did all the rest.

In case we don't come to a solution, I could simply try detaching the sound card for some time and use the integrated (disabled in the BIOS) one to see if that is the culprit.

Thanks.
Regards,
Matteo.
cmatte is offline  
Old 04-23-2013, 02:56 AM   #5
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Quote:
Originally Posted by cmatte View Post
[iaStor.sys...]
I don't really know. I found someone that seems to be lamenting the same problem here but he has a newer driver than mine, so I'll try to find it in the meantime.
I found it out here and installed, it's now 10.8.0.1003 signed by MS 10/2011. Don't know if I can do more.
As that user says, the driver you linked and I downloaded should be supporting ICH9R/DO AHCI and RAID as per this page or this page...

Regards,
Matteo.
cmatte is offline  
Old 04-23-2013, 06:40 AM   #6
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Hi,
I tried the verifier against the mijxflit.sys driver.
It caused BSODs all the way!
System doesn't boot at all if I attach the BT adapter.
It boots without it and the verifier shows the driver isn't loaded.
I tried attaching the PS3 controller with the USB cable (MotionInJoy handles the cable too) and had a BSOD after removing/re-attaching it:
Code:
042313-16364-01.dmp	23/04/2013 15.17.53	DRIVER_VERIFIER_DETECTED_VIOLATION	0x000000c4	00000000`000000dd	fffff880`0aed01d0	fffff880`0aeb1000	fffffa80`0a8aca00	hidusb.sys	hidusb.sys+390a1d0					x64	ntoskrnl.exe+5a240					C:\Windows\Minidump\042313-16364-01.dmp	4	15	9200	117.736
In this situation the verifier shows the driver as loaded and the counters all always at zero.
Now for example the controller is attached and ready for playing, driver loaded, software on, verifier shows all zeros, but no BSODs so far.
The Nirsoft tool for BSODs shows different drivers causing the issue, don't know why, the BS screens I could read all showed the mijxflit.sys as the source of the problem for the BSODs at boot and for the BSOD while re-attaching the joystick to the USB port.
I'm attaching its report and the three mini dumps, if useful.

At this point, I think I'm having multiple problems causing these:
  • if/when the driver isn't loaded (ie nor the joystick was attached to USB port nor the BT adapter was there) I had most of my BSODs, so I think the MotionInJoy stuff couldn't make the issue in these situations, could it?
  • the MIJ driver itself is buggy. Maybe the collage of the newest xbox360 driver by MS could handle something better, since as you said it's a known BSOD source?


Thanks.
Best Regards,
Matteo.
Attached Files
File Type: zip MIJ BSODs.zip (86.1 KB, 64 views)
cmatte is offline  
Old 04-23-2013, 07:16 AM   #7
TSF Enthusiast
 
Join Date: Jul 2012
Location: Colorado
Posts: 3,036
OS: Windows 7 Home Premium x64

My System


We've seen a number of crashes with Windows 8 when BIOS versions are older. There have also been many reports of crashes with older BIOS versions when trying to run an SSD. Not sure if that is the case here, but it is possible your old hardware is not properly supported by Windows 8 or that the SSD is not compatible. Have you tried installing your previous Windows version to see if it provides stability to rule out software/OS as the cause. If you crash in your previous Windows, that would indicate a hardware issue or conflict, probably with the SSD.

Have you tried installing Windows 8 to a platter HDD to test?


SSD Troubleshooting:
The crashes you are receiving are common with SSDs when there are incompatible drivers, hardware, BIOS, or firmware issues. Proceed with SSD troubleshooting:
  • Make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

  • If this is a desktop system, try connecting the drive to a different hard disk controller connection, i.e. Marvell instead of Intel, ASMedia instead of Intel, Intel instead of ASMedia or Marvell, etc.

  • Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.
    1. Power off the system.
    2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
    3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
    4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
    5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
    6. Let the computer remain in the BIOS for 20 minutes.
    7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
    8. Leave the drive disconnected for 30 seconds to let all power drain from it.
    9. Replace only the drive power connection if it is a desktop, (fully reconnect the drive to the system if it is a laptop) and then do steps 4-8 again.
    10. Follow steps 1-3 again.
    11. Reconnect the drive fully to the system.
    12. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
    13. Start your computer normally and run Windows.
    The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

    While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.
If the above does not work, try replacing your SSD with a platter hard disk drive to see if the SSD is faulty or causing conflicts with your overall setup.



-----
writhziden is offline  
Old 04-24-2013, 03:31 AM   #8
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Thanks for your input writhziden.
Before going on, I'd like at first to try to make sure I have the latest drivers before troubleshooting SSD problems and then installing Win8 on an HDD, that is btw a great idea to exclude SSD problems.

So, speaking about drivers at first, I'm sure BIOS and SSD FW are latest versions, the same for video card and audio card, but there's some mess about Intel chipsets and I need your advice.
I have downloaded the infinst_autol.zip file from Intel dated 02/2013 for my chipset from Intel website. Its installer upgraded all the USB Intel drivers. So far, so good.

Now, considering the disk controller (SATA AHCI), as I was saying in my previous posts, I have a big doubt!
I previously managed to upgrade it to the latest known Intel driver I could find:
supplier Intel
version 10.8.0.1003
dated 17/10/2011
driver details:
iaStor.sys - version 10.8.0.1003 - by Intel (1994-2011) - signed by MS
In the chipset package I just downloaded, the one that has just upgraded USB drivers, there's also a driver for the disk controller! I tried manually installing it. It's:
supplier Intel
dated 25/02/2013
version 9.1.9.1003
driver details:
storahci.sys - version 6.2.9200.16548 (win8_gdr.130301-1803) - by MS - signed by MS
Which one should I choose in your opinion? I mean, should I care about date or about version/brand?
cmatte is offline  
Old 04-24-2013, 06:32 AM   #9
TSF Enthusiast
 
Join Date: Jul 2012
Location: Colorado
Posts: 3,036
OS: Windows 7 Home Premium x64

My System


I would suggest trying each, starting with the latest version from MS on 25/02/2013. Before installing either driver, make sure to create a restore point. Then see if the latest version provides stability, and if not, restore the system back to its current driver configuration and install the driver from 17/10/2011.
Create a restore point


-----
writhziden is offline  
Old 04-24-2013, 10:28 AM   #10
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Ok, I started using the 2013 driver with no issues so far and from now on I will do some testing of the machine in this as "clean" as possible status, to see if it is stable and if the BSODs stop. I've removed completely the MIJ driver, software, files left too.

About the driver, yesterday I asked Intel support why my chipset is in their "supported" list of the RST driver but is not really working with the latest. They just answered my inquiry saying 10.8.1003 is the latest and it's not intended to be supported anymore by newer drivers since it's discontinued as of now. So, let's just try the MS driver for some time.

Thank you both for your help till now.
I'll reply back after some days of testing for good or bad news about BSODs.

Regards,
Matteo.
cmatte is offline  
Old 04-25-2013, 03:27 AM   #11
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Hi,
there was not so much testing needed to have another BSOD, yesterday evening while working at a website (browsing and so on)
Code:
==================================================
Dump File         : 042513-14788-01.dmp
Crash Time        : 25/04/2013 01.18.17
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff880`048410b0
Parameter 3       : fffff880`0dc8f090
Parameter 4       : 00000000`00000000
Caused By Driver  : dxgmms1.sys
Caused By Address : dxgmms1.sys+1f0b0
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+5a240
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\042513-14788-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 9200
Dump File Size    : 136.464
==================================================
I thought about the fact I renewed also my graphic card 08/2012. That time I was still using Win7. I can't remember very well but it could be the BSODs randomly and occasionally happened since I installed the new graphic card, so, with Windows 7 too. I also remember I did much testing with Win7 + Win8 + Ubuntu in trial boot at that time and tried various other stuff before doing the clean install of Win8 in the new SSD, so I would have not given much weight to random BSODs because of the mess I was doing with OSes and so on

I did a simple research on the graphic card's BIOS to try and see if there are known problems:
113-217XTHE-O02 serial
015.017.000.000 version
and immediately found some links, forums and videos proving this is bugged and causing random BSODs
This post sums up a complete thread of research done by that guy and that community (but there are others too, in official brands' forums!). I am having the exact board said to be bugged. He got a new one by Sapphire (my brand too) by RMAing his one and got the problem solved.
It's a lot annoying but I think I could try. What's your opinion?
cmatte is offline  
Old 04-25-2013, 08:24 AM   #12
Moderator
- Microsoft Support
BSOD Kernel Dump Analyst
 
satrow's Avatar
 
Join Date: Feb 2012
Location: Wales U.K.
Posts: 5,695
OS: W7 SP1 Pro x64

My System


Quote:
Originally Posted by cmatte View Post
I did a simple research on the graphic card's BIOS to try and see if there are known problems:
113-217XTHE-O02 serial
015.017.000.000 version
and immediately found some links, forums and videos proving this is bugged and causing random BSODs
This post sums up a complete thread of research done by that guy and that community (but there are others too, in official brands' forums!). I am having the exact board said to be bugged. He got a new one by Sapphire (my brand too) by RMAing his one and got the problem solved.
It's a lot annoying but I think I could try. What's your opinion?
Good work, you may well have cracked it!

I spent an hour on that thread in my last online session (I have a HD7850 with the 'flickering' problem) but I was too tired to take it all in.
__________________
satrow is online now  
Old 04-26-2013, 04:29 AM   #13
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Glad I was able to give some help :)

I hope you're wrong about cracking it. I checked it out completely and it seems in perfect conditions.

Anyway I've just removed the HD7870 and I've put back in place the old HD3870. There's a legacy AMD driver for it and Win8 x64 fortunately.
In the meantime I'll be able to see if I have BSODs this way, perhaps I can see if the graphic card was really the root cause. I also contacted my retailer and they are going to activate an RMA request.

I hope in the meantime not to have BSODs, otherwise the RMA request would probably be useless!

p.s. I also found a newer Marvell controller driver and installed it.
cmatte is offline  
Old 04-26-2013, 05:10 AM   #14
Moderator
- Microsoft Support
BSOD Kernel Dump Analyst
 
satrow's Avatar
 
Join Date: Feb 2012
Location: Wales U.K.
Posts: 5,695
OS: W7 SP1 Pro x64

My System


Cracked it = solved it, bad firmware/BIOS in the gfx card.

(I think my flickering problems are reduced too, new beta drivers.)

The Marvell drivers are now version 12.10.10.3, correct?

I'm quietly confident, good luck and keep us informed.
__________________
satrow is online now  
Old 04-26-2013, 06:54 AM   #15
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Quote:
Originally Posted by satrow View Post
Cracked it = solved it, bad firmware/BIOS in the gfx card.
Oops...I admit I had the doubt that was the meaning but I wasn't able to find a good translator that confirmed it so please excuse my poor english

Quote:
Originally Posted by satrow View Post
(I think my flickering problems are reduced too, new beta drivers.)
Aren't you going to RMA it? I've read Sapphire does recognize these problems as issues and gives you another card!
Quote:
Originally Posted by satrow View Post
The Marvell drivers are now version 12.10.10.3, correct?
Not really. It's a Marvell 88SE6102 PATA controller, quite old, but I'm using an old Seagate 320GB HDD that still works good as a base for my data and the 2TB newer SATA drive is the destination of the (great, btw) FileHistory backup system of Win8. I have checked this old ide drive with the Seagate ISO found on the sticky thread after my first post. The full test found no problems, it's alright. The same for the 2TB drive (Seagate too).
The controller is
PCI\VEN_11AB&DEV_6101&SUBSYS_82E01043&REV_B2
and last version I could find of its driver is
Dated 24/05/2012
Version 1.2.0.8400
Details
%SystemRoot%\System32\Drivers\mv61xx.sys version 1.2.0.8400 build by WinDDK signed by MS Windows Hardware Compatibility
%SystemRoot%\System32\Drivers\mv61xxmm.sys version 1.0.0.1200 build by WinDDK signed by MS Windows Hardware Compatibility
%SystemRoot%\System32\mvcoinst.dll version 1.0.0.4 signed by MS Windows Hardware Compatibility [Copyright reports 2009 as a date]
The previous one was
Dated 11/05/2009
Version 1.2.0.69
Details
%SystemRoot%\System32\Drivers\mv61xx.sys version 1.2.0.69 build by WinDDK not signed
%SystemRoot%\System32\Drivers\mv61xxmm.sys version 1.0.0.1200 build by WinDDK signed by MS Windows Hardware Compatibility
%SystemRoot%\System32\mvcoinst.dll version 1.0.0.3 not signed [Copyright reports 2008 as a date]
If you can find something newer I will give it a try
Quote:
Originally Posted by satrow View Post
I'm quietly confident, good luck and keep us informed.
I'm with crossed fingers right now! Will try to use the pc to see if I don't have BSODs without the probable root cause. Be sure I will be back, and thank you all for your help guys, much appreciated
cmatte is offline  
Old 04-26-2013, 07:51 AM   #16
Moderator
- Microsoft Support
BSOD Kernel Dump Analyst
 
satrow's Avatar
 
Join Date: Feb 2012
Location: Wales U.K.
Posts: 5,695
OS: W7 SP1 Pro x64

My System


Your English is fine; it can be an imprecise language - and when slang terms are added into the mix - mistakes are easy to make.

No RMA yet, it looks like my problems are 90% 'fixed' - so far. Still a little buggy when scrolling in Firefox but there are known issues that may be fixed there.

Ah, it's PATA, I hadn't noticed that. The new compatible driver should work fine; if it was for a Wireless USB device, a driver from that date I would be much less confident about.

Fingers are crossed here too
__________________
satrow is online now  
Old 04-27-2013, 03:32 AM   #17
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Let's see if the fingers get free and easily usable for the keyboard some time soon
cmatte is offline  
Old 05-13-2013, 01:29 AM   #18
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Hi guys!
After many days of testing, I can confirm I didn't have a single BSOD after having removed the video card and installed an older one.
That was for sure the root cause.

I am awaiting a new/repleacement one, the RMA procedure is still going on.

Thank you all for the help.

Regards
cmatte is offline  
Old 05-13-2013, 02:14 AM   #19
Moderator
- Microsoft Support
BSOD Kernel Dump Analyst
 
satrow's Avatar
 
Join Date: Feb 2012
Location: Wales U.K.
Posts: 5,695
OS: W7 SP1 Pro x64

My System


Great news, I hope the replacement card arrives soon (with a good firmware version installed) ;)
__________________
satrow is online now  
Old 07-18-2013, 06:58 AM   #20
Registered Member
 
Join Date: Apr 2013
Location: Italy
Posts: 13
OS: Windows8 x64

My System


Hi, I wanted to thank you all for the help guys, and inform you that my vendor (slowly) decided to give me a full refund of the card because they had not a replacement one in stock. I was not refunded of any cost I had to pay for shipping it back in -another- country, the payment-mode price and the shipping costs I paid for it when buying...around 40€. That's unfair and illegal but I won't go in a court for this.
BSODs are mostly forgotten. For our curiosity, instead of one in a day to many in a days...I can see 4 bsods since the 3rd of March...I couldn't even remember about these :)
I will probably buy some new card when I can, it's not a priority at all.

Regards and have a good summer! Here I got to study study study for University, actually :P
cmatte is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD special pool detected memory corruption
Im getting this BSOD lately when im playing games, browsing on the internet and generaly by using the pc. This is the report i have found in the event viewer: - <Event xmlns="https://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-Kernel-Power"...
Klavon BSOD, App Crashes And Hangs 13 04-04-2013 10:25 AM
BSOD usb bugcode driver
Hi everybody, since now a few weeks I have a BSOD problem that occurs up to 4 times a day, rebooting my computer and it's seriously starting to piss me off... I followed the instructions on this page of the forum so if anybody could help me with this proble it would be great, as I need my...
hub151 BSOD, App Crashes And Hangs 3 02-06-2013 05:34 AM
Win8 Multiple tiles, same app w/ different args
I have a Chrome tile on my Win8 Start that opens Chrome on desktop and goes directly to Chrome default page. I also want, as I have in XP and 7, a Start link that goes via Chrome to my Google Calendar. I actually already have this on my Win8 Desktop -- it's just a shortcut to Chrome with an...
XXP Windows 8, 8.1 Support 0 11-21-2012 08:28 AM
Multiple random BSODs, whits end
I built a custom pc in august, it started getting BSODs in december. I reinstalled windows, didn't help. bluescreens started getting worse, reinstalled windows again, helped for a week or so but they started again. There are no dump files from BSODs, but I have been taking pictures of the error...
whitenova BSOD, App Crashes And Hangs 12 02-25-2011 02:00 PM
random BSOD's with win32k.sys and SYSTEM_SERVICE_EXCPETION, win7 x64 dumps included
Hello, I have been having BSODs on my PC forever, and I decided to get to the bottom of it. It seems to be totally random (happens even when the PC is idle, when I am watching youtube or a movie, or even playing a game, even if it isnt tasking at all). Sometimes it cant even boot to Windows, but...
valouris BSOD, App Crashes And Hangs 29 02-14-2011 02:42 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 03:36 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts