Win7-32bit BSOD problem

[renaissance]

Hi,
I'm Theodore from Greece, I've installed windows 7-32bit on my pc .
The pc crashes once in a while , with blue screens and reboot.
I had the same prob with winxp so i installed win7 supposing that restarts would stop...But nothing..
So far i have done these:

remove the tick on "automatically restart" -> (so i could see the blue screen..

update drivers, with device manager and driver genius -> nothing

update bios from asus website -> nothing

do check disk -> nothing

defrag -> nothing

usb legacy support disabled from bios (smwhere read that)->nothing

sptd.sys fixed -> nothing

Rc task disabled (read that too) -> nothing

sleep and hibernation set to never - >nothing

run memtest (3.5) but i have difficulties because when it starts testing (single cpu or multiple) at test 2 and 45% reboots .
when i choose to run memtest previous version (3.4) it recognizes cpu as pentium 3 and completes the test with 10 errors at test 5.

I noticed that asus set to my memories timings 5-5-5-12 and voltage 1,8 , so i put timings 4-4-4-12 and voltage 2.2 (manufacture had these timings although gives voltage 2.0)
I had 6 errors in test 5 .
2 months ago i hadn't any prob with the same ram.

EVENT LOG:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 11/12/2009 3:22:02 μμ
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Renaissance-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2009-12-11T13:22:02.192029300Z" />
<EventRecordID>12560</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Renaissance-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0xff</Data>
<Data Name="BugcheckParameter3">0x1</Data>
<Data Name="BugcheckParameter4">0x8301fcc3</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>



also get bugcheckcode 209.
This is the minidump file:
RapidShare: 1-CLICK Web hosting - Easy Filehosting


Can someone read the minidump file and help me , or have any guesses????

Thanks in advance Theodore.

 

[Legacy]

Hey. These are your drivers that need updating. I recommend a clean install instead:

eamon    eamon.sys    Mon Aug 18 07:13:07 2008
ASACPI   ASACPI.sys   Thu Aug 12 22:52:52 2004
Epfwndis Epfwndis.sys Mon Aug 18 07:02:11 2008
easdrv   easdrv.sys   Mon Aug 18 07:14:08 2008
SCDEmu   SCDEmu.SYS   Mon Apr 09 08:27:07 2007
epfwtdi  epfwtdi.sys  Mon Aug 18 07:02:06 2008
mv61xx   mv61xx.sys   Thu Mar 19 23:47:19 2009

So save yourself the grief and do a clean Windows install by booting to the DVD. Like I said, you could Google those and try to update instead but probably not worth it.

Btw, lowering RAM timings is not going to help and in fact, will make it worse. Visit Crucial's website for the correct timings and Vdimm (voltage.)

Don't ever use Driver Genius or similar. Those will ruin your Windows faster than malware can.

 

[zigzag3143]

Hi,
I'm Theodore from Greece, I've installed windows 7-32bit on my pc .
The pc crashes once in a while , with blue screens and reboot.
I had the same prob with winxp so i installed win7 supposing that restarts would stop...But nothing..
So far i have done these:

remove the tick on "automatically restart" -> (so i could see the blue screen..

update drivers, with device manager and driver genius -> nothing

update bios from asus website -> nothing

do check disk -> nothing

defrag -> nothing

usb legacy support disabled from bios (smwhere read that)->nothing

sptd.sys fixed -> nothing

Rc task disabled (read that too) -> nothing

sleep and hibernation set to never - >nothing

run memtest (3.5) but i have difficulties because when it starts testing (single cpu or multiple) at test 2 and 45% reboots .
when i choose to run memtest previous version (3.4) it recognizes cpu as pentium 3 and completes the test with 10 errors at test 5.

I noticed that asus set to my memories timings 5-5-5-12 and voltage 1,8 , so i put timings 4-4-4-12 and voltage 2.2 (manufacture had these timings although gives voltage 2.0)
I had 6 errors in test 5 .
2 months ago i hadn't any prob with the same ram.

EVENT LOG:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 11/12/2009 3:22:02 μμ
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Renaissance-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2009-12-11T13:22:02.192029300Z" />
<EventRecordID>12560</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Renaissance-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0xff</Data>
<Data Name="BugcheckParameter3">0x1</Data>
<Data Name="BugcheckParameter4">0x8301fcc3</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>



also get bugcheckcode 209.
This is the minidump file:
RapidShare: 1-CLICK Web hosting - Easy Filehosting


Can someone read the minidump file and help me , or have any guesses????

Thanks in advance Theodore.

Hi and welcome

This dmp appears to be caused by multiple things.
First--old drivers--the below drivers are as ild as 9 years. Obviously this machine was upgraded and not clean installed as MS recommmends. These must be upgraded

Second--Hardware-- The HAL (hardware application layer) is clearly involved. I suspect memory

Third--Heat-- there is a possible heat issue.

I would
download and run memtestx86 overnight to see if the ram fails and see if heat presents itself
Run a system file check
type cmd in search>right click and run as admin SFC /SCANNOW

Hope this helps

Ken J+

ASACPI.sys 0x91def000 0x91df0420 0x00001420 0x411c2d04 8/12/2004 9:52:52 PM
secdrv.SYS 0xa209a000 0xa20a4000 0x0000a000 0x45080528 9/13/2006 8:18:32 AM
SCDEmu.SYS 0x90d2f000 0x90d36260 0x00007260 0x461a311b 4/9/2007 7:27:07 AM
epfw.sys 0x83200000 0x83214000 0x00014000 0x48a956a9 8/18/2008 6:02:01 AM
epfwtdi.sys 0x8c3e8000 0x8c3fa000 0x00012000 0x48a956ae 8/18/2008 6:02:06 AM
Epfwndis.sys 0x9180d000 0x91818000 0x0000b000 0x48a956b3 8/18/2008 6:02:11 AM
eamon.sys 0x9b960000 0x9b9ad000 0x0004d000 0x48a95943 8/18/2008 6:13:07 AM
easdrv.sys 0x90d8c000 0x90d9b000 0x0000f000 0x48a95980 8/18/2008 6:14:08 AM

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\121109-45255-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c0a000 PsLoadedModuleList = 0x82d52810
Debug session time: Fri Dec 11 08:20:28.572 2009 (GMT-5)
System Uptime: 0 days 0:20:52.976
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, ff, 1, 8301fcc3}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )

