Short story for now, decided to downsize from eATX to mATX and even since has been a headache.
Will provide any information needed but atm I am posting from my laptop as the desktop just blue screened again while I was writing this post the first time.
Hardware;
Random freezes requiring manual restart started happening shortly after the initial Windows installation. They would happen while playing Diablo 3, browsing with Firefox or while I was away from the computer. Event views produces a " kernel-power " error;
Shortly after I started experiencing those I got my first BSOD. And the logs pointed to my USB SoundCards drivers, so I uninstalled them and have since gotten new ones.
Sorry if this isn't the correct format for BSOD's but as I said, I can get the proper stuff when instructed as right now I'm on my laptop, but these are from WhoCrashed that I sent to a friend.
Both of the drivers on the bottom have been uninstalled / deleted from the system using the "autoruns" tool I found in another thread here while doing research on this. But as of now I am pretty stumped.
P.S. The logs above seem to be missing the newer BSOD occurrences... I guess it didn't dump them for some reason. What I have written down for those is 0x0000001e.
Will provide any information needed but atm I am posting from my laptop as the desktop just blue screened again while I was writing this post the first time.
Hardware;
Code:
Processor - Intel Core i7 2600k
Motherboard - ASRock Z77 Extreme4-M
Memory - G.Skill RipJaws X 16GB ( 4x4GB ) DDR3 1600Mhz
HDD - Seagate Barracuda
Power Supply - Corsair HX750
Code:
[B]-[/B] [B]System[/B]
[B]-[/B] [B]Provider[/B]
[ [B]Name[/B]] Microsoft-Windows-Kernel-Power
[ [B]Guid[/B]] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
[B]EventID[/B] 41
[B]Version[/B] 2
[B]Level[/B] 1
[B]Task[/B] 63
[B]Opcode[/B] 0
[B]Keywords[/B] 0x8000000000000002
[B]-[/B] [B]TimeCreated[/B]
[ [B]SystemTime[/B]] 2012-11-26T00:14:36.548015900Z
[B]EventRecordID[/B] 9345
[B]Correlation[/B]
[B]-[/B] [B]Execution[/B]
[ [B]ProcessID[/B]] 4
[ [B]ThreadID[/B]] 8
[B]Channel[/B] System
[B]Computer[/B] Musketeer
[B]-[/B] [B]Security[/B]
[ [B]UserID[/B]] S-1-5-18
[B]-[/B] [B]EventData[/B]
[B]BugcheckCode[/B] 0
[B]BugcheckParameter1[/B] 0x0
[B]BugcheckParameter2[/B] 0x0
[B]BugcheckParameter3[/B] 0x0
[B]BugcheckParameter4[/B] 0x0
[B]SleepInProgress[/B] false
[B]PowerButtonTimestamp[/B] 0
Sorry if this isn't the correct format for BSOD's but as I said, I can get the proper stuff when instructed as right now I'm on my laptop, but these are from WhoCrashed that I sent to a friend.
Code:
[FONT=Segoe UI, Arial][SIZE=4][B] Crash Dump Analysis[/B] [/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000]Crash dump directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000]Crash dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][B]On Sat 11/24/2012 7:12:11 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\112412-20997-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7EFC0)
Bugcheck code: 0xA (0x3C297D, 0x2, 0x1, 0xFFFFF8000329B24E)
Error: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][B]On Sat 11/24/2012 7:12:11 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=mbfilt64.sys"]mbfilt64.sys[/URL][/COLOR][/SIZE][/FONT] (MBfilt64+0x1817)
Bugcheck code: 0xA (0x3C297D, 0x2, 0x1, 0xFFFFF8000329B24E)
Error: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\drivers\mbfilt64.sys
company: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Creative Technology Ltd."]Creative Technology Ltd.[/URL][/COLOR][/SIZE][/FONT]
description: Creative Audio Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mbfilt64.sys (Creative Audio Driver, Creative Technology Ltd.).
Google query: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=mbfilt64.sys+Creative Technology Ltd.+IRQL_NOT_LESS_OR_EQUAL"]Creative Technology Ltd. IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][B]On Sat 11/24/2012 7:12:08 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\112412-21122-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Unknown"]Unknown[/URL][/COLOR][/SIZE][/FONT] ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][B]On Sat 11/24/2012 7:10:51 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\112412-20966-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Unknown"]Unknown[/URL][/COLOR][/SIZE][/FONT] ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][B]On Sat 11/24/2012 6:50:57 AM GMT your computer crashed[/B]
crash dump file: C:\Windows\Minidump\112412-24320-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ksaud.sys"]ksaud.sys[/URL][/COLOR][/SIZE][/FONT] (0xFFFFF880068C7503)
Bugcheck code: 0xD5 (0xFFFFF98004D4EC00, 0x0, 0xFFFFF880068C7503, 0x0)
Error: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL"]DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL[/URL][/COLOR][/SIZE][/FONT]
file path: C:\Windows\system32\drivers\ksaud.sys
product: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Sound Blaster USB Audio"]Sound Blaster USB Audio[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Creative Technology Ltd."]Creative Technology Ltd.[/URL][/COLOR][/SIZE][/FONT]
description: WDM USB Audio Driver
Bug check description: This indicates that a driver has referenced memory which was earlier freed.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ksaud.sys (WDM USB Audio Driver, Creative Technology Ltd.).
Google query: [FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ksaud.sys+Creative Technology Ltd.+DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL"]Creative Technology Ltd. DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL[/URL][/COLOR][/SIZE][/FONT]
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=4][B] Conclusion[/B] [/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000]5 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ksaud.sys+Creative Technology Ltd.+Sound Blaster USB Audio"]ksaud.sys (WDM USB Audio Driver, Creative Technology Ltd.)[/URL][/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=mbfilt64.sys+Creative Technology Ltd."]mbfilt64.sys (Creative Audio Driver, Creative Technology Ltd.)[/URL][/COLOR][/SIZE][/FONT]
[/COLOR][/SIZE][/FONT]
Both of the drivers on the bottom have been uninstalled / deleted from the system using the "autoruns" tool I found in another thread here while doing research on this. But as of now I am pretty stumped.
P.S. The logs above seem to be missing the newer BSOD occurrences... I guess it didn't dump them for some reason. What I have written down for those is 0x0000001e.
My Computer
At a glance
Windows 7 Ultimate x64Intel Core i7 2600kG.Skill RipJaws X ( 4x4GB ) DDR3 1600MhzNvidia GTX460 SE ( 1GB )
- OS
- Windows 7 Ultimate x64
- CPU
- Intel Core i7 2600k
- Motherboard
- ASRock Z77 Extreme4-M
- Memory
- G.Skill RipJaws X ( 4x4GB ) DDR3 1600Mhz
- Graphics Card(s)
- Nvidia GTX460 SE ( 1GB )
- Monitor(s) Displays
- Acer G235H
- Hard Drives
- Seagate Barracuda 500GB
- PSU
- Corsair HX750
- Case
- Silverstone PS07
- Cooling
- Corsair H80
rb: