Tech Support Guy banner
Status
Not open for further replies.

Constant Blue Screen And Crashing

1K views 11 replies 3 participants last post by  charlesmpersonal 
#1 ·
Starting today Windows 7 has started giving me a blue screen and crash each time I start up the machine. I'm not sure what is causing it but it only happens when I boot normally, when I switch to safe mode the computer runs fine. Below are the details:

Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000002
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF800030DC16C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
 
#2 ·
Some reasons for Blue Screens
New hardware - software installed.
Device driver - Video driver - corrupted - faulty.
Faulty Ram - Overheating - Dying hard drive etc.
However, where the blue screen error is reported is not necessarily where it first started and may not be the cause.
======
Post the Minidump files
Create a new folder on the desktop and call it dumpfiles [or something similar]

Look in c:\windows\minidump
Copy the last 4 minidump files to that folder.
Close the folder and right click on it and select Send To Compressed [zipped] Folder.
Windows will compress the file and then save the new zipped file in the same location.
Attach the zip folder by using the 'Upload a File' button.
 
#10 ·
However, where the blue screen error is reported is not necessarily where it first started and may not be the cause.
If you know the hard drive is faulty - changing it should be done very soon.
And backup your files and data, asap.
A hard drive test is listed in # post 8
======
Mem test from a USB stick
http://www.memtest.org/#downiso
Scroll down to [ Download (Pre-built & ISOs]
Download -Auto-installer for USB Key (Win 9x/2k/xp/7) *NEW!*

Download to desktop - unzip it there.
Put the USB stick into your Pc USB slot.

Click on the Install icon on your desktop - it will then have a box appear asking you to name the USB drive letter.
Put the drive letter in the box and click on install.

But first to check the correct USB drive letter - with the USB stick in the USB slot of your PC, right click My Computer > click on Open.
Your USB stick will be listed with the drive letter.
======
USB - DVD drive.
http://www.pcworld.co.uk/gbuk/compu...drives/1113_8405_71455_xx_xx/xx-criteria.html
 
#8 ·
Minidump check x 1 - in part.
PHP:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d899ab76f0, b3b7465eec284646, fffff80002eae9d0, 1}

*** 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

Followup: memory_corruption
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d899ab76f0, Reserved
Arg2: b3b7465eec284646, Reserved
Arg3: fffff80002eae9d0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Debugging Details:
------------------
BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002adbd00

STACK_TEXT:  
fffff880`033b65d8 00000000`00000000 : 00000000`00000109 a3a039d8`99ab76f0 b3b7465e`ec284646 fffff800`02eae9d0 : nt!KeBugCheckEx

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002eaeb99 - nt!WmipQueryAllDataMultiple+1c9
    [ bc:9c ]
1 error : !nt (fffff80002eaeb99)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
You may have other problems happening here but your next best move is to run a Memory test.
Mem Test.
http://www.memtest.org/
Scroll down to 'Download (Pre-built & ISOs)'
'Download - Pre-Compiled Bootable ISO (.zip)'

Download the ISO file then burn the ISO to a Cd.
Start the Pc using the Cd and run the memory test overnight or for at least 8 passes.

It is best to run a full scan on individual Ram sticks if you can.
Or run the test but if any errors are shown - then remove all sticks of Ram and test each Ram stick one at a time,
and in different slots.

Guide to using Memtest86+
http://www.bleepingcomputer.com/forums/topic207910.html
======
Also run a hard drive test.
SeaTools for DOS tutorial - ISO to CD
http://knowledge.seagate.com/articles/en_US/FAQ/201271en?language=en_US

http://www.tacktech.com/display.cfm?ttid=287
 
#9 ·
Mem Test seems to require an optical drive, which my laptop doesn't have. Can it run by USB or mount with daemon tools? I hoped the minidump file would get to the root of the problem, because my HD is wearing out and I assumed it could be that but now you say it could be the ram. I know I need a new HD but don't want to buy more RAM unless I can confirm that existing ram is faulty.
 
#11 ·
I think that you might have a infected and corrupt hard drive. I have had that issue before and the HDD never worked again. I would buy a new HDD, or try Reinstalling the OS on it. If you get a new HDD, I recommend that you have somewhere like BestBuy put it in and work on installing the OS. I tried that myself and the OS would not go on the HDD. BestBuy said they would do it for a fee.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top