BSOD problems - automatic shut downs

[hunteryau]

My computer had shut down itself and showed a bluescreen for up to 6times today..
this had actually happened to me since i got my computer back from my friend, who helped me in assembling my computer.
But these days when i got some computer work to do i find the problem really serious, and it's affecting my work for so much.

Attached is my system health report and Windows_NT6_BSOD_jcgriff2.
Below is System Spec.

- x86 (32-bit) or x64 ?
it's x86 (32-bit).
- the original installed OS on the system?
Sorry i don't know
- an OEM or full retail version?
Sorry i don't know
- What is the age of system (hardware)?
not over two months, it's newly bought
- What is the age of OS installation
two years maybe? i'm not sure sorry


I need my computer be in good health urgently, anybody please help me

 

[zigzag3143]

There is no information about this file (IPvEx86.sys) Just to be sure please run malwarevytes

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

http://www.malwarebytes.org/products


These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[hunteryau]

i was trying driver verifier. The computer got 'bluescreened' and i rebooted it.
Would u plz explain what does it mean by

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

where can i find the option 'delete existing settings'?

 

[zigzag3143]

i was trying driver verifier. The computer got 'bluescreened' and i rebooted it.
Would u plz explain what does it mean by

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next postwhere can i find the option 'delete existing settings'?

Reboot into windows and turn off verifier by going to search>type verifier> verifier /reset

Dont forget to upload the DMPS/

 

[hunteryau]

how do i locate and zip up the memory dump file?

 

[hunteryau]

umm i know who to zip but i don't know how to locate, i mean

 

[zigzag3143]

how do i locate and zip up the memory dump file?

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Then run the below


“The best and most beautiful things in this world
cannot be seen or even heard,
but must be felt with the heart.”
~ Helen Keller

 

[hunteryau]

For the system information, i found it unable to unload here due to the format's wrong.
Would u tell me details of that so that i can post it up?

Attached is my minidump file, thank you very much=]

 

[zigzag3143]

For the system information, i found it unable to unload here due to the format's wrong.
Would u tell me details of that so that i can post it up?

Attached is my minidump file, thank you very much=]

Memory issue probably caused by your AVG

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide


Microsoft Security Essentials - Free Antivirus for Windows

 

[hunteryau]

However i actually downloaded AVG in these few days, after i found my computer keep bluescreening.
I will contact you later if i counter another bluescreen, thanks

 

[zigzag3143]

However i actually downloaded AVG in these few days, after i found my computer keep bluescreening.
I will contact you later if i counter another bluescreen, thanks

Good luck

 

[hunteryau]

I found my computer bluescreened again.
It seemed that the frequency reduced...this is only my first time since deleting AVG for about 5hours ago.

attached is my newest minidump record.

I have two questions though:
1. Is the bluescreen problem related to my hardware? Maybe some of my devices are not installed properly, or maybe some of them are loose? Is there any relations?

2. I found that when i was playing videos in youtube i have a greater chance to get bluescreen, any relationships again?

Thank you so much for concerning.

 

[hunteryau]

Halo can anybody have a look at my minidump file and figure out what is causing the bluescreen?

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\hunteryau\Minidump\040512-18610-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.21094.x86fre.win7_ldr.111118-2051
Machine Name:
Kernel base = 0x84637000 PsLoadedModuleList = 0x84781890
Debug session time: Thu Apr  5 07:52:00.741 2012 (UTC - 6:00)
System Uptime: 0 days 3:35:50.115
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00008886, The subtype of the bugcheck.
Arg2: 86a26f84
Arg3: 86da75c0
Arg4: 00000403

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


BUGCHECK_STR:  0x1a_8886

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 846d39c4 to 84716624

STACK_TEXT:  
934178e4 846d39c4 0000001a 00008886 86a26f84 nt!KeBugCheckEx+0x1e
93417924 846dc5c9 00000000 00000000 877bc6a0 nt!MiUnlinkPageFromLockedList+0x51
93417994 846ec024 878d8dd8 01000000 00093ad7 nt!MmPurgeSection+0x665
934179c0 8e29e8a7 87429fa8 00000000 00000000 nt!CcPurgeCacheSection+0xe2
93417ae4 8e2b3b45 9845ba24 ba05bc88 cb648988 Ntfs!NtfsDeleteFile+0x8f2
93417ce0 8e2434fa 9845ba24 89b6be00 1d67f7f0 Ntfs!NtfsCommonCleanup+0x1f3e
93417d1c 846bb4fe 9845b9d4 00000000 ffffffff Ntfs!NtfsCommonCleanupCallout+0x1d
93417d1c 846bb5f5 9845b9d4 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
9845b93c 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+51
846d39c4 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+51

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec77376

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_8886_nt!MiUnlinkPageFromLockedList+51

BUCKET_ID:  0x1a_8886_nt!MiUnlinkPageFromLockedList+51

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

Points to memory. Did you run Memtest86+ as instructed by zigzag3143 in post #2?

 

[hunteryau]

Not yet - i haven't got a memory stick or CDs..
But i don't know why the problem of bluescreening seemed to be less serious..it still occurs, though, but not interrupting my work so much.
I'm quite busy these days so it may take me a while to borrow a memory stick or CD and try that test.

Thank you very much for concerning up till now, but i will contact you after the test.

One more question..if i mark this post as solved and in the future i mark it as 'unsolved', will you notice this post?

 

[writhziden]

You're welcome. As long as you post back after marking it unsolved, I will get a notification of the new post via e-mail.