Alex Spicer
New Member
- Joined
- Jun 15, 2013
- Messages
- 10
- Thread Author
- #1
I have been super upset ![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
I just built this pc and am getting BSOD anytime I have a 3d APP up + any VOIP (raidcall/skype)
I am attaching what the tool you provided captured (I dont see the dump):
But I can tell you that from previous BSOD (before reinstall) I saw NDIS.sys caused many of them. accomponied with ntsokernel.sys not handling it.
I tested my memory and it passed memtest. I am at a loss. Please help![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
Link Removed
![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
I just built this pc and am getting BSOD anytime I have a 3d APP up + any VOIP (raidcall/skype)
I am attaching what the tool you provided captured (I dont see the dump):
But I can tell you that from previous BSOD (before reinstall) I saw NDIS.sys caused many of them. accomponied with ntsokernel.sys not handling it.
I tested my memory and it passed memtest. I am at a loss. Please help
![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
Link Removed
Alex Spicer
New Member
- Joined
- Jun 15, 2013
- Messages
- 10
- Thread Author
- #2
- Joined
- Mar 22, 2010
- Messages
- 3,052
Please understand that I come here once a day. I get to as many posts as I can before I have to be at work.
Only 111 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
These devices have problems in Device Manager:
Second one - is this deliberately disabled? If so, why?
Third one, install the USB 3.0 drivers for your motherboard
If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Link Removed
Just in case this is a hardware problem, please run these free hardware diagnostics as you have time: Link Removed. Let us know the results and we can move on from there. As I suspect memory, run MemTest; Prime95; and the video memory test first.
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Only 111 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.
These devices have problems in Device Manager:
First one, install the chipset drivers for the system.SM Bus Controller PCI\VEN_8086&DEV_8C22&SUBSYS_85341043&REV_04\3&11583659&0&FB The drivers for this device are not installed.
Ethernet Controller PCI\VEN_8086&DEV_153B&SUBSYS_859F1043&REV_04\3&11583659&0&C8 This device is disabled.
Universal Serial Bus (USB) Controller PCI\VEN_8086&DEV_8C31&SUBSYS_85341043&REV_04\3&11583659&0&A0 The drivers for this device are not installed.
Second one - is this deliberately disabled? If so, why?
Third one, install the USB 3.0 drivers for your motherboard
If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Link Removed
Just in case this is a hardware problem, please run these free hardware diagnostics as you have time: Link Removed. Let us know the results and we can move on from there. As I suspect memory, run MemTest; Prime95; and the video memory test first.
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Sun Jun 16 02:34:24.645 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061513-5179-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:57.457[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 01:44:12.836 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061513-4165-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:25:26.648[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 15 23:43:39.138 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061513-12199-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:06:06.950[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck [B]A, {1de002f44598, d, 0, fffff8000309b183}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 00001de002f44598, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000000, 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: fffff8000309b183, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: [B][COLOR=RED]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_VRF_nt!KiPageFault+260[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Sun Jun 16 02:34:24.645 2013 (UTC - 4:00)**************************
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
CAHS164.sys Thu Jun 16 03:10:06 2011 (4DF9AC4E)
AsIO.sys Wed Aug 22 05:54:47 2012 (5034AC67)
Rt64win7.sys Thu Oct 25 05:20:09 2012 (50890449)
HECIx64.sys Mon Dec 17 14:32:21 2012 (50CF7345)
nvhda64v.sys Mon Feb 25 00:27:35 2013 (512AF647)
nvlddmkm.sys Sun May 12 15:09:45 2013 (518FE8F9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 01:44:12.836 2013 (UTC - 4:00)**************************
Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Alex Spicer
New Member
- Joined
- Jun 15, 2013
- Messages
- 10
- Thread Author
- #4
SO I GOT UPSET AND RAN DRIVER VERIFIER: (it seems the culprit is IOmap64.sys (ASUS) )
Here is my many dumps It BSOD within 2 min of being in Windows:
Link Removed
I dont see how to fix this I have already installed everything for the z87-PLUS from the Asus site.
2nd UPDATE: Another one but all this dmp showed was ntoskrnl.exe causing it
Here is the dump:
Link Removed
I am at a loss..... should I just buy a new mobo ???? I use z87-PLUS from ASUS
UPDATE
: Below I described what I did but the moment I open dota 2 or cs go (3d applications) I receive a blue screen(sometimes i can p[lay for like 1 hour):
HERE Is the dump+etc:
Link Removed
Wow thanks a ton for the writeup. I did all the steps you mentioned but from ASUSMotherboards/Z87PLUS/ the chipset did not auto resolve the SM Bus Controller. I even pointed it to the unzipped chipset folder and it did not auto resolve.
The SSD is the Samsung (new ones) and I checked the firmware and tested the drive.
I had disabled the onboard NIC because I have an external NIC card. Is that bad practice?
Also below you showed 3rd party drivers such as AsIO, HECIx64.sys ect... Should I update or remove the ones listed (I updated but some of those I feel can be deleted).
Any further help that you provide would be much appreciated. Crossing my fingers for no more BSOD![Big Grin :D :D](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f600.png)
Here is my many dumps It BSOD within 2 min of being in Windows:
Link Removed
I dont see how to fix this I have already installed everything for the z87-PLUS from the Asus site.
2nd UPDATE: Another one but all this dmp showed was ntoskrnl.exe causing it
![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
Here is the dump:
Link Removed
I am at a loss..... should I just buy a new mobo ???? I use z87-PLUS from ASUS
UPDATE
![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
HERE Is the dump+etc:
Link Removed
Wow thanks a ton for the writeup. I did all the steps you mentioned but from ASUSMotherboards/Z87PLUS/ the chipset did not auto resolve the SM Bus Controller. I even pointed it to the unzipped chipset folder and it did not auto resolve.
The SSD is the Samsung (new ones) and I checked the firmware and tested the drive.
I had disabled the onboard NIC because I have an external NIC card. Is that bad practice?
Also below you showed 3rd party drivers such as AsIO, HECIx64.sys ect... Should I update or remove the ones listed (I updated but some of those I feel can be deleted).
Any further help that you provide would be much appreciated. Crossing my fingers for no more BSOD
![Big Grin :D :D](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f600.png)
- Joined
- Mar 22, 2010
- Messages
- 3,052
Alex Spicer
New Member
- Joined
- Jun 15, 2013
- Messages
- 10
- Thread Author
- #6
At this point it's just best to wait and see if you have any further BSOD's.
It seems that you've removed the IOmap64.sys, so that "should" fix it.
If the system BSOD's again, please zip up and upload the contents of the C:\Windows\Minidump folder with your next post.
I actually never removed IOmap64.sys. Did it disappear? I have had so many blue screens since yesterday
![Frown :( :(](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f641.png)
When I stressed all the Microsoft Drivers is when I saw IOmap64.sys. I will keep stressing the drivers and post again.
Here is the current dump: (8:28pm PST)
Link Removed
- Joined
- Mar 22, 2010
- Messages
- 3,052
The last 2 memory dumps are not Driver Verifier enabled memory dumps. If you're still running Driver Verifier, please turn it off. To do this, open up verifier.exe and select "Delete existing settings", then reboot the system for the changes to take effect (?affect?).
Please remove your Microsoft Lifecam program and physically remove the camera from the system.
If this does not stop the BSOD's, then please start with these free hardware diagnostics: Link Removed
Start with the MemTest, Prime95, and video tests (as I suspect a memory problem) - but do all of the tests as they all can relate to the memory (yes, including the hard drive test!).
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Please remove your Microsoft Lifecam program and physically remove the camera from the system.
If this does not stop the BSOD's, then please start with these free hardware diagnostics: Link Removed
Start with the MemTest, Prime95, and video tests (as I suspect a memory problem) - but do all of the tests as they all can relate to the memory (yes, including the hard drive test!).
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Mon Jun 17 23:23:02.374 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061713-7347-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 3:05:55.059[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 17 03:19:50.043 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061713-6146-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:42:44.855[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3506[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 17 01:47:58.607 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-14320-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:02:51.419[/B]
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably caused by :[B]IOMap64.sys ( IOMap64+1734 )[/B]
BugCheck [B]C9, {226, fffff88007272734, fffff980676aeee0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
or someone forgot to return STATUS_PENDING.
Arg2: fffff88007272734, The address in the driver's code where the error was detected.
Arg3: fffff980676aeee0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR: 0xc9_226
PROCESS_NAME: aprp.exe
FAILURE_BUCKET_ID: [B]X64_0xc9_226_VRFK_IOMap64+1734[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 17 01:44:33.623 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-14367-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:02:52.325[/B]
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably caused by :[B]IOMap64.sys ( IOMap64+1734 )[/B]
BugCheck [B]C9, {226, fffff880095d3734, fffff98062bf8ee0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
or someone forgot to return STATUS_PENDING.
Arg2: fffff880095d3734, The address in the driver's code where the error was detected.
Arg3: fffff98062bf8ee0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR: 0xc9_226
PROCESS_NAME: aprp.exe
FAILURE_BUCKET_ID: [B]X64_0xc9_226_VRFK_IOMap64+1734[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 17 01:41:15.692 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-14944-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:02:53.504[/B]
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably caused by :[B]IOMap64.sys ( IOMap64+1734 )[/B]
BugCheck [B]C9, {226, fffff880077cd734, fffff9801d77cee0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
or someone forgot to return STATUS_PENDING.
Arg2: fffff880077cd734, The address in the driver's code where the error was detected.
Arg3: fffff9801d77cee0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR: 0xc9_226
PROCESS_NAME: aprp.exe
FAILURE_BUCKET_ID: [B]X64_0xc9_226_VRFK_IOMap64+1734[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 17 01:37:57.013 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-15912-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:02:51.825[/B]
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably caused by :[B]IOMap64.sys ( IOMap64+1734 )[/B]
BugCheck [B]C9, {226, fffff88008d34734, fffff9800a410ee0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
or someone forgot to return STATUS_PENDING.
Arg2: fffff88008d34734, The address in the driver's code where the error was detected.
Arg3: fffff9800a410ee0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR: 0xc9_226
PROCESS_NAME: aprp.exe
FAILURE_BUCKET_ID: [B]X64_0xc9_226_VRFK_IOMap64+1734[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 17 01:34:38.769 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-14835-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:02:52.581[/B]
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably caused by :[B]IOMap64.sys ( IOMap64+1734 )[/B]
BugCheck [B]C9, {226, fffff8800b96f734, fffff98084444ee0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
or someone forgot to return STATUS_PENDING.
Arg2: fffff8800b96f734, The address in the driver's code where the error was detected.
Arg3: fffff98084444ee0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR: 0xc9_226
PROCESS_NAME: aprp.exe
FAILURE_BUCKET_ID: [B]X64_0xc9_226_VRFK_IOMap64+1734[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 23:49:16.171 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-6364-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:10:04.967[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 23:38:51.240 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-7503-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:03:39.926[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 21:34:46.449 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-7269-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 3:07:30.246[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 18:26:56.218 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-6084-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:11:05.015[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 05:31:23.203 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061613-6021-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:40:36.000[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 0801
BIOS Release Date 04/19/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Mon Jun 17 23:23:02.374 2013 (UTC - 4:00)**************************
[COLOR=RED][B]nx6000.sys Fri Jun 26 13:13:21 2009 (4A4501B1)[/B][/COLOR]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys Mon Aug 2 22:47:59 2010 (4C57835F)
CAHS164.sys Thu Jun 16 03:10:06 2011 (4DF9AC4E)
AsIO.sys Wed Aug 22 05:54:47 2012 (5034AC67)
Rt64win7.sys Thu Oct 25 05:20:09 2012 (50890449)
MpFilter.sys Wed Oct 31 18:43:06 2012 (5091A97A)
HECIx64.sys Mon Dec 17 14:32:21 2012 (50CF7345)
asahci64.sys Wed Jan 9 21:52:36 2013 (50EE2CF4)
nvhda64v.sys Mon Feb 25 00:27:35 2013 (512AF647)
iusb3hub.sys Fri Mar 29 08:36:15 2013 (51558ABF)
iusb3xhc.sys Fri Mar 29 08:36:19 2013 (51558AC3)
iusb3hcs.sys Fri Mar 29 08:37:59 2013 (51558B27)
nvlddmkm.sys Sun May 12 15:09:45 2013 (518FE8F9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 17 01:47:58.607 2013 (UTC - 4:00)**************************
IOMap64.sys Thu Feb 4 20:55:34 2010 (4B6B7A96)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jun 16 05:31:23.203 2013 (UTC - 4:00)**************************
cpudrv64.sys Tue Aug 11 12:39:13 2009 (4A819EB1)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Alex Spicer
New Member
- Joined
- Jun 15, 2013
- Messages
- 10
- Thread Author
- #8
- Joined
- Mar 22, 2010
- Messages
- 3,052
Sometimes it takes a while to figure out what the cause is. I will continue to offer suggestions until I run out of ideas.
Out of 10 memory dumps there were 4 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).
You can get a head start on the hardware diagnostics if you'd like - they are located here: Link Removed
IMO you've done everything necessary to rule out 3rd party drivers as the cause. That leaves either a hardware problem or a Windows problem.
Hardware problems are more likely, but testing will take longer. Windows problems are rarer - but all it takes is doing a "clean" install of Windows to rule them out.
Hardware troubleshooting steps: Link Removed
If nothing is found with the diagnostics, then try: Link Removed
Windows "clean" install: Link Removed
It's your call as to which one to try first.
Good luck!
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Out of 10 memory dumps there were 4 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).
You can get a head start on the hardware diagnostics if you'd like - they are located here: Link Removed
IMO you've done everything necessary to rule out 3rd party drivers as the cause. That leaves either a hardware problem or a Windows problem.
Hardware problems are more likely, but testing will take longer. Windows problems are rarer - but all it takes is doing a "clean" install of Windows to rule them out.
Hardware troubleshooting steps: Link Removed
If nothing is found with the diagnostics, then try: Link Removed
Windows "clean" install: Link Removed
It's your call as to which one to try first.
Good luck!
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Tue Jun 25 02:18:59.109 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-5569-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:09:03.905[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jun 25 01:09:33.167 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-5631-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 4:41:44.853[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+4a )[/B]
BugCheck [B]A, {ffffffff5c2ef27d, 2, 1, fffff80002a9266a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: ffffffff5c2ef27d, 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: fffff80002a9266a, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiProcessExpiredTimerList+4a[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 24 07:38:28.437 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-6583-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:04:30.234[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck [B]A, {140002f44598, d, 0, fffff80002a9e183}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000140002f44598, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000000, 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: fffff80002a9e183, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiPageFault+260[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 24 07:33:42.380 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-6520-02.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 3:45:08.176[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 24 03:48:19.594 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062413-6520-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:12:15.391[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 24 01:35:45.838 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062313-7035-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 9:51:53.634[/B]
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by :[B]cdd.dll ( cdd+5854 )[/B]
BugCheck [B]FC, {fffff88009e8d990, 8000000084768963, fffff88009e8d410, 2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffff88009e8d990, Virtual address for the attempted execute.
Arg2: 8000000084768963, PTE contents.
Arg3: fffff88009e8d410, (reserved)
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR: 0xFC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: csrss.exe
FAILURE_BUCKET_ID: [B]X64_0xFC_cdd+5854[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 21 21:15:35.203 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062113-7176-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:09:17.999[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 21 21:05:57.530 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062113-6630-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:17:09.327[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!PoIdle+1f5 )[/B]
BugCheck [B]50, {fffffca80d4894f0, 1, fffff80002a863c5, 7}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffffca80d4894f0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a863c5, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
BUGCHECK_STR: 0x50
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x50_nt!PoIdle+1f5[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 21 19:48:30.068 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062113-6536-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:31:12.865[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KeGetCurrentProcessorNumberEx+19 )[/B]
BugCheck [B]A, {5, 2, 1, fffff80002a829f9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000005, 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: fffff80002a829f9, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KeGetCurrentProcessorNumberEx+19[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3497[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 21 04:28:58.626 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062113-6926-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 9:15:44.422[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_nt!KiKernelCalloutExceptionHandler+e[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3498[/B]
BIOS Version 1007
BIOS Release Date 05/17/2013
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Tue Jun 25 02:18:59.109 2013 (UTC - 4:00)**************************
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys Mon Aug 2 22:47:59 2010 (4C57835F)
CAHS164.sys Thu Jun 16 03:10:06 2011 (4DF9AC4E)
AsIO.sys Wed Aug 22 05:54:47 2012 (5034AC67)
Rt64win7.sys Thu Oct 25 05:20:09 2012 (50890449)
MpFilter.sys Wed Oct 31 18:43:06 2012 (5091A97A)
HECIx64.sys Mon Dec 17 14:32:21 2012 (50CF7345)
asahci64.sys Wed Jan 9 21:52:36 2013 (50EE2CF4)
nvhda64v.sys Mon Feb 25 00:27:35 2013 (512AF647)
iusb3hub.sys Fri Mar 29 08:36:15 2013 (51558ABF)
iusb3xhc.sys Fri Mar 29 08:36:19 2013 (51558AC3)
iusb3hcs.sys Fri Mar 29 08:37:59 2013 (51558B27)
nvlddmkm.sys Sun May 12 15:09:45 2013 (518FE8F9)
rzendpt.sys Thu May 16 23:17:28 2013 (5195A148)
rzudd.sys Thu May 16 23:17:30 2013 (5195A14A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jun 24 01:35:45.838 2013 (UTC - 4:00)**************************
nx6000.sys Thu Dec 2 17:23:39 2010 (4CF81C6B)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Similar threads
- Replies
- 2
- Views
- 4K
- Replies
- 1
- Views
- 3K
- Replies
- 0
- Views
- 1K
- Replies
- 5
- Views
- 4K
- Replies
- 17
- Views
- 4K