Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - Reloaded Fresh but Still happening :(

21 Feb 2012   #11
Jenelia

Windows 7 Ultimate 64 bit
 
 

Well today I booted up my computer back to windows for the first time since running scan from Seagate tools and it bluescreen right away, twice. This is the last report from windbg

CODE


Quote:
Loading Dump File [C:\Windows\Minidump\022112-21075-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e98670
Debug session time: Tue Feb 21 18:27:34.642 2012 (UTC - 5:00)
System Uptime: 0 days 0:07:30.125
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff80002ced931, 0, fffffa800ceba600}

Probably caused by : memory_corruption ( nt!MiDispatchFault+aa2 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002ced931, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffffa800ceba600, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!MiDispatchFault+aa2
fffff800`02ced931 4c3bea cmp r13,rdx

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: fffffa800ceba600

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

BUGCHECK_STR: 0x1E_c000001d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: MsMpEng.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d1b588 to fffff80002ccfc40

FAILED_INSTRUCTION_ADDRESS:
nt!MiDispatchFault+aa2
fffff800`02ced931 4c3bea cmp r13,rdx

STACK_TEXT:
fffff880`028aaf98 fffff800`02d1b588 : 00000000`0000001e ffffffff`c000001d fffff800`02ced931 00000000`00000000 : nt!KeBugCheckEx
fffff880`028aafa0 fffff800`02ccf2c2 : fffff880`028ab778 fffffa80`0e5cedc0 fffff880`028ab820 0000007f`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`028ab640 fffff800`02ccd41f : fffff880`028ab820 00000000`00000000 00000000`01239f00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`028ab820 fffff800`02ced931 : 00000000`00000001 fffff680`00021680 fffff880`028abc20 fffff6fb`40000108 : nt!KiInvalidOpcodeFault+0x11f
fffff880`028ab9b0 fffff800`02cdcf19 : 00000000`00000000 00000000`01238ff8 fffff700`01080000 00000000`00000000 : nt!MiDispatchFault+0xaa2
fffff880`028abac0 fffff800`02ccdd6e : 00000000`00000000 00000000`01238ff8 00000000`00000b01 00000000`74bb2828 : nt!MmAccessFault+0x359
fffff880`028abc20 000007fe`ff2911fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0249e618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff2911fd


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDispatchFault+aa2
fffff800`02ced931 4c3bea cmp r13,rdx

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!MiDispatchFault+aa2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!MiDispatchFault+aa2

BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!MiDispatchFault+aa2

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



My System SpecsSystem Spec
.
21 Feb 2012   #12
Jenelia

Windows 7 Ultimate 64 bit
 
 

So now I'm going to go do a memory scan. I've already loaded the latest bios for this board. Reloaded defaults in the bios too, I wonder if I need to set voltages for the RAM or CPU. I never had to before and it worked fine up until a week ago.
My System SpecsSystem Spec
21 Feb 2012   #13
writhziden

Windows 7 Home Premium 64 Bit
 
 

Have you tried restoring to an earlier point in time with System Restore? Pay close attention to the NOTE: in part 8. to find older restore points and try to restore to before the problem began.

Backup any important files first.
My System SpecsSystem Spec
.

21 Feb 2012   #14
Jenelia

Windows 7 Ultimate 64 bit
 
 

Yea I thought about restore points but it's really a fresh install, I ran the Windows Memory diagnostics and it reported hardware issues soooo I think for some reason out of the blue a memory chip is bad, the last dump with Driver verifier on turned up nothing driver related so it has to be hardware. UGh... Looks like I'm going to be flipping chips in / out to find the baddies so I think I would say this is resolved... Hardware failure! it Figures! Just my Luck!

Thank you Writh, you've gave me the direction I needed and without it I think I'd be lost. Cheers !

Jen
My System SpecsSystem Spec
21 Feb 2012   #15
writhziden

Windows 7 Home Premium 64 Bit
 
 

No problem. You may also find Avoid Static Damage to Your PC | PCWorld interesting further reading as to why RAM problems can occur. It basically says that ~400 Volts of electrostatic discharge (ESD) can ruin RAM, but you will not feel the discharge until it reaches ~1400-3500 Volts (that link says 3500-4000 Volts, but it varies based on the climate and how dry it is). When RAM receives a shock that we cannot feel, it can work for a while, and then slowly fail over time until symptoms become noticeable. That is one of the many reasons why so many users end up on these forums wondering why their systems are suddenly not working.

So for future reference, make sure you practice good electrostatic discharge (ESD) habbits and keep yourself grounded when touching PC components.

For ESD Safety, follow these steps:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.



Sorry it wasn't something simple. Best of luck tracking the problem down!
My System SpecsSystem Spec
23 Feb 2012   #16
Jenelia

Windows 7 Ultimate 64 bit
 
 

Thank you for that , I do believe that makes alot of sense, I have the computer on a metal file cabinet to keep it off the floor. (I have two german shepherds) so you can imagine the pet dander that gets around, but I have the computer in the living room gated off but the dander and dust does get in here. Most importantly the computer chair was on top of a plastic Chair mat which was on top of a "18x18" RUG.. and it has been dry but not enough for me to get shocked so that point on ESD really does make sense.

I've gone through Windows 7 Memory Diagnostics so far one memory stick at a time and so far 2 sticks (4g each) have checked out fine. I'm logged on now with one that is working so I'm going through to check the other two.

I know when I had all 4 in WMD did report hardware errors so I hope I find the one thats bad and get an RMA from A-Data but it's been almost 2 years so who knows. I can't really complain this is the most trouble I've had with this since I got it, I bought it for 5k from Ibuypower and I called them about the ram and they gave me all the details I needed.

The Mother board is a M4A79T Deluxe (AMD 64 Phenom II x4 965 CPU Installed) I did flash it to the latest bios so I can buy 1600 memory if needed but I don't think I'm that needy for something that powerful at the moment. I just want it working and I'll live with 8GB of Ram if I have to. Money is kinda tight right now. Ok I'm rambling.. sorry Cheers


Thanks again.
My System SpecsSystem Spec
23 Feb 2012   #17
writhziden

Windows 7 Home Premium 64 Bit
 
 

No problem with rambling. You're welcome to provide any updates you want. Glad you're narrowing it down.

You're welcome for the help. Best of luck!
My System SpecsSystem Spec
24 Feb 2012   #18
Jenelia

Windows 7 Ultimate 64 bit
 
 

Thanks I'm going to try the memory diagnostics that comes with Fedora 15 DVD , I have suspicions that the one that comes with Windows isn't thorough enough. I'll report back later
My System SpecsSystem Spec
24 Feb 2012   #19
writhziden

Windows 7 Home Premium 64 Bit
 
 

The Windows diagnostic is not the best, but it does find errors from bad modules if they are bad enough.

My usual rant on this is:
Quote:
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
My System SpecsSystem Spec
26 Feb 2012   #20
Jenelia

Windows 7 Ultimate 64 bit
 
 

I agree Windows Diagnostics suck.. ok I said it. It had me going on a wild goose chase. Thankfully I didn't spend too much time trying to figure *THAT* out so I went directly to MemTest86+ from a bootable Fedora 15 and later downloaded the updated one you linked on it's own bootable CD, Thank you

Having said that I found 2 4gb Chips that actually tested good and have been using them and Windows 7 has been stable for 16 hours and counting, so running on 8GB instead of 16gb. I"ll let this run a week and see what happens

Thanks again for your help
My System SpecsSystem Spec
Reply

 BSOD - Reloaded Fresh but Still happening :(




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD 0x000000d1 fresh 7 install & latest drivers still happening HELP
Just stated getting the same BSOD almost everyday although no drivers have changed or new hardware installed. It has been a few years since I installed 7 so I did a fresh install with a different copy of 7 and again installed the latest drivers currently available. This happens even when the PC is...
BSOD Help and Support
BCCode:50 Problem is happening even on fresh reload of windows.
I'm having this error a lot recently. Seems like it happens everyday now. I'll attach another file that i kept aside after doing a fresh reload of windows to see if I could just wipe the drive and have a fresh set of system files. Well no it's still a piece of shit. So I'm hoping maybe someone...
BSOD Help and Support
BSOD Playing APB Reloaded ntoskrnl.exe
...
BSOD Help and Support
BSOD playing APB:RELOADED
Hello I read your post Blue Screen of Death (BSOD) Posting Instructions.Here is Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML.Please help me. Windows 7 Ultimate x64 Pentium(R) Dual-Core CPU E5700 @ 3.00GHz 4GB RAM 500GB HDD Nvidia Geforce 210 Delux Keyboard A4TECH x7 Mouse and GamePad
BSOD Help and Support
Having BSOD playing APB:Reloaded
Having this BSOD only playing APB:Reloaded and i wanted to know if it's my systems laut or the games. Thank you for help.
BSOD Help and Support
BSOD out of nowhere and still happening on fresh install
hi guys, as the title states i started having BSOD's yesterday, they started out of nowhere then were about an hour apart for a few then became more and more frequent after each reboot, down to about 5 minutes before it would crash with me doing absolutely nothing. this morning i installed...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App