Hello cryption and welcome to Sevenforums.
Unfortunately your attachment did not meet up to the requirements we'd recommend when debugging a crash. Some system infos, driver infos as well as a nfo is needed so we're able to dig into your crash.
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
If you're having problems with getting the nfo-
To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
With that said, let's look at what we've got.
BSOD Analyse
Driver
Code:
2: kd> lmvm asmtxhci
start end module name
fffff880`04456000 fffff880`044ba000 asmtxhci T (no symbols)
Loaded symbol image file: asmtxhci.sys
Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
Image name: asmtxhci.sys
Timestamp: Wed Sep 14 09:36:09 2011 (4E705969)
CheckSum: 0006E608
ImageSize: 00064000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
You've had some issues with an USB Driver from ASMedia. Click
Start | Search for
Device Manager | Expand all the drop downs | Look for the :warn: icons.
Another thing to do is to go to the PC Manufacturers website, and look for all these drivers.
If you're having any sort of Wireless USB Devices, I recommend not using them with Windows 7, as they're causing a stream of BSODs if you're running it asides other Wireless drivers.
ASMedia Technology
Driver timestamps looks OK
BCCode
Code:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.
Looking at your bugcheck it's likely that a memory corruption event were there. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.
Memtest86+ - Advanced Memory Diagnostic Tool
SFC
We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.
Tip
If you're having a custom customization layer on your Aero, it's likely to get restored to default.
Press
Start | search
'cmd' |
Right-click it
| open as
Admin | type
SFC /SCANNOW
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Best Regards,
Frederik.
