szymekk3

New Member
Joined
Mar 21, 2013
Messages
30
Hello!
I'm new to this forum as I have experienced multiple BSODs over the past month, I would like to hear some advice from experienced people. So over the past month I haven't changed anything except for speakers, but I doubt that this is the cause. The BSODs appear mostly while playing youtube videos(I listen to music mixes which are long). I have formated my computer and flashed the motherboard driver, I also downgraged and upgraded graphics drivers with no success :( I have no further knowledge on troubleshooting a problem like this so I would greatly appreciate any advice!

Here is the BlueScreenView analasys txt file:

Link Removed

All help is appreciated!
 


Solution
FWIW - I don't trust the Windows Memory test.
Run the MemTest86+ test that's in my Hardware Diagnostics link.
If that passes, then run the Prime95 test - as that will stress your RAM more than MemTest86+ does.

Your BIOS dates from 2008. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

Only 120 Windows Updates installed. Most systems have 150 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all)...
A great number of different BSOD error codes is suggestive of a low-level problem. 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 ).

1) Please provide this information so we can provide a complete analysis: Link Removed

2) While waiting for a reply, please run these free diagnostics: Link Removed
Please let us know the results.
 


As I said I flashed the BIOS, I am not overclocking any component and there are no viruses as I fully scanned the computer and formated Windows 7. I'm guessing this is an automatic reply :)
 


Yes it is a "canned speech" (but not automated - I have to copy/paste it in), but it's also to illustrate that there can be other problems - even with the steps that you've taken.
The point here is that you've got a low-level problem - and the reports/tests that I requested will get us started on figuring out what exactly it is.

1) Please provide this information so we can provide a complete analysis: Link Removed

2) While waiting for a reply, please run these free diagnostics: Link Removed
Please let us know the results.


When we analyze these reports, we fix/diagnose things in this order (with some exceptions):
1st - 3rd party driver issues
2nd - hardware issues
3rd - Windows issues

The reason for this is that well over 90% of BSOD's are due to 3rd party drivers
And, IME, the next most common reason is hardware.
Finally, although Windows problems are addressed last, we address Windows Updates early on - which usually fixes any Windows issues caused by missing updates. The reason for this becomes evident if you look through the Link Removed page - there's lot's of errors that have many different fixes listed through Windows Update (see Link Removed - there's more than 70 different Microsoft KB articles associated with that error alone).
 


Ok I've ran the Windows memory test and everything is ok, Ive also downloaded and ran the tool you recommended and the results are included below, I will run the rest of the tools later and post the results, one thing I've noticed is that when I run many programs at once I get a BSOD, now I'm thinking this could be caused by my RAM.

Link Removed
 


So here are the rest of the test I hope the problem becomes clear now.

Link Removed

Thanks for the support so far!
 


FWIW - I don't trust the Windows Memory test.
Run the MemTest86+ test that's in my Hardware Diagnostics link.
If that passes, then run the Prime95 test - as that will stress your RAM more than MemTest86+ does.

Your BIOS dates from 2008. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

Only 120 Windows Updates installed. Most systems have 150 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

You have an Atheros AR5007UG Wireless USB Network Adapter and it's drivers date from 2007
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Out of 15 memory dumps there were 10 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 ).

There are traces of Kaspersky drivers in the memory dumps. While not a sure diagnosis, I'd suggest removing it to see if that's the problem. When you remove it, please install a free antivirus while you're testing - and be sure that the Windows Firewall is turned back on.

I would suggest running all of the hardware diagnostics at this link: Link Removed
If there's no problem noted, then start with this procedure: Link Removed

Good luck!

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

Rt86win7.sys Thu Feb 26 04:04:22 2009 (49A65B16)
Realtek NIC
Link Removed

intelide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17)
Intel IDE storage driver
Link Removed