Followup: MachineOwner
---------

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

[B]IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8301fcc3, address which referenced memory[/B]

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
 00000000 

CURRENT_IRQL:  0

FAULTING_IP: 
hal!HalEndSystemInterrupt+67
8301fcc3 8bce            mov     ecx,esi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

[I][B]PROCESS_NAME:  Saboteur.exe[/B][/I]

TRAP_FRAME:  a5379cac -- (.trap 0xffffffffa5379cac)
ErrCode = 00000002
eax=00000000 ebx=0ef5fd18 ecx=8df00000 edx=00000000 esi=a5379d34 edi=662f59e7
eip=8301fcc3 esp=a5379d20 ebp=a5379d24 iopl=0         nv up di pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010046
hal!HalEndSystemInterrupt+0x67:
8301fcc3 8bce            mov     ecx,esi
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8301fcc3 to 82c507eb

STACK_TEXT:  
a5379cac 8301fcc3 badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
a5379d24 8301d479 82c4d400 000000d1 0ef5fd18 hal!HalEndSystemInterrupt+0x67
a5379d24 0084c9fc 82c4d400 000000d1 0ef5fd18 hal!HalpClockInterruptPn+0x1a1
WARNING: Frame IP not in any known module. Following frames may be wrong.
0ef5fd18 00000000 00000000 00000000 00000000 0x84c9fc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+2cf
82c507eb 833dc4dad68200  cmp     dword ptr [nt!KiFreezeFlag (82d6dac4)],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTrap0E+2cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0xA_nt!KiTrap0E+2cf

BUCKET_ID:  0xA_nt!KiTrap0E+2cf

