BSODS & Bizarre Shutdowns

Jun 29, 2015
Reaction score
Dear Techies,

Of late, I've been plagued by BSODS so much so that I get about 3 everyday. It all began a couple of
months ago when Windows began to shut down suddenly and recurrently. On restarting, sometimes
it boots till the Windows logo and BSODS; at other times, it freezes at the logo. Subsequently, it starts
only after I remove and re-fix the battery.

I have tried everything that my limited non-techie knowledge availed me. Here's a list of the methods
I've tried:

1) The good ol' chkdsk/f/r (or r/f)... Stabilises the system temporarily.

2) sfc/scannow... Same as above.

3) Last known good configuration

4) Startup Repair

5) Memory Test

6) System Restore

As I've said, all these methods have only served to make it work temporarily.

I've this vague suspicion that it could be because of the battery or that while I'm working I keep the
laptop on continuous charge.I don't know for sure and that's where you guys come in.

My system specs and all the other technical details are attached. However, I'm giving the basics below
for a 'quick see'

System Information report written at: 06/29/15 13:07:44
System Name: ISHRAT
[System Summary]

Item Value
OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name NA
System Manufacturer LENOVO
System Model 2767W3A
System Type X86-based PC
Processor Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz, 2534 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date LENOVO 7UET94WW (3.24 ), 17/10/2012
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name NA
Time Zone India Standard Time
Installed Physical Memory (RAM) 2.00 GB
Total Physical Memory 1.90 GB
Available Physical Memory 889 MB
Total Virtual Memory 3.80 GB
Available Virtual Memory 2.53 GB
Page File Space 1.90 GB
Page File C:\pagefile.sys

Any help will be much appreciated.

Thank you

Note: I couldn't upload the file. The message says that it's 'too large'.


Jun 29, 2015
Reaction score
Thanks a ton, mate.
The problem is that the system has stopped generating the .DMP files. I did the following to rectify it (the result was nada):

1) Confirmed the existence of the Minidump folder in windows, via %systemroot%.

2) The 'Automatically manage paging file size for all drives' was already checked.

3) 'Write an event to the system log' was already checked.

4) Changed from 'Kernel memory dump' which was there by default to 'Small memory dump' (128 KB).

5) The path, '%SystemRoot%\Minidump, was already there by default.

7) Started 'Windows Error Reporting Service' and made it 'Automatic'.

Am I missing something here? Maybe you're required to restart before the changes take effect. I don't remember restarting it.

So my only option is to wait for another crash and hope for the best.

Nice lines, mate. Here's one I like

"When I am dead, I hope it may be said, 'His sins were scarlet, but his books were read.'"
-- Hilaire Belloc


Mar 1, 2012
Reaction score

I'm incredibly sorry I didn't respond. Please feel free to send me a PM if I don't respond in the future.

If you haven't resolved you problem, please try the suggestion below.

I know crash dumps are in the following locations:
c:\Windows\Live KernelReports\WATCHDOG

Maybe the last one you haven't checked?

Please set the crash dump back to kernel.
  1. Click the Start Button.
  2. Type in cmd
  3. You should see cmd.exe in the list.
  4. Right click on cmd.exe and select "Run as Administrator"
  5. In the command prompt window type in:

wmic recoveros set DebugInfoType = 2
It should say that the command was successful.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question