New
#51
You do need to update the Garmin; the driver date is pre-Windows 7. Your Creative Audio driver is also still pre-Windows 7. Creative Worldwide Support > Audigy 2 ZS PlatinumCode:Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\032512-34554-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 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03092650 Debug session time: Sun Mar 25 14:44:11.141 2012 (UTC - 6:00) System Uptime: 0 days 23:35:12.577 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, 100000000, fffff88009c14b70, 0} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c ) Followup: MachineOwner --------- 1: 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: 0000000100000000, Address of the instruction which caused the bugcheck Arg3: fffff88009c14b70, 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: +0 00000001`00000000 ?? ??? CONTEXT: fffff88009c14b70 -- (.cxr 0xfffff88009c14b70) rax=fffff8800fb57350 rbx=fffffa80082a9000 rcx=fffffa8007d7cb70 rdx=0000000000000001 rsi=fffff88009c15750 rdi=fffffa8007d7cb70 rip=0000000100000000 rsp=fffff88009c15558 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000010 r11=fffff88009c15540 r12=fffff8a009ed9220 r13=0000000000000000 r14=0000000000000001 r15=0000000000000001 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246 00000001`00000000 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: iexplore.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000100000000 STACK_TEXT: fffff880`09c142a8 fffff800`02eca2e9 : 00000000`0000003b 00000000`c0000005 00000001`00000000 fffff880`09c14b70 : nt!KeBugCheckEx fffff880`09c142b0 fffff800`02ec9c3c : fffff880`09c15318 fffff880`09c14b70 00000000`00000000 fffff800`02ef5f60 : nt!KiBugCheckDispatch+0x69 fffff880`09c143f0 fffff800`02ef5a6d : fffff800`030e5650 fffff800`0301ed58 fffff800`02e4e000 fffff880`09c15318 : nt!KiSystemServiceHandler+0x7c fffff880`09c14430 fffff800`02ef4845 : fffff800`03014638 fffff880`09c144a8 fffff880`09c15318 fffff800`02e4e000 : nt!RtlpExecuteHandlerForException+0xd fffff880`09c14460 fffff800`02f057c1 : fffff880`09c15318 fffff880`09c14b70 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415 fffff880`09c14b40 fffff800`02eca3c2 : fffff880`09c15318 fffffa80`082a9000 fffff880`09c153c0 fffff880`09c15750 : nt!KiDispatchException+0x135 fffff880`09c151e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiSystemServiceHandler+7c fffff800`02ec9c3c b801000000 mov eax,1 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiSystemServiceHandler+7c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 FAILURE_BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c BUCKET_ID: X64_0x3B_nt!KiSystemServiceHandler+7c Followup: MachineOwner ---------
Unfortunately, your crash report was rather inconclusive. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
Last edited by writhziden; 26 Mar 2012 at 09:07.
Hello, thank for the reply. For the SoundBlaster problem, every time I try to install the driver SBAX_PCDRV_LB_2_18_0017.EXE I got this error :
Long time ago I started another thread for this problem, you can see it herE :
https://www.sevenforums.com/crashes-d...ml#post1853976
The only driver that work for my SoundBlaster Model 0460 is the SBXF_PCDRV_LB_2_18_0015.EXE
I did not try the BETA one...Should I buy another SB to resolve my problem
You mentioned you have 5 things plugged into an 8 port USB hub, What are the 5 USB devices?
Remove your Sound card, check the pins and socket are clean and re-install.
Right now , I have plugged :
Scanner HP , Ipod/Ipone Cable, one cable for my Golf GPS, one cable for a MultiMedia TV BOX...the other cable to plugged into my computer. So I have only 4 cable plugged in the 8-port and one is running (HP SCANNER)
For my soundcard... I already try into another socket in my computer, same thing. I think I try to clean contact in the past..
Hello, I'm just returning from work and my computer was on login screen... so I login and I had a BSOD
If you have time to check if it's the same problem ? SoundCard ??
Thank
Points to a memory problem. You have two different sets of RAM that cause the same crashes, correct?Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\032812-28641-01\032812-28641-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 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`0304b650 Debug session time: Wed Mar 28 13:20:11.168 2012 (UTC - 6:00) System Uptime: 2 days 22:34:42.994 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002eb6211, fffff8800a997e30, 0} Probably caused by : memory_corruption ( nt!MiGetNextNode+25 ) Followup: MachineOwner --------- 1: 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: fffff80002eb6211, Address of the instruction which caused the bugcheck Arg3: fffff8800a997e30, 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!MiGetNextNode+25 fffff800`02eb6211 488b4808 mov rcx,qword ptr [rax+8] CONTEXT: fffff8800a997e30 -- (.cxr 0xfffff8800a997e30) rax=0000000000000003 rbx=fffffa800ae0a720 rcx=fffffa8006f4d890 rdx=fffffa8007a2b9f1 rsi=fffffa800a95ed48 rdi=fffffa8006f4d890 rip=fffff80002eb6211 rsp=fffff8800a998818 rbp=fffffa80079f6d00 r8=0000000000000002 r9=fffffa8006995da0 r10=fffffa8006995288 r11=0000000000000002 r12=fffff8a01610c010 r13=0000000000000000 r14=fffff8a01610c088 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!MiGetNextNode+0x25: fffff800`02eb6211 488b4808 mov rcx,qword ptr [rax+8] ds:002b:00000000`0000000b=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: audiodg.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002eb6211 STACK_TEXT: fffff880`0a998818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetNextNode+0x25 FOLLOWUP_IP: nt!MiGetNextNode+25 fffff800`02eb6211 488b4808 mov rcx,qword ptr [rax+8] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiGetNextNode+25 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 STACK_COMMAND: .cxr 0xfffff8800a997e30 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetNextNode+25 BUCKET_ID: X64_0x3B_nt!MiGetNextNode+25 Followup: MachineOwner ---------
Have you tried physically removing the soundcard from the system? Since audio drivers are primary drivers and should be up to date for the system to function properly, it may be a good test. I suspect either a motherboard or CPU problem if it is not the soundcard drivers causing the crashes.
Hello again, it was quite on my system, I was getting some BSOD sometime but last week and this week it seem I got one every day..I will post the minidump , just to see if that changed.. this morning my system was rebooted so I got the BSOD on idle in the night, sometime I get back from work and system is rebooted too..
Last week, the system crash on me , and I have time to se a driver on the screen , it was nvlddmkm.sys I think... seem to be some NVDIA driver ? I have the latest...
P.S. Something strange happen, everytime I crash, my cookie is gone lol.. I go on the bank login and card is dissappear , I have to re-enter all my info...
Thank you very much
Your crash still indicates memory problems. Do some more rigorous hardware testing.
WarningBefore you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
- If you are overclocking any hardware, please stop.
- Monitor temperatures during the following tests.
Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing CPU stress test using IntelBurnTest
- Do this again: 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).
For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- 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.