New
#1
Where are the logs of BSOD in Windows 7?
I just had a BSOD a few days ago but forgot to write down the error number. Does Windows 7 keep a log of BSOD and where can I find it?
TIA
I just had a BSOD a few days ago but forgot to write down the error number. Does Windows 7 keep a log of BSOD and where can I find it?
TIA
Hi rfe777,
Please follow - Blue Screen of Death (BSOD) Posting Instructions
The tool will gather all the necessary files for a through troubleshooting analysis of your system, this will include the .dmp files from your BSODs.
However, to answer your question, Windows (default settings) will save all the Minidumps and Kernel Memory dumps in these two directories:
Minidumps:
Kernel Memory Dump (default):Code:%systemroot%\Minidump or C:\Windows\Minidump
Code:%systemroot% or C:\Windows\
It'll be fine just posting in this thread :)
OK:)
About what happened: A few days ago I had a BSOD for the second time in 2-3 months. The first time it was shortly after updating the drivers for my ATI Radeon 4850 graphics card(but I'm not sure it's the cause of the BSOD).
The second time I don't have any idea what's caused it.
Here is the zip with the dumb files.
Any help you can give me will be greatly appreciated, because if it happens again I'll have to format my PC.
Code:BugCheck A, {408000e, 2, 1, 82e8e54f} Probably caused by : udfs.sys ( udfs!UdfPerformVerify+6d )This bugcheck indicates that a instruction or device driver has attempted to access a invalid memory address, and then cause a interrupt at a IRQL level which was too high.Code:Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
The memory address being referenced, seems to point to the ecx CPU register.Code:TRAP_FRAME: 8e7779e4 -- (.trap 0xffffffff8e7779e4) ErrCode = 00000002 eax=8578db6c ebx=8578db64 ecx=0408000e edx=00000000 esi=85750d48 edi=85750e08 eip=82e8e54f esp=8e777a58 ebp=8e777abc iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!KeWaitForSingleObject+0x373: 82e8e54f 8939 mov dword ptr [ecx],edi ds:0023:0408000e=????????
Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:
InformationAdditional Help - Using Driver Verifier to identify issues with Drivers
Install and perform full scans with:
- Malwarebytes : Free anti-malware download <-- Ignore this point
- Microsoft Security Essentials | Protect against viruses, spyware, and other malware
InformationRemember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system
You can also view this thread for a complete free and lightweight security protection combination:
I would recommend MSE, it causes the least problems from my experience, ESET can cause BSODs very rarely.
You can use ESET if you want :)