noobiesnack
New Member
- Joined
- Sep 22, 2011
Random BSOD + System Hangs Even After 3 reinstalls
I should probably start off with the history of all this. I built the computer myself in February of this year. I accidentally installed x86 version and it ran perfectly fine. Since I didnt really care at the time, I just left it. Then in May, I decided it was time to go to x64 and also upgraded my RAM from 4GB (2x2GB) to 12GB (2x2GB + 2x4GB). Early July I decided a SSD looked good, installed Windows to it and it ran fine until August.
Sometime in August I started playing a game called APB Reloaded and had crashing issues with the game. Around the same time, I suddenly started getting random BSODs for MEMORY_MANAGEMENT. I ran diagnostics on it and good ol Google. It seemed as though it was just random at the time.
Jump forward a little more (a good 10 BSODs later) and the beginning of September. I started getting annoyed with the BSODs and started trying to solve the problem. Initially, it was looking as if the problem was pointing at AVAST Anti-Virus. So, naturally I got rid of it and tried MSE. About a day later, I get another BSOD pointing to audio. I updated the Audio. 2 days later I get another BSOD that pointed to faulty Drivers in Windows. I attempted to recover and went another few days dealing with random BSODs. I tried to see if I could recreate them. Failed horribly to recreate.
I then found a post suggesting to use verifier to overload the windows drives. I attempted it and I immediately crashed before windows loaded. I found out that there was a very old driver in windows and immediately removed it. Tried to see what would happen after that, after I turned off verifier, and got another BSOD. Tried verifier again and got to desktop only for it to crash for page_fault_in_nonpaged_area pointing at the audio drives. Tried to uninstall the audio drives, and ran it again. Still got BSOD for MEMORY_MANAGEMENT.
Then I seriously thought it might be my memory. I turned the memory diagnostics on, all night on all settings. The results: 19 passes No Errors Detected. I then went to the SSD as the possible cause. Ran every possible HDD utility possible under windows (including a Disk Monitor program) and found 0 Errors. Tried running sfc /scannow, nothing but registry errors that fixed and immediately came back with 0 errors. I then tried to reset all bios settings back to their defaults. I also found, at the time, that I had the onboard graphics enabled and a floppy drive that didnt exist. Also upped my mem speed from 1333 to 1600 during this and pulled the 2x2GB sticks of RAM out. I noticed a huge increase in the speed of the computer (when it was running properly). Gave up at trying when windows decided to BSOD for a random error upon loading firefox.
At that point I said to hell with it and reinstalled windows (This time using Win 7 Pro x64 with SP1) and had hellva time trying to get it to install. I had to force close the install and then install it to get it to install without closing the disk boot. That was yesterday. Today, everything was running perfectly fine. I was installing all my programs and got all the basic stuff down and everything was stable. I got up to go do some homework on my laptop, which is just a few feet away from my desktop, while windows was rebooting from update installation. I turned and looked and it was on the login screen. I said whatever and continued working on my work.
About 15 minutes later, the computer suddenly goes blue and I see it out of the corner of my eye... SYSTEM_SERVICE_EXCEPTION. ofc, I went straight to google and started the debugging tools. Since I was on the login screen, there really wasnt too many drivers loaded and no programs running. The debugging tool has IMAGE_NAME: memory_corruption... Google found to be of little help so now I am here...
Here is the results of the debug tool...
If anything else happens, I will update... If anyone has any thoughts, please share?
PS. heres the specs:
Gigabyte 880GMA-UD2H rv 2.2 (built in VGA disabled)
AMD II x4 645 3.1GHz
2x2GB Corsair DDR3 and 2x4GB Corsair DDR3 with native 1600 support and same timings
NVIDIA 430GT with no OC (running Beta driver WQL 285.27) and all 3d support turned off.
1x40GB Intel SSD with OS
1x500GB WD Green HDD
1x256GB Seagate HDD
1x1TB WD External HDD
also have 2 old drives (DVD ROM and DVD-RW) that I pulled from an old system.
Case has plenty of cooling (1 400mm top mounted, 2 120mm HDD fans, and 120mm rear fan) Highest CPU records approx 40C and highest GPU records 59C (when playing EvE Online in station which is GPU intensive)
Update 1: I managed to get the whole system to lockup from a random error. I could move the mouse around but no programs would respond, including task manager and explorer.exe. I waited a few minutes then just forced it to shut down. I am going to rollback to before I updated and see what happens.
Update 2: After rolling back and confirming that the system is at least stable, attempted to update selected windows updates. went fine. I then updated to IE9 and upon restart:
Update 3: Rolled back with success. Installed IE9 again with no problems this time (no changes to install method which further questions wtf is going on). Changed Bios features DRAM to Dual-Channel mode and pulled the 2x2GB sticks out. Seems to be running fine right now, but this issue is so unpredictable... Also doubled checked all connectors to make sure everything is secure in the case.
I should probably start off with the history of all this. I built the computer myself in February of this year. I accidentally installed x86 version and it ran perfectly fine. Since I didnt really care at the time, I just left it. Then in May, I decided it was time to go to x64 and also upgraded my RAM from 4GB (2x2GB) to 12GB (2x2GB + 2x4GB). Early July I decided a SSD looked good, installed Windows to it and it ran fine until August.
Sometime in August I started playing a game called APB Reloaded and had crashing issues with the game. Around the same time, I suddenly started getting random BSODs for MEMORY_MANAGEMENT. I ran diagnostics on it and good ol Google. It seemed as though it was just random at the time.
Jump forward a little more (a good 10 BSODs later) and the beginning of September. I started getting annoyed with the BSODs and started trying to solve the problem. Initially, it was looking as if the problem was pointing at AVAST Anti-Virus. So, naturally I got rid of it and tried MSE. About a day later, I get another BSOD pointing to audio. I updated the Audio. 2 days later I get another BSOD that pointed to faulty Drivers in Windows. I attempted to recover and went another few days dealing with random BSODs. I tried to see if I could recreate them. Failed horribly to recreate.
I then found a post suggesting to use verifier to overload the windows drives. I attempted it and I immediately crashed before windows loaded. I found out that there was a very old driver in windows and immediately removed it. Tried to see what would happen after that, after I turned off verifier, and got another BSOD. Tried verifier again and got to desktop only for it to crash for page_fault_in_nonpaged_area pointing at the audio drives. Tried to uninstall the audio drives, and ran it again. Still got BSOD for MEMORY_MANAGEMENT.
Then I seriously thought it might be my memory. I turned the memory diagnostics on, all night on all settings. The results: 19 passes No Errors Detected. I then went to the SSD as the possible cause. Ran every possible HDD utility possible under windows (including a Disk Monitor program) and found 0 Errors. Tried running sfc /scannow, nothing but registry errors that fixed and immediately came back with 0 errors. I then tried to reset all bios settings back to their defaults. I also found, at the time, that I had the onboard graphics enabled and a floppy drive that didnt exist. Also upped my mem speed from 1333 to 1600 during this and pulled the 2x2GB sticks of RAM out. I noticed a huge increase in the speed of the computer (when it was running properly). Gave up at trying when windows decided to BSOD for a random error upon loading firefox.
At that point I said to hell with it and reinstalled windows (This time using Win 7 Pro x64 with SP1) and had hellva time trying to get it to install. I had to force close the install and then install it to get it to install without closing the disk boot. That was yesterday. Today, everything was running perfectly fine. I was installing all my programs and got all the basic stuff down and everything was stable. I got up to go do some homework on my laptop, which is just a few feet away from my desktop, while windows was rebooting from update installation. I turned and looked and it was on the login screen. I said whatever and continued working on my work.
About 15 minutes later, the computer suddenly goes blue and I see it out of the corner of my eye... SYSTEM_SERVICE_EXCEPTION. ofc, I went straight to google and started the debugging tools. Since I was on the login screen, there really wasnt too many drivers loaded and no programs running. The debugging tool has IMAGE_NAME: memory_corruption... Google found to be of little help so now I am here...
Here is the results of the debug tool...
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002fe5305, fffff880077f5e30, 0}
Probably caused by : memory_corruption ( nt!MiInsertVadCharges+265 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fe5305, Address of the instruction which caused the bugcheck
Arg3: fffff880077f5e30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!MiInsertVadCharges+265
fffff800`02fe5305 480fab02 bts qword ptr [rdx],rax
CONTEXT: fffff880077f5e30 -- (.cxr 0xfffff880077f5e30)
rax=00000000003ff7ea rbx=000007fefd50b000 rcx=0000000000000001
rdx=fffff70001000000 rsi=0000000000000003 rdi=000007fefd4a0000
rip=fffff80002fe5305 rsp=fffff880077f6810 rbp=00000000003ff7ea
r8=00000000000000ef r9=0000000000000003 r10=fffff70001080078
r11=fffff880077f6800 r12=0000000000000000 r13=000000000000000f
r14=0000000000000001 r15=fffffa8009d63b30
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!MiInsertVadCharges+0x265:
fffff800`02fe5305 480fab02 bts qword ptr [rdx],rax ds:002b:fffff700`01000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002fe5305
STACK_TEXT:
fffff880`077f6810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiInsertVadCharges+0x265
FOLLOWUP_IP:
nt!MiInsertVadCharges+265
fffff800`02fe5305 480fab02 bts qword ptr [rdx],rax
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiInsertVadCharges+265
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
STACK_COMMAND: .cxr 0xfffff880077f5e30 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiInsertVadCharges+265
BUCKET_ID: X64_0x3B_nt!MiInsertVadCharges+265
Followup: MachineOwnerIf anything else happens, I will update... If anyone has any thoughts, please share?
PS. heres the specs:
Gigabyte 880GMA-UD2H rv 2.2 (built in VGA disabled)
AMD II x4 645 3.1GHz
2x2GB Corsair DDR3 and 2x4GB Corsair DDR3 with native 1600 support and same timings
NVIDIA 430GT with no OC (running Beta driver WQL 285.27) and all 3d support turned off.
1x40GB Intel SSD with OS
1x500GB WD Green HDD
1x256GB Seagate HDD
1x1TB WD External HDD
also have 2 old drives (DVD ROM and DVD-RW) that I pulled from an old system.
Case has plenty of cooling (1 400mm top mounted, 2 120mm HDD fans, and 120mm rear fan) Highest CPU records approx 40C and highest GPU records 59C (when playing EvE Online in station which is GPU intensive)
Update 1: I managed to get the whole system to lockup from a random error. I could move the mouse around but no programs would respond, including task manager and explorer.exe. I waited a few minutes then just forced it to shut down. I am going to rollback to before I updated and see what happens.
Update 2: After rolling back and confirming that the system is at least stable, attempted to update selected windows updates. went fine. I then updated to IE9 and upon restart:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 30, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46585 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41287
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: runonce.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880083a26e0 -- (.trap 0xfffff880083a26e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f64e85 rsp=fffff880083a2870 rbp=fffff880083a28c0
r8=fffff80002e0a000 r9=0000000000000001 r10=0000058000000000
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nt!MiResolvePageFileFault+0x1115:
fffff800`02f64e85 8b4830 mov ecx,dword ptr [rax+30h] ds:dc4d:00000000`00000030=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e1d62e to fffff80002e8a640
STACK_TEXT:
fffff880`083a2578 fffff800`02e1d62e : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`083a2580 fffff800`02e8876e : 00000000`00000000 00000000`00000030 00000000`00000000 00000000`80000000 : nt! ?? ::FNODOBFM::`string'+0x46585
fffff880`083a26e0 fffff800`02f64e85 : 00000000`0022ed56 00000000`00000000 fffff8a0`00004df0 fffff800`02ef3964 : nt!KiPageFault+0x16e
fffff880`083a2870 fffff800`02efb530 : 000007fe`ff7570b8 fffff683`ff7fbab8 fffffa80`0e85ca58 fffffa80`0c896811 : nt!MiResolvePageFileFault+0x1115
fffff880`083a29b0 fffff800`02e97979 : fffff880`083a2ae8 ffffffff`ffffffff 00000000`00000100 00000000`00740072 : nt! ?? ::FNODOBFM::`string'+0x399d4
fffff880`083a2ac0 fffff800`02e8876e : 00000000`00000000 000007fe`ff7570b8 fffff900`c2f2ea01 00000000`00000000 : nt!MmAccessFault+0x359
fffff880`083a2c20 000007fe`ff6eecf8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`000def70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff6eecf8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+46585
fffff800`02e1d62e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+46585
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585
BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585
Followup: MachineOwnerUpdate 3: Rolled back with success. Installed IE9 again with no problems this time (no changes to install method which further questions wtf is going on). Changed Bios features DRAM to Dual-Channel mode and pulled the 2x2GB sticks out. Seems to be running fine right now, but this issue is so unpredictable... Also doubled checked all connectors to make sure everything is secure in the case.
Last edited:
