Win7 Pro 64Bit - memdump

Please update the chipset drivers for your motherboard. One of the unknown devices is a USB controller. Hopefully that'll let us figure out what the other one is.

If the RAM is overheating, then that will cause BSOD's. I'd suggest pointing a house fan at the RAM to keep it cool while testing. More to follow after work....

After reviewing the uploads, if the RAM is that hot, then I'd suggest running MemTest to see if that's what's causing the issues: Memory Diagnostics (read the details at the link)

If that doesn't pick up anything, then try Prime95 according to these directions:]

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

Watch it closely, and if it starts spitting out errors, terminate the test IMMEDIATELY.

New year and another problem

Had a recent update and getting random BSOD. Seems there is an unknown device again ... how can I fix this grrrr.

Zip file with the latest info is attached. No change of system. Win7 Pro 64 bit with 8 gig Ram.

Thanks in advance for the help.

edit: Looking at my older posts ... I ended up staggering the memory sticks after going over the motherboard documentation. Read the instructions ... who would have guessed After i did that memory temps fine ... barely warm.

I really can't remember everything from the previous problem, so I'll just start over fresh here.
We should consider it a new issue anyway - due to the long period that's elapsed since you last posted.

I have no clue as to the make/model of your system. If it's a custom build, we'll need the make/model of the motherboard. Is it a desktop or laptop? Unplug all USB devices and see if the unknown device remains.

You have a TP-LINK 150Mbps Wireless USB Adapter. Using these devices with older drivers is sure to cause BSOD's. DO NOT use these devices if you cannot find Win7 drivers for them - compatibility mode just doesn't work.
Here's my rant about these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and 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 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.

MSINFO32 shows that this device is disabled:

Microsoft Virtual WiFi Miniport Adapter #2 {5D624F94-8850-40C3-A3FA-A4FD2080BAF3}\VWIFIMP\6&2FE22C31&2&04 This device is disabled.

Please enable the device and then update the drivers (?Windows Update?). Then either leave it enabled or uninstall it from the system - don't disable it again (for testing purposes).

Memory dumps from Jan 2012 are all STOP 0x109 (details on error here: BSOD Index ) and all blame memory_corruption. This is most likely either a RAM issue, or a driver issue. Please run MemTest and Prime 95 in order to firmly rule out the RAM (links to these programs here: Hardware Diags )

Please post back with the results of the memory tests.

Sometimes Norton will cause memory problems, and not leave any clues that I can find.
Please try this to rule out your Norton:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_...080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010612-24913-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan  6 18:05:49.373 2012 (UTC - 5:00)
System Uptime: 1 days 8:35:14.793
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000109
Arguments a3a039d8`a1b56721 b3b7465e`f4323677 fffff800`03418790 00000000`00000001
BiosVersion = 1006   
BiosReleaseDate = 08/18/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010512-26192-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 06:10:19.541 2012 (UTC - 5:00)
System Uptime: 0 days 8:28:06.961
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000109
Arguments a3a039d8`ab1145e5 b3b7465e`fd8e153b fffff800`034187ff 00000000`00000001
BiosVersion = 1006   
BiosReleaseDate = 08/18/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010412-23587-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan  4 21:01:28.986 2012 (UTC - 5:00)
System Uptime: 1 days 5:02:51.391
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
Bugcheck code 00000109
Arguments a3a039d8`a9ba387c b3b7465e`fc3707d2 fffff800`0341803d 00000000`00000001
BiosVersion = 1006   
BiosReleaseDate = 08/18/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Just FYI -

Just FYI - a recent poster (early Nov 2011) states that they were advised by Asus to manually set their memory settings/timings/voltages because of issues with the M4 series of motherboards.
You can get the settings/timings/voltages from the website of your RAM manufacturer.

The dumps all indicate something on the system is modifying kernel-level code and overwriting function areas with different data - as soon as this happens, the checksum and hash of the binary in memory and the one on disk that the file in memory came from don't match - and Windows bugchecks with a 0x109 immediately. In this case, there is indeed an overwrite in non-writable kernel memory for memory regions used by the kernel itself:

Code:

0: kd> !chkimg -lo 50 -db !nt
4 errors : !nt (fffff80003418257-fffff80003418de7)
fffff80003418250  49  8b  73  48  49  8b  e3 *61  5f  41  5e  41  5d  41  5c  5f I.sHI..a_A^A]A\_
...
fffff80003418670  fb  7c  7e  49  89  5d  00 *8f  15  97  0a  13  00  48  03  d1 .|~I.].......H..
...
fffff800034188d0  90  90  90  90  90  90  90 *b0  90  90  90  90  90  90  90  90 ................
...
fffff80003418de0  48  83  ec  28  33  d2  8d *4e  03  e8  82  b0  d3  ff  33  c0 H..(3..N......3.

The question is (given some of these are also "off by one" errors), WHEN did this start? This is almost always a hardware problem.