Followup: MachineOwner
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8301fcc3, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
 00000000 

CURRENT_IRQL:  0

FAULTING_IP: 
hal!HalEndSystemInterrupt+67
8301fcc3 8bce            mov     ecx,esi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Saboteur.exe

TRAP_FRAME:  a5379cac -- (.trap 0xffffffffa5379cac)
ErrCode = 00000002
eax=00000000 ebx=0ef5fd18 ecx=8df00000 edx=00000000 esi=a5379d34 edi=662f59e7
eip=8301fcc3 esp=a5379d20 ebp=a5379d24 iopl=0         nv up di pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010046
hal!HalEndSystemInterrupt+0x67:
8301fcc3 8bce            mov     ecx,esi
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8301fcc3 to 82c507eb

STACK_TEXT:  
a5379cac 8301fcc3 badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
a5379d24 8301d479 82c4d400 000000d1 0ef5fd18 hal!HalEndSystemInterrupt+0x67
a5379d24 0084c9fc 82c4d400 000000d1 0ef5fd18 hal!HalpClockInterruptPn+0x1a1
WARNING: Frame IP not in any known module. Following frames may be wrong.
0ef5fd18 00000000 00000000 00000000 00000000 0x84c9fc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+2cf
82c507eb 833dc4dad68200  cmp     dword ptr [nt!KiFreezeFlag (82d6dac4)],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTrap0E+2cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0xA_nt!KiTrap0E+2cf

BUCKET_ID:  0xA_nt!KiTrap0E+2cf

Followup: MachineOwner
---------

 

[renaissance]

first of all i'd like to thank u for answering so fast..

1) Heat is not a prob...
2) I updated the drivers u told me but nothing so far...
3) i had a clean install of win7..(formatted the particion and then install)
4) i cannot run the memtest..as i mentioned before..i download it , i burn to a cd, boot from the cd..but it begins and then reboot again in pass 0 , test 2 ,45% !! it doesnt mention an error, just crashes and reboots!! memtest shouldn't run and just mention the errors? Any guesses? version of memtest 3.5 .Wrong version?

5)Also u wrote down about " mv61xx.sys" driver.This is the IDE controller that i have. It's being used by a hdd and a dvd rom..And also is up to date..so i think there is nothing left to do with this one....

 

[Legacy]

Are you sure you updated ASACPI.sys? Check in the driver folder:

C:\Windows\System32\drivers

 

[zigzag3143]

R

Yeah, sorry for repeating myself. I have been so many BSOD's, that they all blend in to one gaint. Since the HAL (hardware abstraction layer) is involved I am still thinking memory. Is there any other hardware that is different like a card reader, or anything different?

Ken

 

[renaissance]

no prob ken, thanks anyway.
No i dont have any other hardware besides the usual (hdd, memory, dvd-rom, graphics card)
How can i run memtest ? Is it the version?

no, i didnt update asacpi.sys driver , my fault.
It links to a utility from asus that i dont use so i uninstall it.
So , no more asacpi.sys

 

[zigzag3143]

no prob ken, thanks anyway.
No i dont have any other hardware besides the usual (hdd, memory, dvd-rom, graphics card)
How can i run memtest ? Is it the version?

As far as I know the version doesnt matter. Is your computer a desktop?

If so can you pull all but 1 memory stick and try memtest?

Grasping at straws here


Ken J

 

[renaissance]

yeap its a desktop..
i ll try tomorrow in the morning to play with rams and dimms
an run memtest. Ill let u know ..

Ken i d like to ask u another question: the timings that asus mobo gives to crucial ram are 5-5-5-15 with voltage 1,8!!!!!
Crucial says that correct timings are 4-4-4-12 with 2.0 voltage.
Now my ram works at 5-5-5-15 (Auto) and manually set up to 2,0 vdimm.

Is this fine or should i change it?

 

[usasma]

In addition to the suggestions already posted, I'd have to state that there are issues with voltages for RAM in the P5 series of motherboards from Asus. Check the suggestions at the Asus website and at the Crucial website.