RtNdPt60.sys Sun Jul 19 22:26:38 2009 (4A63D5DE)
Realtek NDIS User mode I/O Driver - Ethernet
Link Removed



Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Sat Mar 23 07:58:48.286 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032313-17128-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:56:25.081[/B]
Probably caused by :[B]memory_corruption ( nt!MmIsFileMapped+fe )[/B]
BugCheck [B]1000008E, {c0000005, 8330687b, a9e89b54, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: c0000005, The exception code that was not handled
Arg2: 8330687b, The address that the exception occurred at
Arg3: a9e89b54, Trap Frame
Arg4: 00000000
BUGCHECK_STR:  0x8E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: [B]0x8E_nt!MmIsFileMapped+fe[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar 22 16:47:46.433 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032213-19609-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 3:45:44.228[/B]
Probably caused by :[B]ntkrpamp.exe ( nt!KiTrap0E+dc )[/B]
BugCheck [B]1A, {41287, 45738038, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00041287, An illegal page fault occurred while holding working set synchronization.
    Parameter 2 contains the referenced virtual address.
Arg2: 45738038
Arg3: 00000000
Arg4: 00000000
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: [B]0x1a_41287_nt!KiTrap0E+dc[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Mar 21 16:16:15.210 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032113-17690-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:08:20.004[/B]
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by :[B]NETIO.SYS ( NETIO!PtGetKey+43a )[/B]
BugCheck [B]19, {20, 87839430, 8783a2d8, 9bd58cf6}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 87839430, The pool entry we were looking for within the page.
Arg3: 8783a2d8, The next pool entry.
Arg4: 9bd58cf6, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x19_20_NETIO!PtGetKey+43a[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Mar 21 16:01:03.439 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032113-21262-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:20:15.234[/B]
Probably caused by :[B]memory_corruption ( nt!MiDereferenceControlAreaPfn+2b )[/B]
BugCheck [B]A, {d35cbe82, 2, 1, 8307a6e2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: d35cbe82, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8307a6e2, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Illustrator.ex
FAILURE_BUCKET_ID: [B]0xA_nt!MiDereferenceControlAreaPfn+2b[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Mar 21 15:39:59.000 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032113-15615-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 2:02:35.795[/B]
Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+336 )[/B]
BugCheck [B]19, {3, 85f2d210, 85f2d210, c409b144}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 85f2d210, the pool entry being checked.
Arg3: 85f2d210, the read back flink freelist value (should be the same as 2).
Arg4: c409b144, the read back blink freelist value (should be the same as 2).
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  avp.exe
FAILURE_BUCKET_ID: [B]0x19_3_nt!ExDeferredFreePool+336[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar 18 15:46:08.540 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-24351-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 4:17:22.334[/B]
*** WARNING: Unable to verify timestamp for RtNdPt60.sys
*** ERROR: Module load completed but symbols could not be loaded for RtNdPt60.sys
*** WARNING: Unable to verify timestamp for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*** WARNING: Unable to verify timestamp for athrusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrusb.sys
Probably caused by :[B]RtNdPt60.sys ( RtNdPt60+3f8b )[/B]
BugCheck [B]C5, {7713b172, 2, 1, 8312f4c1}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 7713b172, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8312f4c1, address which referenced memory
BUGCHECK_STR:  0xC5_2
PROCESS_NAME:  opera.exe
FAILURE_BUCKET_ID: [B]0xC5_2_RtNdPt60+3f8b[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar 18 11:27:47.581 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-18564-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 4:29:28.376[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by :[B]memory_corruption ( nt!MiGetPreviousNode+32 )[/B]
BugCheck [B]A, {ad0e3e2e, 0, 0, 830a8c0c}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ad0e3e2e, memory referenced
Arg2: 00000000, IRQL
Arg3: 00000000, 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: 830a8c0c, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: [B]0xA_nt!MiGetPreviousNode+32[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Mar 16 09:40:07.170 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-17628-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 2:41:45.840[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+197249 )[/B]
BugCheck [B]D1, {e15cc55a, 2, 8, e15cc55a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: e15cc55a, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: e15cc55a, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID: [B]0xD1_CODE_AV_BAD_IP_nvlddmkm+197249[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Mar  3 14:24:26.183 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030313-15600-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 8:00:42.978[/B]
Probably caused by :[B]ntkrpamp.exe ( nt!FsRtlLookupPerStreamContextInternal+9a )[/B]
BugCheck [B]50, {e4679592, 0, 830cfd83, 2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: e4679592, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 830cfd83, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000002, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID: [B]0x50_nt!FsRtlLookupPerStreamContextInternal+9a[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Mar  2 11:28:53.858 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030213-18907-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:51:06.653[/B]
Probably caused by :[B]ntkrpamp.exe ( nt!PspReturnQuota+11f )[/B]
BugCheck [B]21, {0, 1, b7b1fc02, b76e3b56}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000, The process (if any) that was initially charged.
Arg2: 00000001, The quota type in question (paged pool, nonpaged pool, etc.)
Arg3: b7b1fc02, The initial charge amount to return.
Arg4: b76e3b56, The remaining (unreturned) charge.
BUGCHECK_STR:  0x21
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x21_nt!PspReturnQuota+11f[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Mar  2 10:08:39.777 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030213-24336-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 1:13:51.572[/B]
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by :[B]ntkrpamp.exe ( nt!ExFreePoolWithTag+1b1 )[/B]
BugCheck [B]C2, {7, 109b, 632ad5f6, 8772c938}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000109b, (reserved)
Arg3: 632ad5f6, Memory contents of the pool block
Arg4: 8772c938, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0xc2_7_nt!ExFreePoolWithTag+1b1[/B]
  BIOS Version                  F9
  BIOS Release Date             12/29/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar  1 18:39:52.258 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030113-22276-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:52:22.053[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14d78d )[/B]
BugCheck [B]D1, {3409a02f, 2, 0, 90d5c78d}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 3409a02f, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90d5c78d, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: [B]0xD1_nvlddmkm+14d78d[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 26 17:59:33.237 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022613-21309-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 4:12:56.048[/B]
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
Probably caused by :[B]hardware ( Wdf01000+12f0a )[/B]
BugCheck [B]BE, {834257a0, 3425121, 8ba1fa64, b}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 834257a0, Virtual address for the attempted write.
Arg2: 03425121, PTE contents.
Arg3: 8ba1fa64, (reserved)
Arg4: 0000000b, (reserved)
BUGCHECK_STR:  0xBE
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  wininit.exe
FAILURE_BUCKET_ID: [B]IP_MISALIGNED[/B]
  BIOS Version                  F6
  BIOS Release Date             06/05/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Feb 25 18:43:38.200 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022513-36332-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 2:01:36.010[/B]
Probably caused by :[B]ntkrpamp.exe ( nt!NtQueryVirtualMemory+2a2 )[/B]
BugCheck [B]1000008E, {c0000005, 8325eb27, 98667c14, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: c0000005, The exception code that was not handled
Arg2: 8325eb27, The address that the exception occurred at
Arg3: 98667c14, Trap Frame
Arg4: 00000000
BUGCHECK_STR:  0x8E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: [B]0x8E_nt!NtQueryVirtualMemory+2a2[/B]
  BIOS Version                  F6
  BIOS Release Date             06/05/2008
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  G31M-S2L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Feb 25 16:41:00.401 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\022513-30685-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Built by: [B]7601[/B].18044.x86fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 1:12:03.212[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+304d3d )[/B]
BugCheck [B]D1, {20, 2, 0, 90d0cd3d}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000020, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90d0cd3d, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  avp.exe
FAILURE_BUCKET_ID: [B]0xD1_nvlddmkm+304d3d[/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]**************************Sat Mar 23 07:58:48.286 2013 (UTC - 4:00)**************************
[COLOR=RED][B]athrusb.sys                 Mon Jan 29 07:56:51 2007 (45BDEF13)[/B][/COLOR]
[COLOR=RED][B]Rt86win7.sys                Thu Feb 26 04:04:22 2009 (49A65B16)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:11:03 2009 (4A5BBF07)
[COLOR=RED][B]intelide.sys                Mon Jul 13 19:11:19 2009 (4A5BBF17)[/B][/COLOR]
[COLOR=RED][B]RtNdPt60.sys                Sun Jul 19 22:26:38 2009 (4A63D5DE)[/B][/COLOR]
klmouflt.sys                Mon Nov  2 11:26:08 2009 (4AEF0820)
amdxata.sys                 Fri Mar 19 12:19:01 2010 (4BA3A3F5)
kl2.sys                     Fri Mar  4 04:17:16 2011 (4D70AE1C)
kl1.sys                     Fri Mar  4 04:17:22 2011 (4D70AE22)
klim6.sys                   Thu Mar 10 09:35:57 2011 (4D78E1CD)
RTKVHDA.sys                 Tue Jun 19 04:49:44 2012 (4FE03D28)
klif.sys                    Tue Sep 25 10:30:48 2012 (5061C018)
nvhda32v.sys                Wed Dec 19 00:41:17 2012 (50D1537D)
nvlddmkm.sys                Sat Feb  9 18:13:25 2013 (5116D815)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar 18 11:27:47.581 2013 (UTC - 4:00)**************************
nvhda32v.sys                Tue Jul  3 11:24:41 2012 (4FF30EB9)
nvlddmkm.sys                Tue Oct  2 14:15:55 2012 (506B2F5B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar  1 18:39:52.258 2013 (UTC - 4:00)**************************
nvlddmkm.sys                Sat Dec 29 01:49:51 2012 (50DE928F)
[/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
Link Removed
 


Solution
Ok I've updated every driver that was in red that had an update and I'll be carrying the MemTest86+ as soon as I can. Thank you so much for that analasys!
 


I've hadn't had a BSOD while doing the things that caused one but I'm sill going to carry out the RAM test, if it doesn't return any errors then I'm going to assume that the driver updates fixed the problem, thank you for your help!!
 


Back
Top