New
#1
bsod on new system included reports
hi, for the past month i have been having crashes and i thought due to it being a new build it may be due to needing windows updates. it is still happening and i thought i may have fixed it yesterday by using a previous nvidia graphics driver as i managed to game for over 2 hours without a bsod but today within 20 mins while downloading i got a crash. i have included the zip file with system info as requested by site and some whocrashed reports if anyone can deciver this and aid me to a fix i would be very happy. thanks.
i have took ram out and put back in. deleted corsair link software and avast. tried several nvidia gpu drivers and used driver sweeper to remove old. i have re installed windows but i cant figure this out.
windows 7 home premium 64bit
nvidia gtx660 ftw 2gb
amd fx9590 (not over clocked)
asus m5a99fx 2.0
corsair h100i
1x scan disck ssd for windows
2x hdd for games
windows security center
novatech 750 psu
novatech 16gb ram
Attachment 308026
System Information (local)
</B>
computer name: PETE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: BB-895908G, NOVATECH LTD, ASUSTeK COMPUTER INC., M5A99FX PRO R2.0
CPU: AuthenticAMD AMD FX(tm)-9590 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17075523584 total
VM: 2147352576, free: 1936429056
Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 2/25/2014 3:12:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022514-13119-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 2/25/2014 3:12:43 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Mon 2/24/2014 2:12:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-12885-01.dmp
This was probably caused by the following module: msfs.sys (Msfs+0x49F4)
Bugcheck code: 0xFC (0xFFFFF880010E19F4, 0x800000040047D121, 0xFFFFF8800AC92530, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\msfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Mailslot driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 2/24/2014 12:23:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-12901-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031FC147, 0xFFFFF88003832C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
Conclusion
</B>
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Last edited by morgon80; 25 Feb 2014 at 11:16. Reason: including system details