|02 Jul 2012||#1|
| || |
BSOD on startup
Hi for the past few days I have been experiencing the BSOD on random occasions, but today I'm getting it every time Windows boots into the desktop, I try'd booting into safe mode but still the same happens.
Below is the mini dump files, If someone could please help in resolving this issue, I would be most grateful.
|My System Specs|
|02 Jul 2012||#2|
| || |
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.
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.
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
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.
Driver timestamps looks OK
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.
Memtest86+ - Advanced Memory Diagnostic Tool
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.
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
SFC /SCANNOW Command - System File Checker
|My System Specs|
|Similar help and support threads for2: BSOD on startup|
|BSOD on Startup - Startup Reapir not working||BSOD Help and Support|
|BSOD at startup, cant repair startup||BSOD Help and Support|
|BSOD after playing games + Random BSOD on startup||BSOD Help and Support|
|BSOD with D3, Startup||BSOD Help and Support|
|BSOD on startup , error 0x000000f4 . startup takes half an hour||BSOD Help and Support|
|Bsod on startup!||BSOD Help and Support|
|BSOD on Startup||BSOD Help and Support|