New
#21
Crazy
Hey Zigzag,
Can you suggest anything else? I also went to HP.com and downloaded every single up to date driver for my computer. I am BSOD like crazy.
Thanks
BSOD ntoskrnl.exe Help
-
-
New #22
-
New #23
Minidumps You Dont have
Hello Zigzag,
Here are the mini-dumps that you dont have, they are titled here.zip
Please help this is annoying as hell.
Thanks in advance.
-
New #24
Memory corruption probably caused by your Spybot. I would remove it at least to test AND run these
These crashes were caused by memory corruption (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!!!
1-Memtest.
RAM - Test with Memtest86+*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 or 6 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.
2-Driver verifier
Driver Verifier - Enable and DisableUsing 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.
I'd suggest that you first backup your data 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).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
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 "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 (an estimate on my part).
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.
Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
-
New #25
Hello Zigzag,
I will remove the spybot. But again stated in previous posts, I have completed the Memtest86 and it doesn't give me any errors. I also did the driver verifier and it still currently turned on.
Also if I did a reformat to the computer, and by doing this also removes all software including the spybot, and then reinstalled, why would this issue still happen with a fresh copy of the spybot?
thanks
-
New #26
-
New #27
CMD
Hey Zigzag,
After entering in this command, the command line just drops to the next line with no results inbetween.
-
New #28
-
New #29
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>verifier /query
1/11/2012, 3:57:16 PM
Level: 00000FBB
RaiseIrqls: 0
AcquireSpinLocks: 113503
SynchronizeExecutions: 16378
AllocationsAttempted: 748502
AllocationsSucceeded: 748502
AllocationsSucceededSpecialPool: 748502
AllocationsWithNoTag: 35
AllocationsFailed: 0
AllocationsFailedDeliberately: 0
Trims: 138070
UnTrackedPool: 624621
Verified drivers:
Name: amdxata.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0
Name: atipcie64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0
Name: ahcix64s.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0
Name: nvlddmkm.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 63
CurrentNonPagedPoolAllocations: 6513
PeakPagedPoolAllocations: 69
PeakNonPagedPoolAllocations: 6621
PagedPoolUsageInBytes: 919240
NonPagedPoolUsageInBytes: 5793640
PeakPagedPoolUsageInBytes: 1346120
PeakNonPagedPoolUsageInBytes: 5812136
Name: nvbridge.kmd, loads: 0, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0
Name: netr28x.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 19
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 28
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 4114476
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 4118508
Name: ndis.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 6
CurrentNonPagedPoolAllocations: 9565
PeakPagedPoolAllocations: 8
PeakNonPagedPoolAllocations: 9759
PagedPoolUsageInBytes: 984
NonPagedPoolUsageInBytes: 3749744
PeakPagedPoolUsageInBytes: 1300
PeakNonPagedPoolUsageInBytes: 3809488
Name: rt64win7.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 4104
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 4104
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 443756
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 443756
Name: gearaspiwdm.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 248
PeakNonPagedPoolUsageInBytes: 496
Name: usbfilter.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 140
PeakNonPagedPoolUsageInBytes: 0
Name: nvhda64v.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 4
CurrentNonPagedPoolAllocations: 13
PeakPagedPoolAllocations: 4
PeakNonPagedPoolAllocations: 13
PagedPoolUsageInBytes: 2512
NonPagedPoolUsageInBytes: 9312
PeakPagedPoolUsageInBytes: 2512
PeakNonPagedPoolUsageInBytes: 9312
Name: rtkvhd64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 854
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 854
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 777920
PeakPagedPoolUsageInBytes: 92
PeakNonPagedPoolUsageInBytes: 777920
Name: dump_diskdump.sys, loads: 0, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0
Name: dump_ahcix64s.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0
Name: dump_dumpfve.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 16400
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 16400
Name: atmfd.dll, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0
Name: rainfo.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 28
PeakNonPagedPoolUsageInBytes: 0
Name: lmirfsdriver.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 120
Name: secdrv.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 72
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 316
PeakNonPagedPoolUsageInBytes: 0
C:\Windows\system32>
-
New #30
Quote
Related Discussions