New
#1
Random BSOD's and Freezing on new build.
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;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
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.Code:- System - Provider [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4} EventID 41 Version 2 Level 1 Task 63 Opcode 0 Keywords 0x8000000000000002 - TimeCreated [ SystemTime] 2012-11-26T00:14:36.548015900Z EventRecordID 9345 Correlation - Execution [ ProcessID] 4 [ ThreadID] 8 Channel System Computer Musketeer - Security [ UserID] S-1-5-18 - EventData BugcheckCode 0 BugcheckParameter1 0x0 BugcheckParameter2 0x0 BugcheckParameter3 0x0 BugcheckParameter4 0x0 SleepInProgress false PowerButtonTimestamp 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.
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.Code:Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sat 11/24/2012 7:12:11 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112412-20997-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x3C297D, 0x2, 0x1, 0xFFFFF8000329B24E) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation 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. On Sat 11/24/2012 7:12:11 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: mbfilt64.sys (MBfilt64+0x1817) Bugcheck code: 0xA (0x3C297D, 0x2, 0x1, 0xFFFFF8000329B24E) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\mbfilt64.sys company: Creative Technology Ltd. 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: Creative Technology Ltd. IRQL_NOT_LESS_OR_EQUAL On Sat 11/24/2012 7:12:08 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112412-21122-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Sat 11/24/2012 7:10:51 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112412-20966-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Sat 11/24/2012 6:50:57 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112412-24320-01.dmp This was probably caused by the following module: ksaud.sys (0xFFFFF880068C7503) Bugcheck code: 0xD5 (0xFFFFF98004D4EC00, 0x0, 0xFFFFF880068C7503, 0x0) Error: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL file path: C:\Windows\system32\drivers\ksaud.sys product: Sound Blaster USB Audio company: Creative Technology Ltd. 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: Creative Technology Ltd. DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Conclusion 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: ksaud.sys (WDM USB Audio Driver, Creative Technology Ltd.) mbfilt64.sys (Creative Audio Driver, Creative Technology Ltd.)
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.